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
Initiate a transaction - 0.1 FTM from Fantom to Solana via token manual route
Resume the transaction
Observe the browser console for errors
Expected Result: The transaction should resume without errors or interruptions.
Actual Result: The following error is displayed in the console:
Uncaught (in promise) Error: when deserializing item 'mintRecipient': chunk is shorter than expected: 133 < 145
at updateOffset (main-BGFYirgS.js:286:9999)
at deserializeItem (main-BGFYirgS.js:286:11810)
at internalDeserialize (main-BGFYirgS.js:286:10219)
at deserialize$2 (main-BGFYirgS.js:286:9768)
at main-BGFYirgS.js:286:149265
at deserializePayload (main-BGFYirgS.js:286:149502)
at deserialize$1 (main-BGFYirgS.js:286:148883)
at getVaa (main-BGFYirgS.js:291:20192)
Attachments/Notes
The error also occurs in the production environment. See related comment in #3122 (comment).
The text was updated successfully, but these errors were encountered:
Issue is also reproducible when resuming transfer from Solana.
Transfer: 0.0001 WSOL from Solana (Phantom) to Base (MetaMask) with Token Bridge Manual route.
Build: Netlify preview
Uncaught (in promise) Error: when deserializing item 'mintRecipient': chunk is shorter than expected: 133 < 145
at updateOffset (main-BGFYirgS.js:286:9999)
at deserializeItem (main-BGFYirgS.js:286:11810)
at internalDeserialize (main-BGFYirgS.js:286:10219)
at deserialize$2 (main-BGFYirgS.js:286:9768)
at main-BGFYirgS.js:286:149265
at deserializePayload (main-BGFYirgS.js:286:149502)
at deserialize$1 (main-BGFYirgS.js:286:148883)
at getVaa (main-BGFYirgS.js:291:20192)
Describe the current behavior in detail
Environment:
Steps to Reproduce:
Expected Result: The transaction should resume without errors or interruptions.
Actual Result: The following error is displayed in the console:
Attachments/Notes
The error also occurs in the production environment. See related comment in #3122 (comment).
The text was updated successfully, but these errors were encountered: