Skip to content

Commit ab82135

Browse files
committed
improved formatting
1 parent 88fa1a6 commit ab82135

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

docs/troubleshooting/authentication/safetynet_phone_sign-in_issue_on_android_devices.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,8 @@ Firebase uses one of the following methods to confirm the authenticity of phone
7777
- [Firebase Phone Authentication (FlutterFire)](https://firebase.flutter.dev/docs/auth/phone/)
7878
- [Using Firebase Auth in FlutterFlow](https://docs.flutterflow.io/authentication)
7979
- [Play Integrity API Migration](https://developer.android.com/google/play/integrity)
80-
:::
8180

8281
Still stuck? Check Firebase logs, test on a physical device, and ensure your API keys and fingerprints are correctly added. Proper configuration of SafetyNet or reCAPTCHA is critical to ensuring phone number sign-in works reliably across devices.
82+
:::
83+
84+

docs/troubleshooting/authentication/troubleshooting_custom_authentication.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Here's an example:
1414

1515
![](../assets/20250430121149388590.png)
1616

17-
## How to Fix Custom Authentication Issues in FlutterFlow
17+
## How to Fix Custom Authentication Issues
1818

1919
1. **Verify Server and API Endpoints**
2020
- Confirm that your server correctly returns JWT tokens for login and sign-up requests. The server's response should include the **authentication token**, **refresh token**, **expiration time**, and **user ID (UID)**.

0 commit comments

Comments
 (0)