Testing and Diagnostics

Use this checklist to prove that Bubbl is correctly installed before releasing your app.

Minimum test flow

1. Boot the SDK with your live Bubbl API key.
2. Call diagnostics() and confirm the SDK reports version 4.0.2.
3. Grant notification permission and location permission.
4. Register a real FCM or APNs token.
5. Call refresh() and confirm it succeeds.
6. Call refreshGeofence() with a test location supplied by your Bubbl contact.
7. Send or simulate a Firebase data payload.
8. Open a notification and confirm CTA, media, or survey behavior if your campaign uses those features.
9. Call flush() and confirm no unexpected pending queue growth remains.

Diagnostics fields

Diagnostics include:

• SDK version.
• Platform.
• Whether the SDK has booted.
• Pending event count.
• Push token suffix, when a token has been registered.

Do not send full push tokens or user identifiers in support screenshots unless Bubbl support explicitly asks for them.

Logs to collect

For a support ticket or smoke test, capture:

• SDK version and package version.
• App ID or bundle ID.
• Device model and OS version.
• Bubbl API key suffix only, not the full key.
• Permission state for notifications and location.
• Diagnostics output.
• Build logs for install issues.
• Device logs around boot, token forwarding, payload handling, and geofence refresh.

Useful test commands

Android device logs:

adb logcat

Flutter run with API key:

flutter run --dart-define=BUBBL_API_KEY=<YOUR_BUBBL_API_KEY>

React Native Android run:

npx react-native run-android

iOS must be tested on macOS with Xcode and a valid provisioning profile for push.