Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[expo-notifications][Android] Ensure response is correctly mapped in useLastNotificationResponse hook #28938

Conversation

douglowder
Copy link
Contributor

Why

Fix an omission in #28883 , where notification responses from Android have their data property correctly mapped for the response listener, but not for the useLastNotificationResponse hook.

How

Move the mapping to a utility method, and call that in both places where it is needed.

Test Plan

  • CI should pass
  • Test app with real device should show correct data property in useLastNotificationResponse() result

Checklist

Copy link

linear bot commented May 17, 2024

@douglowder douglowder force-pushed the doug/eng-12137-android-notificationresponsereceivedlistener-not-called-when branch from c676f0e to 8ce35d9 Compare May 17, 2024 04:29
@douglowder douglowder marked this pull request as ready for review May 17, 2024 04:55
@douglowder douglowder requested a review from tsapeta as a code owner May 17, 2024 04:55
@expo-bot expo-bot added bot: passed checks ExpoBot has nothing to complain about and removed bot: suggestions ExpoBot has some suggestions labels May 17, 2024
@douglowder douglowder merged commit 671dfd8 into main May 17, 2024
18 checks passed
@douglowder douglowder deleted the doug/eng-12137-android-notificationresponsereceivedlistener-not-called-when branch May 17, 2024 05:10
douglowder added a commit that referenced this pull request May 28, 2024
@brentvatne brentvatne added the published Changes from the PR have been published to npm label May 29, 2024
douglowder added a commit that referenced this pull request Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot: fingerprint compatible bot: passed checks ExpoBot has nothing to complain about published Changes from the PR have been published to npm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants