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

Firefox: Extension shows whitescreen #1458

Open
bkchr opened this issue Sep 10, 2024 · 16 comments
Open

Firefox: Extension shows whitescreen #1458

bkchr opened this issue Sep 10, 2024 · 16 comments
Assignees
Labels
Bug Tracks issues causing errors or unintended behavior, critical to fix for reliability. P1 - High Essential for progress, blocks other tasks. Must be completed soon to maintain project flow.

Comments

@bkchr
Copy link

bkchr commented Sep 10, 2024

When trying to sign a transaction, the extension window only shows a white screen. At the beginning you see the window, flashing really fast to just a white screen.

image

(Also trying to open the window via the extension, shows the same result.)

The following error is printed in the console:

Uncaught TypeError: C.name is undefined
    MA moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:389
    Ca moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    _s moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    Cc moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    bu moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    vu moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    yu moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    au moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    ou moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    E moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    O moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
[extension.js:389:2875](moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js)
    MA moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:389
    Ca moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    _s moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    Cc moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    bu moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    vu moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    yu moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    au moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    ou moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    E moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
    O moz-extension://2d853b4a-544b-4b75-881b-38d1f4b49329/extension.js:2
@bee344
Copy link
Member

bee344 commented Sep 10, 2024

@bkchr What chain are you connected to? Or does this happen for several chains? Did you update the extension's metadata before this?

@bkchr
Copy link
Author

bkchr commented Sep 10, 2024

This was while being connected to polkadot collectives. Did not tried others.

@bkchr
Copy link
Author

bkchr commented Sep 10, 2024

On Polkadot I see the same.

@TarikGul
Copy link
Member

I'm having trouble reproducing, but I have a few other ideas. I think we have a solid idea where this is happening in the codebase though!

@MishoKanaria
Copy link

I have also experienced the white screen issue on Chrome. I narrowed it down to Display Address Format to Mythos. Once selected, I cannot remove the white screen

@TarikGul
Copy link
Member

TarikGul commented Oct 1, 2024

Thank you for the extra info - I have a weird suspicion the following is also relavent - polkadot-js/common#1917

@michalkucharczyk
Copy link

I saw the same problem,updating metadata on collectives helped (not sure however how it happened since the extension was white).

@bkchr
Copy link
Author

bkchr commented Oct 7, 2024

I saw the same problem,updating metadata on collectives helped (not sure however how it happened since the extension was white).

That worked for me as well!

@TarikGul TarikGul added P4 - Needs Investigation Requires analysis to determine cause or feasibility. Not fully understood, needs research first. Bug Tracks issues causing errors or unintended behavior, critical to fix for reliability. labels Oct 30, 2024
@TarikGul TarikGul moved this from Issues (Bugs) to P4 - Needs Investigation in Polkadot-js general project board Oct 30, 2024
@liv-ci
Copy link

liv-ci commented Dec 7, 2024

I have also experienced the white screen issue on Chrome. I narrowed it down to Display Address Format to Mythos. Once selected, I cannot remove the white screen

I exactly have this issue. Do you know how to fix that ?

@liv-ci
Copy link

liv-ci commented Dec 8, 2024

I saw the same problem,updating metadata on collectives helped (not sure however how it happened since the extension was white).

That worked for me as well!

When I try to use the Mythos Address Format from the Polkadot Js wallet I keep having the white screen despite the fact that I have updated the metadata for all the parachains. Do you know a fix for that ?

@TarikGul
Copy link
Member

TarikGul commented Dec 8, 2024

Moving this up to High Priority, and will have it pushed up the queue and looked at on Monday.

@TarikGul TarikGul added P1 - High Essential for progress, blocks other tasks. Must be completed soon to maintain project flow. and removed P4 - Needs Investigation Requires analysis to determine cause or feasibility. Not fully understood, needs research first. labels Dec 8, 2024
@TarikGul TarikGul moved this from P4 - Needs Investigation to P1 - High in Polkadot-js general project board Dec 8, 2024
@70m4w0k
Copy link

70m4w0k commented Dec 9, 2024

I have the same issue but error is different :
Out of range ss58Format specified

  • updating metadata on collectives didn't helped
  • no metadata updatable on mythos

Capture d’écran du 2024-12-09 20-53-48

[edit]
It works on private navigation

@TarikGul TarikGul self-assigned this Dec 9, 2024
@TarikGul
Copy link
Member

I have the same issue but error is different : Out of range ss58Format specified

  • updating metadata on collectives didn't helped
  • no metadata updatable on mythos

Capture d’écran du 2024-12-09 20-53-48

[edit] It works on private navigation

Are you getting this same error by trying to access Mythos or is it collective which is giving you the out off ss58 range?

@TarikGul
Copy link
Member

@liv-ci @70m4w0k If either of you could share step by step how you got to the white screen that would be super helpful!

@MishoKanaria
Copy link

@liv-ci @70m4w0k If either of you could share step by step how you got to the white screen that would be super helpful!

I'm using Brave browser, a chromium based browser. When selecting to display addresses in Mythos format in the extension the application goes white. The only solution I've found is to reinstall. Hope this helps

@Dinonard
Copy link

Dinonard commented Jan 2, 2025

Had the same issue appear today (again).
Was working fine throughout the day, then the white screen just appeared.
Same as the original post states, accounts appear for a brief moment before being replaced by a white screen.

Manged to "fix" it by clearing all cookies for the Astar portal page.
Might also help with other pages as well.

Dumped all of the logs from the console when the issue appeared, could be helpful perhaps.

Console Logs
Removing unpermitted intrinsics lockdown-install.js:1:52832
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. assets
@polkadot/types-augment requires direct dependencies exactly matching version 10.9.1.
Either remove and explicitly install matching versions or dedupe using your package manager.
The following conflicting packages were found:
	12.3.1	@polkadot/types vendor.002ddc00.js:233:237384
Cookie warnings 28
The value of the attribute “expires” for the cookie “_ga_BCEBJCWELG” has been overwritten. assets
Cookie “_ga_BCEBJCWELG” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 assets
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite assets
The value of the attribute “expires” for the cookie “_ga_BCEBJCWELG” has been overwritten. assets
Cookie “_ga_BCEBJCWELG” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 assets
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite assets
Cookie “_gid” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite assets
Cookie “_gat_UA-223468575-1” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite assets
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite assets
Cookie “_gid” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite assets
The value of the attribute “expires” for the cookie “_ga_BCEBJCWELG” has been overwritten. assets
Cookie “_ga_BCEBJCWELG” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 assets
The value of the attribute “expires” for the cookie “_ga_BCEBJCWELG” has been overwritten. assets
Cookie “_ga_BCEBJCWELG” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 assets
The value of the attribute “expires” for the cookie “_ga_BCEBJCWELG” has been overwritten. assets
Cookie “_ga_BCEBJCWELG” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 assets
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite assets
Cookie “_gid” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite assets
The value of the attribute “expires” for the cookie “_ga_BCEBJCWELG” has been overwritten. assets
Cookie “_ga_BCEBJCWELG” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 assets
The value of the attribute “expires” for the cookie “_ga_BCEBJCWELG” has been overwritten. assets
Cookie “_ga_BCEBJCWELG” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 assets
The value of the attribute “expires” for the cookie “_ga_BCEBJCWELG” has been overwritten. assets
Cookie “_ga_BCEBJCWELG” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 assets
Cookie “_ga” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite assets
Cookie “_gid” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite assets
The value of the attribute “expires” for the cookie “_ga_BCEBJCWELG” has been overwritten. assets
Cookie “_ga_BCEBJCWELG” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite 2 assets
Request to access cookie or storage on “<URL>” was blocked because it came from a tracker and content blocking is enabled. 2
Cookie “_gh_sess” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. astar.png
Cookie “_octo” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. astar.png
Cookie “logged_in” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. astar.png
2025-01-02 17:04:20        API/INIT: RPC methods not decorated: chainHead_v1_body, chainHead_v1_call, chainHead_v1_continue, chainHead_v1_follow, chainHead_v1_header, chainHead_v1_stopOperation, chainHead_v1_storage, chainHead_v1_unfollow, chainHead_v1_unpin, eth_getBlockReceipts, transactionWatch_v1_submitAndWatch, transactionWatch_v1_unwatch, transaction_v1_broadcast, transaction_v1_stop vendor.002ddc00.js:250:16677
2025-01-02 17:04:20        API/INIT: astar/1200: Not decorating unknown runtime apis: 0xe8accb82fb152951/2, 0x91b1c8b16328eb92/1 vendor.002ddc00.js:250:16677
web3Enable: Enabled 1 extension: polkadot-js/0.56.1 vendor.002ddc00.js:233:235850
web3Accounts: Found 4 addresses vendor.002ddc00.js:233:236231
Cookie “_gh_sess” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. astar.png
Cookie “_octo” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. astar.png
Cookie “logged_in” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. astar.png
Calculating leaderboard app.7cb3d89a.js:1:11379628
protocol state 
Object { era: 938, nextEraStart: 7804534, periodInfo: {…}, maintenance: false }
app.7cb3d89a.js:1:129707
Fetching dapps app.7cb3d89a.js:1:11362481
ledger 
Object { locked: 505895173692695373274235n, unlocking: (1) […], staked: {…}, stakedFuture: {…}, contractStakeCount: 1 }
app.7cb3d89a.js:1:129979
Download the Apollo DevTools for a better development experience: https://addons.mozilla.org/en-US/firefox/addon/apollo-developer-tools/ vendor.002ddc00.js:215:1045253
Staker info size: 1 app.7cb3d89a.js:1:11404834
Fetching stake amounts app.7cb3d89a.js:1:11363228
Staker info size: 1 app.7cb3d89a.js:1:11404834
Fetching stake amounts app.7cb3d89a.js:1:11363228
Staker info size: 1 2 app.7cb3d89a.js:1:11404834
web3Enable: Enabled 1 extension: polkadot-js/0.56.1 vendor.002ddc00.js:233:235850
web3Accounts: Found 4 addresses 3 vendor.002ddc00.js:233:236231
Source map error: Error: URL constructor:  is not a valid URL.
Stack in the worker:resolveSourceMapURL@resource://devtools/client/shared/source-map-loader/utils/fetchSourceMap.js:56:22
getOriginalURLs@resource://devtools/client/shared/source-map-loader/source-map.js:73:24
workerHandler/</<@resource://devtools/client/shared/worker-utils.js:115:52
workerHandler/<@resource://devtools/client/shared/worker-utils.js:113:13

Resource URL: wasm:https://portal.astar.network/js/vendor.002ddc00.js%20line%20248%20%3E%20WebAssembly.instantiate
Source Map URL: null

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Tracks issues causing errors or unintended behavior, critical to fix for reliability. P1 - High Essential for progress, blocks other tasks. Must be completed soon to maintain project flow.
Projects
Development

No branches or pull requests

8 participants