Simulating a Phone Call Interruption During a Transaction Signing

Mobile devices are multifunctional, and interruptions are common. This test checks the resilience of the MetaMask Android app when a phone call or other system-level interruption occurs during a critical process like transaction signing. The tester initiates a send transaction and proceeds to the confirmation screen where the password must be entered. At this point, an incoming phone call is simulated (or a call is made to the device). The system should handle the incoming call, pushing the MetaMask app into the background. After the call ends (or is declined), the user must be able to return to the MetaMask app. The ideal behavior is for the app to have maintained its state, returning the user directly to the transaction confirmation screen, allowing them to continue where they left off. The worst-case but acceptable behavior is for the app to have cancelled the transaction and returned to the main screen, requiring the user to start over. The test fails if the app crashes, becomes unresponsive, or displays corrupted data. This tests the app’s ability to manage its activity lifecycle correctly. For reporting any instability issues, the primary channel is the support page at metamask.