Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.
I have successfully built the phone login screens using Bravo Tags according to the documentation. But there are some points that need clarification to successfully test this, and I'm facing different outcomes while testing different numbers. In no case did I get an OTP successfully.
1. On Bravo Vision (on iOS), I get the popup that the phone login will only work on the final app. Thus, I can't successfully test this without publishing the app.
2. On Bravo Vision (on Android), I don't get any such popup.
Thus, the following cases were tried on Bravo Vision Android only:
- a. "+AABBBBBBBBBB", where AA is the double-digit country code.
- Result: I get to the OTP screen successfully. However, no OTP is received at that number.
- b. "+ABBBBBBBBBB": For single-digit country codes like US, etc, i.e. "+1BBBBBBBBBB" is the phone number for US.
- Result: App hangs and I must force close Bravo Vision.
- c. "+AABBBBBBBBB": For single-digit country codes, but trying "+01BBBBBBBBBB" i.e. for US.
- Result: "Invalid verification code request."
- d. "BBBBBBBBBB": Leaving out the country code altogether for a 10-digit number.
- Result: "Invalid verification code request."
- e. "ABBBBBBBBBB": Leaving out the + at the beginning of the country code.
- Result: "Invalid verification code request."
I have also tried testing this with the APK, as specified in the documentation. I am facing the same results. How can I successfully test this by receiving OTP? Is there some registration step that needs to be done or service that I must sign up for to enable SMS sending?
2 replies
Hi ,
On iOS Bravo Vision, we don't use a real phone login, but a "fake" login that you can go through by inserting any phone number in a valid format.
Regarding valid phone numbers, you'll need to add the country code with the "+" sign, followed by the phone number. We'll investigate the issue you're having with single-digit phone numbers, but you can test which phone formats are allowed in Firebase by inserting a test phone number and code in your Firebase project.
In Firebase it looks like both +AA and +A formats are allowed. In the Android APK, I was able to get to the OTP verification screen only because the numbers I used were test phone numbers. Using any other number results in the app hanging and not proceeding to the OTP verification. How to successfully test this in the APK? Or does the app have to go live before a real phone number can be tested?
Wrote something in this thread and want it removed? Request removal
Ask the community on Discord
This archive is read-only. New questions, office hours and product updates now happen in the Bravo Discord.
Join the Discord