[Bug]: specific NFT can not be sent from Firefox but it can from Chrome #30327
Labels
regression-prod-12.13.0
Regression bug that was found in production in release 12.13.0
Sev2-normal
Normal severity; minor loss of service or inconvenience.
team-assets
type-bug
Something isn't working
Comments
javiergarciavera
added
Sev2-normal
metamaskbot
added
the
regression-prod-12.13.0
|
right now we don't support ERC1155 sending because we had previously reverted this, right @salimtb ? This is something we wanted to revisit after the massive FLI |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Given this NFT on Linea (https://lineascan.build/token/0xD6309eF7808BF66e1e1adA1AE75Cc255015B61bf), when the owner clicks on send NFT it gets an infinite spinner on Firefox, the same works on Chrome
Expected behavior
The user should be able to send the same NFT from Chrome and Firefox
Screenshots/Recordings
https://www.loom.com/share/a2cd4dbf6986473784e0444bbb16a787
Steps to reproduce
Contact me in order to use the specific account
Error messages or log output
Detection stage
In production (default)
Version
12.13.0
Build type
Beta
Browser
Firefox
Operating system
MacOS
Hardware wallet
No response
Additional context
No response
Severity
No response
The text was updated successfully, but these errors were encountered: