I’ve integrated the latest Web3Auth Flutter package into my app. Everything works perfectly in both debug and release builds when I install directly on my device.
However, after uploading the app to the Google Play Store and downloading it from there, Web3Auth stops working. Whenever I try to open Web3Auth, it immediately throws a userCancelled exception instead of proceeding with the login flow.
Works fine in:
Debug build
Local release build (APK/AAB)
Fails in:
Play Store downloaded build
Any guidance or fixes would be really appreciated
Thank you for the detailed report! Here’s a summary of your issue and the context for the support team:
Issue Summary
SDK & Version: Web3Auth Flutter SDK, v6.3.0 (Plug n Play)
Platform: Android (Google Play Store)
Integration: Using Firebase as a custom authentication provider (JWT login)
Problem:
Web3Auth works in both debug and local release builds (installed directly on device).
After uploading to the Play Store (internal testing), the app throws a userCancelled exception immediately when trying to open Web3Auth, and the login flow does not proceed.
Works in:
Debug build
Local release build (APK/AAB)
Fails in:
Play Store downloaded build
Additional Details Needed (if possible)
To help the team debug further, could you please provide:
Web3Auth Initialization & Login Code Snippets
(especially how you set up the redirect URI and loginConfig in your Flutter code)
Verifier Name (from your Web3Auth Dashboard)
Sample idToken (JWT) (redact any sensitive info)
Redirect URI registered in Web3Auth Dashboard and AndroidManifest.xml
Any Play Store-specific configuration (e.g., App Signing, Proguard rules, SHA-1/256 fingerprints added to Firebase/Web3Auth Dashboard)
Screenshots of the error/console logs (if available) would also help.
Possible Causes & Suggestions
This is a common scenario with authentication flows after Play Store upload. Here are some things to check:
Redirect URI Mismatch:
The Play Store build may have a different package name or signing certificate, causing a mismatch in the redirect URI or OAuth configuration.
Ensure the redirect URI in your app and on the Web3Auth Dashboard matches the Play Store version.
Ensure the SHA-1/256 fingerprints from the Play Store signing key are added to your Firebase project and Web3Auth Dashboard.
App Signing by Google Play:
When using Play Store, Google re-signs your APK/AAB. You must add the Play Store app signing SHA-1/256 to Firebase and any OAuth providers.
Proguard/R8 Minification:
If you’re using Proguard or R8, ensure you have the correct rules to keep Web3Auth and Firebase classes.
Intent Filters:
Double-check that your AndroidManifest.xml has the correct intent filters for the custom scheme you use for redirect.
Firebase Configuration:
Make sure your google-services.json is up to date and includes the Play Store signing fingerprints.
Next Steps:
Please share the requested code/config details and confirm if you’ve added the Play Store app signing SHA-1/256 to both Firebase and Web3Auth. This will help us pinpoint the issue quickly.
Let me know if you need help finding your app signing keys or configuring the redirect URI!
Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.
Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours
I am not using firebase just passwordless authentication its work fine when i use it as release but when ever i put it in playstore its stops opening me i dont know why its happening in 6 version of web3auth please help me.
Works fine in:
Fails in: