ember-system-alarm-bridge-plugin

Expo config plugin that injects Ember'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.
• Android exact-alarm compatibility: SCHEDULE_EXACT_ALARM through API 32 and USE_EXACT_ALARM on API 33+.

Foreground Alarm Rules

The bridge observes native alarm state and applies Ember'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 30-second 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.

The app schedules one native alarm per occurrence. Android arms step-suppression tracking before each alarm so recent walking can suppress ringing even when JavaScript is backgrounded.

Foreground wake-check bursts use the same native alarm lifecycle on both platforms. The bridge records a burst as audible only after native playback begins, keeps the current alarm alive until it stops, and lets JavaScript start the 10-second retry only after that audible alarm is dismissed or muted.

Android alarm surfaces use a dedicated high-importance full-screen notification channel. The foreground-service notification remains visually interruptive while alarm audio and vibration are owned by the ringing service, preventing notification grouping from suppressing the heads-up or lock-screen surface. In-app sound-only bursts use a separate low-importance channel and do not interrupt the active wake-up check.

Only one alarm may ring at a time. An untouched alarm keeps ringing; Ember does not start fixed-duration bursts behind it. If the active alarm is silenced without opening Ember (for example with a side/lock or volume button), the native bridge stops that alarm and schedules exactly one retry for 10 seconds later. A different scheduled alarm that becomes due while one is already ringing waits in its own 10-second retry loop instead of being discarded. Opening Ember or completing the wake-up check cancels the active session retry, without suppressing independently scheduled alarms.

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)
• startForegroundAlarmSound(alarmId, title, body)
• getAudibleAlarmCount()
• getAudibleAlarmIds()
• 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.