Skip to content
Draft
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
updated content
  • Loading branch information
mrdavidorok committed Aug 13, 2025
commit f639283a3e175a178a4d23e6b2f58ddc26d108e6
38 changes: 37 additions & 1 deletion docs/ff-concepts/notifications/push-notifications.md
Original file line number Diff line number Diff line change
Expand Up @@ -282,4 +282,40 @@ Also, ensure that these principals (emails) and their roles are present in the p

Below is a sample image for App Engine Default service account.
![pn-faq-img-2](imgs/pn-faq-img-2.png)
</details>
</details>

<details>
<summary>How do I test push notifications locally in FlutterFlow?</summary>

Push notifications cannot be fully tested in a browser or most emulators — they require a real device with proper push notification service configuration.

**To Test lLcally:**

1. **Use a Physical Device**
- Connect an Android or iOS device via USB or Wi-Fi.
- Notifications do not work reliably in Flutter web builds or most simulators.

2. **Set Up Your Push Notification Service**
- **For Firebase Cloud Messaging (FCM):**
- Add your Android package name and/or iOS bundle ID in Firebase Console.
- Download `google-services.json` (Android) or `GoogleService-Info.plist` (iOS) and add it to your project.
- **For OneSignal:**
- Create an app in OneSignal Dashboard.
- Configure the app ID and platform keys in FlutterFlow.

3. **Run the App Locally**
- Use FlutterFlow **Run Mode** or `flutter run` after exporting code.
- Ensure push notification permissions are requested on launch.

4. **Send a Test Notification**
- **Firebase Console:** Go to **Cloud Messaging** → **Send message** → target your device.
- **OneSignal Dashboard:** Go to **Messages** → **New Push**.

5. **Grant Notification Permissions on Device**
- iOS will prompt the first time; make sure to allow.
- Android 13+ will also prompt for permission.

:::tip
Keep your device connected and reuse the same build for repeated tests to avoid re-granting permissions each time.
:::
</details>