Charlie Cruzan

Hey @okeybond, does this happen on a blank `expo init` project (after building the apk, of course)? Are you sure the binary version of the app is on SDK 35?

This seems likely to be related to the legacy Updates code, which has been replaced with `expo-updates`, so if you're seeing this problem please upgrade to SDK 39 or 40,...

Closing since this is expected behavior

@Rohansi I'm a little confused- after adding `showInRecents: true`, what's the issue?

Is this only in snack? does the project work locally?

`addNotificationResponseReceivedListener` is triggered when you _interact_ with the notification. Since tapping the notification isn't part of your reproduction steps, could you confirm that the listener isn't triggered even after tapping...

The first reproduction in Expo Go is a known limitation, but I just tested in a standalone version by running `expo run:android` and `eas build`, and I'm seeing the alert...

I used the example from the docs: https://docs.expo.dev/versions/latest/sdk/notifications/#api, on a real device (oneplus, Android 10)

Hm, I'm really not sure what's happening here... If I run the app with `expo run:android --variant release`, press the button to trigger a local notification, kill the app, tap...

Thanks for letting me know! For now, please rely on the workaround I shared above: ``` const lastNotificationResponse = Notifications.useLastNotificationResponse(); React.useEffect(() => { if (lastNotificationResponse) { alert("response"); } }, [lastNotificationResponse]);...