You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 12, 2021. It is now read-only.
A few people have reported issues in which a response coming back from the mobile app is unable to be verified. It's unlikely that the problem is in the libraries, as a valid signature with other issues would not crash in this particular place.
In android chrome, a user provided this trace
A similar trace was provided by an EthDenver user, after receiving the response from a disclosure request:
Initial suspicions were that an old signer of some sort is using the wrong algorithm to sign -- I think I've seen something similar with ES256K vs ES256K-R? However, the latter crash was experienced by a user after supposedly creating a fresh account on the latest version of the app, so that's particularly confusing, and I have been unable to reproduce so far.
The text was updated successfully, but these errors were encountered:
A few people have reported issues in which a response coming back from the mobile app is unable to be verified. It's unlikely that the problem is in the libraries, as a valid signature with other issues would not crash in this particular place.
In android chrome, a user provided this trace
A similar trace was provided by an EthDenver user, after receiving the response from a disclosure request:
Initial suspicions were that an old signer of some sort is using the wrong algorithm to sign -- I think I've seen something similar with ES256K vs ES256K-R? However, the latter crash was experienced by a user after supposedly creating a fresh account on the latest version of the app, so that's particularly confusing, and I have been unable to reproduce so far.
The text was updated successfully, but these errors were encountered: