You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We checked this functionality in other countries like Switzerland and Germany but there it is working fine. So it looks like a local problem in Sierra Leone with the Firebase service for sending SMS verification codes.
Sandino opened a support ticket at the firebase support to check if Google has a general problem sending SMS in Sierra Leone. This ticket is still open and we do not have a final result for this.
Now, we are discussing if we can add another authentication method such as email and password, TOTP multi-factor or integrate a custom auth system which was recommended by the Firebase support.
This was the last email from the support team:
Hi Sandino,
We have investigated it and have confirmed the following key points:
Services are available in neighboring regions, indicating that the issue is not related to Google data centers.
Firebase services are healthy and stable.
The problem appears to be localized within a specific region and is affecting only certain carriers.
To ensure the safety and reliability of our services, carriers or entire regions with consistently low SMS success rates may become temporarily unavailable. To continue using Firebase Authentication in this region, I recommend considering using a different authentication method such as email and password or TOTP multi-factor. Alternatively, we also offer the ability to integrate a custom auth system.
Therefore, as much as I'd love to help you, we are not able to solve this.
Thanks,
Jonathan
ssandino
changed the title
[Mobile App Feature]: Authenticate with Firebase using email links if authentication with phone number is not working
[Mobile]: Firebase authentication with email if phone is not working
Nov 9, 2024
Is there an existing request for this feature?
Is your feature request related to a problem? Please describe.
We have at least 2 or 3 mobile phone numbers in Sierra Leone which do get an internal error while "SignupCubit.signupWithPhoneNumber". See https://social-income.sentry.io/issues/5618737947/?environment=prod&project=450715419226[…]m%5D&referrer=issue-stream&statsPeriod=14d&stream_index=2
We checked this functionality in other countries like Switzerland and Germany but there it is working fine. So it looks like a local problem in Sierra Leone with the Firebase service for sending SMS verification codes.
Sandino opened a support ticket at the firebase support to check if Google has a general problem sending SMS in Sierra Leone. This ticket is still open and we do not have a final result for this.
Now, we are discussing if we can add another authentication method such as email and password, TOTP multi-factor or integrate a custom auth system which was recommended by the Firebase support.
This was the last email from the support team:
Describe the solution/feature
We integrate Authenticate with Firebase Using Email Links in case of authentication with phone number is not working.
Describe alternatives you've considered
No response
Criteria for Completion
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: