[docs][notifications] Add Android and iOS notification object examples #31211
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Aman Mittal <amandeepmittal@live.com>
amandeepmittal
approved these changes
Aug 29, 2024
betomoedano
deleted the
@betomoedano/add-platform-notification-examples
branch
behenate
pushed a commit
that referenced
this pull request
Sep 30, 2024
#31211) # Why The PR adds examples of notification objects for both Android and iOS platforms when using addNotificationReceivedListener. These examples highlight key structural differences: Android uses a nested structure with FCM-specific fields, while iOS has a flatter structure with APN-specific elements. # How Create a [minimal expo notifications app](https://github.com/betomoedano/expo-notifications-app.git) integrating FCM v1, create development builds for Android and iOS using EAS # Test Plan Register both devices to receive push notifications, get the tokens, and trigger notifications using [Push Notification Tool](https://expo.dev/notifications) Paste notification object examples and run docs locally. <img width="1487" alt="image" src="https://github.com/user-attachments/assets/02dfce45-2b7d-4baa-9bbc-5348c45f1f83"> <img width="1191" alt="image" src="https://github.com/user-attachments/assets/054d1e33-d083-4807-ba9d-6f420311d444"> <img width="1181" alt="image" src="https://github.com/user-attachments/assets/7b52e7da-6ec6-4883-ae8f-34606c6f0cd2"> # Checklist - [x] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [x] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). --------- Co-authored-by: Aman Mittal <amandeepmittal@live.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
The PR adds examples of notification objects for both Android and iOS platforms when using addNotificationReceivedListener. These examples highlight key structural differences: Android uses a nested structure with FCM-specific fields, while iOS has a flatter structure with APN-specific elements.
How
Create a minimal expo notifications app integrating FCM v1, create development builds for Android and iOS using EAS
Test Plan
Register both devices to receive push notifications, get the tokens, and trigger notifications using Push Notification Tool
Paste notification object examples and run docs locally.
Checklist
npx expo prebuild& EAS Build (eg: updated a module plugin).