Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: DID Linked Domain Resolution broken #1092

Closed
2 tasks done
eike-hass opened this issue Feb 7, 2024 · 0 comments · Fixed by #1094
Closed
2 tasks done

[Bug]: DID Linked Domain Resolution broken #1092

eike-hass opened this issue Feb 7, 2024 · 0 comments · Fixed by #1094
Assignees
Labels
bug report Something isn't working as intended

Comments

@eike-hass
Copy link
Contributor

Issue description

Resolution of Linked Domains on Alias Address page fails, likely because the Wasm library can't be loaded.

Expected behaviour

Linked Domains get resolved

Actual behaviour

"no linked domains" and error in console

Can the issue reliably be reproduced?

Yes

Steps to reproduce the issue

  1. Open https://explorer.iota.org/testnet/addr/rms1ppyx34shww5l3e28gynp5r5zljyru2vuyc2vjjeyqr3yy02vtwlx52sh4rj?tab=DID
  2. See "no linked domains"

Errors

From browser console:
Uncaught (in promise) CompileError: WebAssembly.instantiate(): expected magic word 00 61 73 6d, found 3c 21 44 4f @+0

Duplicate declaration

  • I have searched the issues tracker for this issue and there is none

Code of Conduct

  • I agree to follow this project's Code of Conduct
@eike-hass eike-hass added the bug report Something isn't working as intended label Feb 7, 2024
@begonaalvarezd begonaalvarezd self-assigned this Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Something isn't working as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants