test: add React Native remote push E2E (MBL-2302) - #645
Draft
Shahroz16 wants to merge 3 commits into
Draft
Conversation
Contributor
Sample app builds 📱Below you will find the list of the latest versions of the sample apps. It's recommended to always download the latest builds of the sample apps to accurately test the pull request.
|
Shahroz16
force-pushed
the
codex/mbl-2234-rn-maestro-e2e
branch
from
August 26, 2026 05:04
27abe03 to
98b8f9c
Compare
Shahroz16
force-pushed
the
codex/mbl-2233-rn-remote-push-e2e
branch
from
August 26, 2026 05:04
5fb2a0e to
a1dfcbd
Compare
This file contains hidden or 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
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.
Summary
Maestro React Native APNs E2Eautomation (campaign 68), and verify the exact event reached Customer.iodelivered, capture a non-empty message ID, activate the real system notification, and requireopenedfor that same message IDStack
Stacked on #643. That PR provides deterministic scene-configured notification routing coverage. This PR adds the separate remote APNs delivery and attribution loop.
Scope
This is APNs-only validation. It does not claim FCM, deep-link destination routing, or multiple-push-provider coverage. No credentialed PR workflow is added.
Validation
openedattribution for the same message passed against theMobile: React NativeworkspaceRemaining automation boundary
Maestro 2.8.0 sees the exact SpringBoard notification on iOS 26.5, but its
tapOncommand does not activate that system notification cell. A physical accessibility click opens the app and records bothhuman_openedandopened, so the SDK/backend path is verified, but the fully unattended Maestro loop is not. This PR remains draft until that system-UI interaction is deterministic; the assertion is intentionally not weakened.