-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Aptos Connect Signature for Sponsored Transactions is Invalid #465
Comments
We have debugged the issue so far and reached to the following log. It occurs with all tested endpoints (official/nodit) and intermittently with the following flow: Sign in with Google -> Sign Transaction. I suspect smth like that the JWT has expired internally and is not being refreshed.
|
Context
Requesting a signature via Aptos Connect sometimes results in an invalid Signature error when trying to sponsor and submit the transaction.
Error from the logs:
{"message":"Invalid transaction: Type: Validation Code: INVALID_SIGNATURE","error_code":"vm_error","vm_error_code":1}
This behavior is not deterministic, meaning that sometimes the transaction is executed successfully, sometimes the error above is returned.
The error happens using Aptos Connect via Browser, as well as via Telegram Mini App.
Steps to Reproduce
The issue can be reproduced by requesting a signature and sponsor the transaction using the following next client- and server functions:
Client:
Server:
Expected Behavior
The message signature is valid and the transaction can be executed by the server after sponsoring the gas fees.
Actual Behavior
Sometimes, the user's signature seems to be invalid. This is an excerpt of the server logs:
{"message":"Invalid transaction: Type: Validation Code: INVALID_SIGNATURE","error_code":"vm_error","vm_error_code":1}
Debugging Notes
Unfortunately, this error is not deterministic. At one test, after the INVALID_SIGNATURE error already happened twice, the third execution was successfull.
The text was updated successfully, but these errors were encountered: