Firebase phone auth sms not using app name from playstore - firebase

I've made an app with Flutter Firebase and released to Google playstore about 2 months ago and till today,the verification SMS sent to user's phone isn't picking up the app name from the playstore. The SMS received is given as example below
111111 is your verification code for myproject465.firebaseapp.com
Another user got responded by firebase support [here][1] stating that the %APP_NAME% will be automatically used after release(small delay may occur) but it's been more than a month and still not picking up the app name.
I've contacted firebase support but as I'm unable to opt in for a paid tech support, they can't help me further. Hope someone here can help me out
UPDATED: Enabling Safety net in the project fixed the issue for me( auth domain update not done)
[1]: https://stackoverflow.com/a/52525587/7610087

Related

Firebase Authentication for Android not working

I am using firebase phone authentication for signin/loggin in user using flutter.
It was working fine till yesterday but from today I am receiving the below-mentioned error.
[firebase_auth/missing-client-identifier] This request is missing a valid app identifier,
I have configured the project properly i.e. enabling Android Device Verification and adding SHA 256 in the firebase project's console setting page.
I am observing 100% error rate Android Device Verification and Identity Toolkit API.
Can someone help me on what the issue can be
Ideally this issue shouldn't have happened as it was working fine till yesterday

Firebase phone auth failing on app already in production with status code 17028

We are using firebase phone authentication to authenticate our users. We've been using it for over a year now.
Today at 13:00 GMT, new users are receiving 17028 An invalid safety_net_token was passed after entering their phone number.
I tried to verify each of the causes I found on the firebase docs:
Verifying the SHA1 and SHA256 on the firebase console (We use the fingerprints that are on the play store console)
Verifying the package name
The last app update was on October 1st and since then thousands of users created an account with Firebase Auth and there were no configuration changes on the firebase console.
Upon looking at other StackOverflow questions, the error we are getting is not the same as 17028 A safety_net_token was passed, but no matching SHA-256 was registered in the Firebase console. Please make sure that this application's packageName/SHA256 pair is registered in the Firebase Console Even though it is the same error code, in our case, it says an invalid token was passed.
We are using firebase with react-native-firebase module.
EDIT: After disabling Android device verification API from Google Cloud Console the verification is now working but with no device verification. (Users have to verify they're not robots with a CAPTCHA).
Update: It is working fine now, and the outage has been fixed.
It looks to be a firebase internal issue, and the only solution now is to disable "Android Device Verification" and all your users will see the Recaptcha page.
check
https://status.firebase.google.com/
https://status.firebase.google.com/incidents/TYeQBVB4kkzyk2kE8vbP

Apple rejected the app due to "Token mismatch" authentication error in a Flutter app with Firebase Phone Authentication

Firebase Authentication with phone number is configured and tested on iOS via Testflight but seems that is not working when Apple is reviewing the app.
We provided a whitelisted phone number which worked with the build downloaded from Testflight.
I've found a couple of similar issues in GitHub but all was fixed... I'm using the latest version of Firebase auth plugin.
I added a GitHub issue as well but no reaction there: https://github.com/FirebaseExtended/flutterfire/issues/3800
Did somebody had to deal with this ?
Finally the app passed Apple review. Below is what we did, in case somebody will encounter this in the future:
We had two APN's created in Apple Developer account. The second one was configured in Firebase Console
===> we removed the first so now we have only one APN in Apple Dev account
In Firebase Console we had also certificates uploaded (Firebase states that
those are not used if a .p8 key is uploaded)
===> we removed the unused APN certificate and used only the APN .p8 key.
Resubmitted the app to review and it passed.

Firebase Phone Auth Blocked

I am testing Firebase SMS authentication on my android app on release mode. So, after few succesful authentications, I started getting the error:
we have blocked all requests from this device due to unusual activity. Try again later
I deleted the affected user but still not working. Then, I contacted Firebase support and that's what they said:
There's a limit of 5 SMS per phone number per 4 hour
Now I am struggling how to test my app before making it live for real users.
I need to test receiving SMS instead of using whitelisted phone numbers. The reason is that I have a bug on release mode which requires many testings to be fixed. Please I need some help!

FCM console push test is currently broken? (Android)

I've been using FCM console(web) to test push notification for Android smartphone.
I use push token from Android device, but FCM console says "Completed" and it's not delivered.
It worked fine before, but recent few days, it's not working.
Is there anyone facing same problem?
I got an answer from FCM support team.
Thank you for that information.
It would seem that you are affected by the changes made between July
31 and August 1st. We rolled out a change to Firebase Notifications to
filter apps by GMP App Id rather than by package name. This change was
purely internal and should have had no effect on visible behavior as
all apps using Firebase should have had both package name and app id
set to match. However, we are now seeing some apps that have the wrong
app id set and this is causing messages to not be delivered (or in
some cases to be delivered to the wrong app if an app has the app id
of another app). These apps have a bug that was previously masked but
is now exposed.
We are investigating ways in which apps have sent these incorrect app
ids and ways in which we can catch them and warn app developers.
For now, the Firebase Notifications console will only work with apps
that use the FCM SDK. We recommend updating to the latest version of
the FCM SDK in order to mitigate the issue, but in case you don't want
to migrate to FCM SDK, you can still use your own server to send push
notifications.
Apologies for the inconvenience this may have caused. Please let me
know if there's anything else I could help with.
Regards,

Resources