Wallet Application Generates New Address When Signing Zero-X Message

[nico7091]

Description: Our development team has identified an issue with the Uniswap wallet application. While the browser extension functions correctly, the standalone application does not.

Issue Details: When sending a message that begins with 0x to be signed, the wallet application incorrectly generates a new address instead of using the existing wallet address.

However, the Uniswap extension handles this scenario correctly and does not generate a new address.

Expected Behavior: The wallet application should behave the same as the extension—using the existing wallet address when signing messages instead of generating a new one.

Steps to Reproduce: Open the Uniswap wallet application.

Send a signing request with a message starting with 0x.

Observe that the wallet generates a new address instead of using the existing one.

Compare this behavior with the extension, where the issue does not occur.

Environment: Platform: [iOS/Android]

Expected Behavior: The app should sign the message without generating a new address.

Additional Information: Please let us know if you need further details or logs to help diagnose the issue.

[plondon]

Thanks for the report, I can see a crash by reproducing these steps:

1. visit https://1.x.wagmi.sh/examples/sign-message
2. connect using wallet connect
3. attempt to sign 0x1234 <--- crash
4. attempt to sign 1234 <--- success