Wallet Application Generates New Address When Signing Zero-X Message

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.

Start by reproducing the signing request in the standalone iOS or Android wallet with a message beginning with 0x, then compare its address-selection flow with the browser extension. Trace where the app chooses the signing address and verify that the existing wallet address is retained. Done means the app signs the message without generating a new address on the affected platforms.