-
Notifications
You must be signed in to change notification settings - Fork 7
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
wallet Dapp Connection dialog fails silently with some privacy settings #45
Comments
stackoverflow disucssion suggests this is due to unusual privacy settings. In any case, I'd like us to do better than a silent failure. In some cases we seem to be careful about lack of access to wallet-app/src/util/storage.ts Line 8 in 0d65965
but in others, maybe not so much? wallet-app/src/contexts/Provider.tsx Line 211 in 0d65965
|
third party cookies blocked, do not track, clear cookies on shutdown ( I intermittently wipe all cookies manually like google youtube etc that get left on about once a month) |
This is the relevant code wallet-app/src/bridge-dapp.tsx Lines 184 to 203 in 0d65965
I guess the check for 'localstorage' in window is returning true, but it's throwing a security error when trying to read it? It's difficult to tell because these behaviors are not well documented by browsers, it can vary by environment. Maybe we just need to wrap the whole thing in a try-catch. |
Since the security settings make the PSM connection to Wallet impossible, I agree the issue here is about feedback. At the least, I think we should have a global error handler that reports exceptions to the user. Could be a simple toast. Do we also have a check specific to localStorage? IMO a user this app upon seeing an error message about localStorage would look into their browser settings. |
I allowed all cookies, and the transfer worked just now. The two window system is unique to do a swap in my experience. Look forward to the Agoric system buildout : ) |
A community member reports:
cc @FredRadford @samsiegart @turadg
The text was updated successfully, but these errors were encountered: