B Bubbl Docs

Troubleshooting

The SDK does not boot

Check:

  • The API key is present and belongs to your live Bubbl company workspace.
  • The device has network access.
  • You are using SDK version 4.0.2.
  • You are not overriding endpoint URLs unless Bubbl support asked you to.

Notifications do not appear

Check:

  • Notification permission is granted.
  • Android notification channel is enabled in system settings.
  • Firebase config matches the exact app ID or bundle ID installed on the device.
  • The app forwarded the current FCM or APNs token to Bubbl.
  • The campaign is active and eligible for that API key/device.
  • The SDK is not configured as host-rendered or event-only while you expect SDK default UI.

Firebase payload parsing returns nothing

Check:

  • You are passing the Firebase data payload, not only the notification title/body wrapper.
  • The payload was sent for a Bubbl campaign.
  • The SDK booted before payload handling.

Geofences do not trigger

Check:

  • Location permission is granted.
  • Background location is granted if you expect behavior while the app is not visible.
  • The test location is inside a campaign geofence.
  • Campaign dates, segments, and eligibility rules match the device.
  • On iOS, the app was not force-quit by the user.

Diagnostics shows pending events

A non-zero pending count can be normal while the device is offline or the SDK is waiting to flush. Call flush() during testing, then check diagnostics again.

If the pending count keeps increasing while the device is online, capture device logs and diagnostics for Bubbl support.

Event replay

Use event listeners and diagnostics that are documented for your installed SDK version. If you are following a support-only or pre-release instruction, confirm the SDK package version with Bubbl before relying on it in your live app.