-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sms code retrieval is not working when the app is published on the play store #13
Comments
Same issue. |
Most likely you are generating the App signature incorrectly, try to use these guides: https://www.ackee.agency/blog/sms-verification-with-retriever-api |
I download deployment_cert.der and follow google's guide. |
@oktaydegerli Can you share the example of SMS you are receiving? |
"44075 dogrulama kodu ile isleminize devam edebilirsiniz. 5Qs7QEoqbMg B354" 5Qs7QEoqbMg is the appsignature for the published app. Which is generated with using deployment_cert.der. For debug, app signature is different and it works well. |
First of all let's try this: https://stackoverflow.com/a/55017393/8119550 Also a helping hand from ChatGPT Find the Production App Signature:
|
Describe the bug
When I publish the app on playstore the auto sms code retrieval is not working, and I think the issue is caused by appsignature changing when its published that causes it not to detect the sms code ,because the signauture appears similar for all devices and it has a space between the appsignature string
The text was updated successfully, but these errors were encountered: