We are currently receiving an error from users (myself included) where they attempt to login via google, are given the 2FA to verify, reverify via their email address and then are given an “account mismatch”.
We recorded the exact experience here: Jam
We think it’s due to POST 500 Batch too large https://sapphire-1.auth.network/metadata/bulk_set_stream but we don’t have any way to debug further.
Please help. Thank you.
@sheldon.smickley Welcome Aboard!
Your issue has been forwarded to our team and we will get back to you with further updates.
hey @sheldon.smickley ,
Could you help me with your verifier, verifier ID and client ID ?
Since the bulk stream api is failing and it’s showing that the user has too many shares, can you tell me the number of shares the account has?
Thanks Maharshi. I think this could be a key reason. We are using a progressive web app (PWA) but every time a user opens the site and logs in again via safari, they will have a new device share.
Will add more to this comment once I get you more information about our verifier.
Client ID: BAWKYGf9DxxRIO_YEQQesINyfDTKlfzrN3lrdqV0Fcp6cOPynuysCFAWHfIDjFttCs4GJPQUK6IXvOHyHR5zdRw
Verifier ID/Name: firebase_1698396118
we are using a custom verifier using JWT tokens (from firebase).
Hey guys just checking in on this - thank you!
Hi @sheldon.smickley , thanks for providing a very clear bug report using jam, appreciate that.
We found the issue and its happening for users having large number of shares which is exceeding the max size allowed.
We are working on a fix , i will update you here once this is fixed.
That’s fantastic to hear! Thank you.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
I just wanted to followup and check if this is fixed for you. We released new updates to our SDKs fixing this issue from our end. You might like to update to the latest version to make sure you get the fix.
Additionally, I’d request you to please implement a flow within your app to restrict the share creation to at max 6. More than 6 shares created will cause the metadata to throw errors like this. Please check from your tkey details, if the number of shares are exceeding 6, please get the user to delete their older shares. Ideally, you should create 2 recovery shares and ask the user for their trusted devices and only store the device share on them.