Foreground Service notifications arriving as normal notifications?

[brimby]

My app is running on an Expo dev build on an Android device. I am registering a foreground service at the very top of my index.jsx (not in a component) and attaching trigger (alarm) notifications to it. My notification arrives as a normal notification that I can swipe away etc instead of an on-going/long-running task. Is there some permission I need to use? (I didn't include EXACT_ALARM in the manifest yet, but I used openAlarmPermissionSettings() to switch the permission on during testing.) Is it a problem that I'm using triggers and/or the AlarmManager? Here is my out-of-context notification code, but I can provide better details if there isn't a glaring issue with what I'm doing or that I'm totally misunderstanding what a foreground service does:

          const trigger = {
            type: TriggerType.TIMESTAMP,
            timestamp: triggerDate.getTime(),
            alarmManager: {
              allowWhileIdle: true,
            }
          }

          notifee.createTriggerNotification({
            id: `${dayStr}|${startHour}|${startMinute}|${key}`,
            title,
            body,
            android: {
              channelId: 'badger',
              showChronometer: true,
              chronometerDirection: 'down',
              timestamp: countdownDate.getTime(),
              asForegroundService: true,
            },
          }, trigger)

And here is the registering of my service at the top of index.jsx:

notifee.registerForegroundService((notification) => {
  return new Promise(() => {
    // nothing yet
  })
})