[🐛] Error: [auth/internal-error] An internal error has occurred, please try again.

[EmanuilM]

[🐛] Error: [auth/internal-error] An internal error has occurred, please try again.

[mikehardy]

It is regrettable that support basically refuses to support just because it's react-native-firebase but I'm happy you have found a demo using their code so they'll check it out hopefully - this appears to be a backend (that is: firebase / google cloud) issue though and no changes have occurred here

Since there won't be anything we can actually do in this repo to fix things via code change or similar I'm going to close this as not actionable but you are more than welcome to continue collaborating here - closed issues are just as good for sharing information via comments as open ones, they just don't signal that we have an action to take in repo

Hopefully this resolves for your Belorussian users

[snowluminum]

If it's of any help, I was encountering the same auth/internal-error on iOS. I then used same code on web (React Native Web), and the network response showed this:

code: 400
reason: "invalid"
message: "DYNAMIC_LINK_NOT_ACTIVATED : FDL domain is not configured"

after setting up my domain as a Dynamic Link domain, it worked.

Obviously Dynamic Links are being sunsetted, but see this part of the guide for more info on how it affects email link sign in methods.

btw me and @EmanuilM facing problem with phone auth, not email

[snowluminum]

Facing the same issue here.

Also noticed this in google cloud console

[EmanuilM]

Facing the same issue here.

Also noticed this in google cloud console

What is this? Can you give more information about the stats and where i can find them

[snowluminum]

Here you go

https://console.cloud.google.com/apis/api/identitytoolkit.googleapis.com/metrics

At the bottom of the page there is errors by api endpoint. Don't know exacly how to view what king of errors.

Also not sure if its problem of rnfirebase, because on web we use google's firebase package and get this

[EmanuilM]

I believe the issue is with Google authentication services. I contacted the support team, but they informed me that they cannot assist because they do not support the react-native-firebase library. I attempted to implement authentication using the JavaScript SDK, but it does not support reCaptcha for mobile devices.

I have also verified the credentials in the Google Cloud Console, and everything appears to be correct.

If you find a solution, I would be grateful if you could share it.

[EmanuilM]

Could you please let me know when you first started encountering this error? Additionally, do you have any applications currently in production? If so, are they being affected by this issue?

[snowluminum]

Yep, app is in production, and as i see users only from Belarus are affected. Tried this https://fir-ui-demo-84a6c.firebaseapp.com/ demo and facing the same issue here. Check phone numbers affected by this error here, if problem persists than we have same error. btw started facing this issue 3-5 days ago

[EmanuilM]

@snowluminum Did you try to contact Firebase support and provide them your example app? If so what they are saying about the issue

[snowluminum]

I can say you more) They provided me example app. But the thing is that they resposes take too long (1-2 days)

[EmanuilM]

Thank you for the information

I also reached out to them, and their suggestion was to use their JS SDK. Unfortunately, it is not compatible with the React Native environment. I am currently waiting for their response.

I would appreciate it if you could share any additional information you receive from them.

[snowluminum]

Thank you for the information

I also reached out to them, and their suggestion was to use their JS SDK. Unfortunately, it is not compatible with the React Native environment. I am currently waiting for their response.

I would appreciate it if you could share any additional information you receive from them.

You have no issues in demo?

[EmanuilM]

I have issue in the demo website, the issue is same as yours error code 39

[snowluminum]

Than JS SDK wont help you)

[EmanuilM]

Do you have alternative auth method for your production apps until the problem from Firebase is resolved?

[snowluminum]

Do you have alternative auth method for your production apps until the problem from Firebase is resolved?

Unfortunatly no, i'm ended writing self hosted saml method that works side by side with firebase phone auth. In our app phone auth is crucial method to prvent spam.

[harveyappleton]

If it's of any help, I was encountering the same auth/internal-error on iOS. I then used same code on web (React Native Web), and the network response showed this:

code: 400
reason: "invalid"
message: "DYNAMIC_LINK_NOT_ACTIVATED : FDL domain is not configured"

after setting up my domain as a Dynamic Link domain, it worked.

Obviously Dynamic Links are being sunsetted, but see this part of the guide for more info on how it affects email link sign in methods.

[EmanuilM]

If it's of any help, I was encountering the same auth/internal-error on iOS. I then used same code on web (React Native Web), and the network response showed this:

code: 400
reason: "invalid"
message: "DYNAMIC_LINK_NOT_ACTIVATED : FDL domain is not configured"

after setting up my domain as a Dynamic Link domain, it worked.

Obviously Dynamic Links are being sunsetted, but see this part of the guide for more info on how it affects email link sign in methods.

I do not believe the issue is related to dynamic links in a mobile environment, as I have never used dynamic links in my applications. This may be relevant for web environments, which differ significantly from mobile applications.

[EmanuilM]

@snowluminum Have you received a response from Firebase support?

I have received a response from them. They advised that other developers experiencing the same issue should contact support directly, as each case needs to be reviewed independently. Additionally, they asked for my project IDs to investigate what is happening with their authentication service.

[harveyappleton]

I do not believe the issue is related to dynamic links in a mobile environment, as I have never used dynamic links in my applications. This may be relevant for web environments, which differ significantly from mobile applications.

It solved the auth/internal-error for me on iOS :) I believe under the hood, it uses/relies on Dynamic Links for the handoff from email back to the app, hence why its detailed in the deprecation guide

[EmanuilM]

Did you try it on the Android environment before fixing it? Also, have you ever used dynamic links before in your app?

[snowluminum]

@snowluminum Have you received a response from Firebase support?

I have received a response from them. They advised that other developers experiencing the same issue should contact support directly, as each case needs to be reviewed independently. Additionally, they asked for my project IDs to investigate what is happening with their authentication service.

They responded and said that they are validating the problem

[snowluminum]

If it's of any help, I was encountering the same auth/internal-error on iOS. I then used same code on web (React Native Web), and the network response showed this:

code: 400
reason: "invalid"
message: "DYNAMIC_LINK_NOT_ACTIVATED : FDL domain is not configured"

after setting up my domain as a Dynamic Link domain, it worked.
Obviously Dynamic Links are being sunsetted, but see this part of the guide for more info on how it affects email link sign in methods.

I do not believe the issue is related to dynamic links in a mobile environment, as I have never used dynamic links in my applications. This may be relevant for web environments, which differ significantly from mobile applications.

i may be funny but i have expired domain 🤔

[EmanuilM]

I can say you more) They provided me example app. But the thing is that they resposes take too long (1-2 days)

I received the same message from the support team and i have already provided them with the necessary information. Have they responded to your message?

[snowluminum]

I received the same message from the support team and i have already provided them with the necessary information. Have they responded to your message?

They said that they need more info and asked for 3 more examples

[EmanuilM]

They asked me for three examples and after I provided them, they responded that the issue is not with Firebase servers. They also suggested alternatives, such as using email authentication.

Please keep me updated on their response

[EmanuilM]

Btw until the issue is resolved, I have found an alternative solution by using Supabase auth service. When I receive an internal error from Firebase, I redirect the authentication to the new provider. In this way, users can still use their phone numbers as an authentication method.

I hope this helps you :)