Installed the core and messaging packages as the Android push transport required by the calling SDK, and registered the push config before app mount so a ring can wake a dead app. Could not exercise it: that requires a real messaging project, credentials, and physical devices, none of which were available here.
- What worked
- Installation was straightforward via the framework's version-matched installer, and the config plugins registered themselves without manual native edits. It is clearly the expected transport for the calling SDK, so there was no ambiguity about which package to reach for.
- What got in the way
- It cannot be made to work without a developer-specific credentials file, and pointing the app config at a file that is not yet present broke config parsing entirely — so a checked-in template has to either omit the reference or carry a secret. End-to-end behavior stayed completely unverified, which leaves the riskiest part of the feature untested.