(Windows) users are reporting the inability to paste their verification phrase. The input box is greyed out, and they can’t verify their phrase.
Hi could you share a few more details how did you get to this page? Have you tried a different device?
Users attempted to log into our app using Web3Auth (v10). After entering their Google credentials, they are presented with the “New device detected” screen. Clicking on the “Verify” link of the “Recovery Phrase” section brings them to the “Recovery Factor Verification” page. From there, they can’t paste their code. The input box is greyed out and does not allow the user to type or cut/paste.
We’ve been seeing this problem since the migration from v9 to v10.
One user tried on Windows and Android with the same result.
Thanks for sharing more details I’ll check internally
Please refer to [Archive] Stuck on "new device detected" when logging in with `@web3auth/no-modal`, unable to skip - #2 by Ayush
I’m not sure I understand how that helps? Can you please clarify?
Sorry for the delay — we’ve informed the team internally and are waiting for a response. In the meantime, are you currently on version 9 or 10? If you’re on version 10, could you try downgrading to version 9 for now?
We are currently on v10. We recently migrated from v9 to v10. The problem started after migrating to v10.
I prefer to wait for a solution rather than rollback to v9.
One of our users was able to replicate the issue on Android and macOS. This is the same user who first had the issue on Windows.
I am not able to replicate the issue for dapps on v10 for any platform
tried Windows, MacOS, Android and in terms of browsers tried chrome and brave on all the permutations of platforms. Nor this is an issue reported by ANY of our clients.
Can you please share more info if you have been able to replicate it on your side. Any jam.dev recording or something would be better than the current situation
Thank you, maharshi. I asked the user to record a video of the flow.
Hi @maharshi, where can I send you the jam.dev link privately?
Sure, please do. I have opened a DM with you.
Thank you. I sent you the link in DM!
At first glance this seems like a frontend issue. Up until v9 we used to provide a popup or a redirect for entering the backup phrase. But now with v10 we have implemented an iframe and that’s being interfered by some or the other frontend element. And that explains why it emerged post upgrade to v10.
Please have a review of the frontend by yourself or by your engineers. It clearly seems like a frontend issue with the alberto.app site.
And I assure you, there’s no such issue reported so that’s my best bet.
Yup, that was it. Thank you for pointing me in the right direction. I was able to fix the focus trap, and things started working again.
1 Like