bonk-system-alarm-bridge-plugin

Expo config plugin that injects Bonk's native alarm bridge into the mobile app.

What It Adds

• iOS AlarmKit bridge source (IOS26AlarmBridge.swift).
• Objective-C React Native module declarations (IOS26AlarmBridge.m).
• Android AlarmManager bridge source (SystemAlarmBridgeModule.kt, receiver, scheduler, and store).
• AlarmKit usage description in the iOS Info.plist.
• Xcode project source-file wiring for the generated bridge files.
• Android manifest permissions/receiver wiring and React Native package registration.

Foreground Alarm Rules

The bridge observes native alarm state and applies Bonk's foreground rules immediately:

• If the app is not active, alarms are left to ring normally.
• If the app is active and the mission is complete, alerting alarms are stopped.
• If the app is active and the user has interacted within the inactivity threshold, alerting alarms are stopped.
• If the app is active but the user has been inactive long enough during a wake session, the alarm is allowed to ring.

On Android, one root alarm is scheduled per wake session. The native receiver schedules the next tick in the alarm chain before deciding whether to show or suppress the current notification, so a foreground-suppressed first alarm can still produce the next ring after the app closes.

The JavaScript app keeps the native bridge updated through setForegroundAlarmContext.

Audible Alarm Counting

The bridge records an audible alarm ID only when the alarm reaches alerting state and is not suppressed. JavaScript can also explicitly record the trigger alarm when the app opens from an already-ringing alarm.

Available native methods include:

• setForegroundAlarmContext(payload)
• getAudibleAlarmCount()
• recordAudibleAlarm(alarmId)
• resetAudibleAlarmCount()
• getAlertingAlarmIds()
• stopAlertingAlarms(alarmIds)
• cancelSystemAlarms(alarmIds)

Packaging

The mobile app may consume this plugin from npm or from a local tarball. When using the local package, repack after source changes:

npm pack

Then update the mobile dependency or lockfile integrity as needed.