[Bug]: App does not return to DApp after signing a message

[ZebanNikolay]

Describe the bug

Using MetaMask Android SDK (0.6.6) to sign a message from an external DApp. After the user completes the signature, the MetaMask app remains open instead of returning automatically to the DApp or shown a BottomSheet with message "Please return to the app to continue using their services." like cancel flow.

This forces the user to manually switch back, which disrupts the flow.

Expected behavior

• After signing is completed, MetaMask should automatically return the user to the DApp.
• Alternatively, display a BottomSheet allowing the user to return manually (similar to the "Cancel" flow).

Screenshots/Recordings

• Video 1 - Signing flow stays in MetaMask without auto-return
• Video 2 - Expected behavior or similar BottomSheet shown on cancel

Steps to reproduce

1. Integrate MetaMask Android SDK (0.6.6) into your DApp.
2. Initiate a connectSign(digest) operation to sign a message.
3. When prompted, approve the signature in the MetaMask application.
4. Observe that after signing, the MetaMask app remains open and does not navigate back to the DApp.
5. User has to manually switch back to the DApp to continue.

Detection stage

In production (default)

Version

7.44.0(1676)

Device

Pixel 6

Operating system

Android