iOS devices issue with retrieving wallet address #856
Replies: 4 comments 6 replies
-
If session storage is blocked then we fallback to an encrypted server channel. It should always return the address. You can DM me your app link and way to reproduce the issue on telegram: himanshuchawla009 |
Beta Was this translation helpful? Give feedback.
-
I am not getting a support from @himanshuchawla009 Just getting generic answers. |
Beta Was this translation helpful? Give feedback.
-
Hey @alaabadran Can you please check your iOS version? Web3Auth cannot work with iOS v13 and lower. It only supports iOS 14 and above. This is because the browsers don't support BigInt. Please check the compatible browsers here: https://browsersl.ist/#q=supports+bigint%2C+not+dead |
Beta Was this translation helpful? Give feedback.
-
This issue was solved by migrating to the latest SDK. |
Beta Was this translation helpful? Give feedback.
-
We have integrated Web3Auth with our website.
Previously, when trying to login with iOS devices using Chrome browser.. It was working fine.
Lately, login is successful but wallet address is not retrieved. This is causing many functionalities to break up. And currently, I can make it work on Safari iOS browser by disabling
Prevent Cross-Site Tracking
in settings.Debugging the issue (session storage data) on Safari Browser (iOS):
{"userModule":{"userInfo":{"email":"","name":"","profileImage":"","verifier":"","aggregateVerifier":"","verifierId":"","typeOfLogin":"google"},"clientTimeOffset":0,"keyInfo":{"typeOfUser":"v1","privateKey":"","pubKey":{"pub_key_X":"","pub_key_Y":""},"publicAddress":"","metadataNonce":""},"walletKeyInfo":{"typeOfUser":"v1","privateKey":"","pubKey":{"pub_key_X":"","pub_key_Y":""},"publicAddress":"","metadataNonce":""},"currentDappClientId":"REMOVED","authToken":"","challenge":"","uniqueDapps":[],"alwaysSkip":false,"persistedUserInfo":{}}}
All are empty
The data is blocked by the brower.
Is there any solution for this?
Beta Was this translation helpful? Give feedback.
All reactions