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!
Related
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
I'm having difficulty figuring out if the user has deleted my app from their Huawei phone when sending a Push.
I'm looking at the push docs, I do not see any error code for this case. Also, looking at the sample app that Huawei has given, I can't see it there either.
Does anyone know exactly what I need to look for when sending a push to Huawei to detect if an app is deleted from the phone?
One gets posted a receipt state with value 2, when the app isn't installed anymore.
If the app does not exist after the message is successfully sent to the device, the app has been uninstalled.
My ReceiptStatus.php would feature these values, but not yet implemented.
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
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
We have an iOS app which is able to receive push notification through the Apigee SDK.
The push notifications are sent by using the Apigee admin console.
Within the console, we configured both dev and prod environments. The prod environment is used for the app published in the App Store. In both cases, the push notifications are well received by our iPhone devices.
However, my question is about the status displayed in the Message History section of the Apigee console.
In the case of the dev notifier, the console display the message : Finished (with errors) with by example, a total sent of 660 for a total errors of 1318.
I don't well understand these figures and I don't know where they are documented.
Is the total sent figure for the number of devices to which the push is sent? However, we don't have as many devices with the dev app version installed
The devices we have with the dev app version installed have well received the push as expected so why are there as many errors?
The detail of the error message is: "INVALID_TOKEN: Failed sending notification."
Thanks very much for your help
We have a bug where statistics get calculated inaccurately if you have errors from the Apns service since they come back asynchronously.
Invalid Token usually means the device is not registered with the apple push notifications service anymore.