Tornike Kurdadze

This issue should be fixed in version ^2.0.0

Hey @jiapan0622, can you provide more details? Have you tried `pod install` `pod update`?

In version 3.0.0 `com.google.android.gms:play-services-auth:` was upgraded to `21.3.0`. Additionally, I removed the `com.google.android.gms:play-services-auth-api-phone:18.0.1` and added new credentials manager. So, this should not be a problem anymore, feel free to open...

If you are using FIrebaseAuth you don't need to use smart_auth to get the SMS code. You just need to handle `verificationCompleted`. ``` await FirebaseAuth.instance.verifyPhoneNumber( verificationCompleted: (PhoneAuthCredential credential) { pinController.setText(credential.smsCode);...

Is the verificationCompleted method called at all?

The code looks good, but I don't understand why firebase_auth is redirecting you to the reCAPTCHA.

Hey guys, I'll check the [PR](https://github.com/Tkko/flutter_smart_auth/pull/16) today.

Merged the [PR](https://pub.dev/packages/smart_auth/versions/2.0.0) The changes are included in version 2.0.0

> Hello there, Hope you're doing great. I'm getting a error whenever the message is recieved "E/Pinput/SmartAuth(22173): Retrieved SMS is null, check if SMS contains correct app signature" Please checkout...

Most likely you are generating the App signature incorrectly, try to use these guides: https://stackoverflow.com/questions/53849023/android-sms-retriever-api-computing-apps-hash-string-problem https://www.ackee.agency/blog/sms-verification-with-retriever-api