Notifications don't open app since SDK45 (Android)

Summary

I upgraded a managed app from SDK44 to SDK45 and now, when a notification is received while the app is in background, touching the notification in Android doesn’t open the app as it used to with SDK44. The listener is called and executed, but the app UI is not shown.

This happens both in Expo GO Android and in the native Android app. When the same code is run in Expo GO Apple it correctly opens the app.

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

Android

SDK Version (managed workflow only)

45

Environment

expo-env-info 1.0.3 environment info: System: OS: Linux 5.17 Pop!_OS 22.04 LTS Shell: 5.1.16 - /bin/bash Binaries: Node: 16.14.2 - /usr/bin/node npm: 8.5.0 - /usr/bin/npm npmPackages: expo: ^45.0.0 => 45.0.4 react: 17.0.2 => 17.0.2 react-dom: 17.0.2 => 17.0.2 react-native: 0.68.2 => 0.68.2 react-native-web: 0.17.7 => 0.17.7 npmGlobalPackages: eas-cli: 0.52.0 expo-cli: 5.4.4 Expo Workflow: managed

Reproducible demo

This is the listener:

Notifications.addNotificationResponseReceivedListener(response => {
console.log(`received notification "${response.notification.request.content.title}"`);
});

[Kudo]

i’m sorry that we might take longer time to release the fix. i found a regression issue from my fix. will try to find a solution and anyway, will keep the status updates here.

[amagnolo]

sorry i was busy for next sdk development and didn’t get a chance to look it this week. will try to do it these two days.

Nothing personal Kudo, but this order of priorities is one of the biggest hindrances of Expo for the adoption in business environment. You’re often too concentrated on delivering timely “best new things” and neglecting making existing stuff work right. Expo SDK45 was released almost 2 months ago and was completely unusable for anyone employing notifications on Android. It was probably never tested with current Android OS version before release. What’s worse, this bug and its regressions (still open) are not even mentioned in the release notes known problems, making anyone upgrading their apps from previous SDK having to find it out the hard way.