Facing Google Wallet crashes when using Fingerprint on the lock screen? Discover quick solutions in this guide to ensure seamless mobile payments. Despite its convenient features for online and contactless payments, Google mobile payment service has encountered issues.
Table of Contents
Many users reported crashes since the December update, particularly when launching Google Wallet from the lock screen and using Fingerprint authentication. If you’re facing this bug, follow these workarounds outlined below to resolve the issue effectively.
Solution1: Community-Tested Workaround
Several users on the Google Support Forum have successfully utilized the following workaround. Give it a try to potentially resolve the issue:
- Tap the Wallet lock screen icon.
- Choose the “Show All” option.
- Unlock the device using your fingerprint.
- Verify if the Wallet app continues without crashing on your device.
This workaround has proven effective for many users; attempt these steps to see if it resolves the issue for you.
Solution 2: Change Lock Screen Unlock Method
- Go to Settings > Security and Privacy > Device Unlock.
- Authenticate with your current credentials.
- Select a different lock screen unlock style from the provided list.
Solution 3: Access Google Wallet After Unlocking
Launch the Google Wallet app only after unlocking your device. Access it from the app drawer or the quick settings toggle instead of launching it directly from the lock screen. This adjustment should prevent the app from crashing on your device.
Solution 4: Clear Google Wallet Data
Resolving potential app data corruption could rectify the issue. Proceed with caution as this process will delete saved cards, requiring you to re-add them:
- Navigate to Settings > Apps > All Apps > Google Wallet.
- Access Storage and Cache, then select “Delete Data” > OK.
- Relaunch Wallet, set it up again, and assess the results.
Officially, the developers haven’t acknowledged or provided an ETA for a fix. If any updates or acknowledgments occur, this guide will be promptly updated. For now, these workarounds remain the recommended solutions.