Key no longer acessible

Hey, we have found something that is not supposed to happen. The same login method generated 2 different keys and one of these keys is no longer acessible, there are funds on it and we have our hands tied on how to recover it.

To be super specific, we accept 2 different login methods (google SSO, email) and we have 3 addresses linked with these 2 login methods, which means that 1 login method has 2 addresses associated with it.

This happened concurrently with a missing tokenId bug that has been widely reported on this forum - so there might be some correlation.

We need help on how to help the user recover the funds that got stuck there - as we have no more ideas on what can be done on our end. Urgency is very much appreciated.

Thank you

@joao Welcome Aboard!

Sorry for the delay.

Have you ensured you have updated to the latest SDK version?

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.