Troubleshooting

What the common symptoms mean and how to fix them, from a start that fails to pushes and geofences that don't arrive.

Start with Bubbl.diagnostics() and Bubbl's own log: see Testing and diagnostics. Most problems show up in active, registered, hasPushToken or lastError.

Turn on debug logs#

Bubbl only logs warnings and errors by default. To see everything it does, start it with logLevel set to debug while you investigate, then set it back:

BubblOptions(baseUrl = "https://api.bubbl.tech", logLevel = BubblOptions.LogLevel.DEBUG)

BubblOptions(baseUrl: "https://api.bubbl.tech", logLevel: .debug)

const BubblOptions(baseUrl: 'https://api.bubbl.tech', logLevel: BubblLogLevel.debug)

{ baseUrl: 'https://api.bubbl.tech', logLevel: 'debug' }

Bubbl logs natively, also from Flutter and React Native apps:

• Android: Logcat, tag BubblSDK.
• iOS: the unified log, subsystem tech.bubbl.sdk: the Xcode console, or Console.app filtered on the subsystem.

With debug on, you'll see lines such as:

• Geofence check: each time Bubbl decides whether to fetch geofences, with the result (Updated, Unchanged or NotDue), or no location fix when the phone has no position.
• Watching N geofences with Play services on Android, once the geofences are set.
• Geofence entry sent: N notification(s) to show (or exit) when the phone crosses a geofence.
• Since 5.0.1, The Bubbl server answered HTTP … to … requests in a row when the server keeps failing (3 requests in a row). This one is an error, so it shows at the default level too.

Leave debug off in release builds.

Bubbl doesn't start#

On Android, the native Bubbl.start throws these as an IllegalArgumentException, so they show as a crash in development. On iOS, and in Flutter and React Native, they're logged and Bubbl doesn't start.

The device doesn't register#

Registered, but nothing arrives#

Push#

Geofences#

geofences is 0#

geofences in diagnostics() is how many geofences Bubbl got from its last fetch. It's 0 before the first fetch, and after a fetch that found nothing. It isn't how many the operating system is watching. Check these in order:

1. Location. With location off for Bubbl (locationEnabled false) or no location permission, Bubbl doesn't fetch at all.
2. Distance. Bubbl asks for the geofences within 5 km of the device, nearest first, and gets at most 50. A device more than 5 km from every campaign location gets none. On an emulator, give it a position near your locations: see Positions on emulators and simulators.
3. The campaign. Only running geo campaigns are served: started, not paused and not ended, with at least one notification that's sent on entering or on leaving. A campaign with no notification attached, or one that hasn't started yet, adds nothing.
4. The key. The SDK API key must be the workspace whose campaigns you expect. Another workspace's key sees none of them.
5. Timing. The app fetches again every 15 minutes, or sooner once it has moved 2.5 km. A change to a campaign can take up to 5 minutes to reach the server's answers. Until then, the device keeps the set it last fetched, even an empty one.

To see each fetch on Android, turn on debug logs: Bubbl logs Geofence check: with Updated(geofences=…), Unchanged or NotDue (not time to fetch yet), or no location fix when the device has no position.

Flutter and React Native#

Still stuck? Collect Bubbl.diagnostics() and the native log at debug level before contacting Bubbl support.