Meteor-Community-Packages / Meteor-Community-Packages/raix-push
Android Client no longer registering after upgrade
- Dominant language
- JavaScript
- Stars
- 505
- Forks
- 191
- PR merge metrics
- No merged PRs in 30d
Description
After upgrading from Push 2.6.12 to 3.0.0 my Push notifications stopped working on Android.
When I run my app in a browser, the logging (with Push.debug=true) shows:
```
Push: Settings userId "qwertyuiopasdfghj" for app: mnbvcxzlkjhgfdsap
```
When I run my app on Android no such message is shown.
In both cases (logged in on Android or in Browser) when I `Push.send` I get:
```
Push: Send message "blablabla" via query { userId: 'qwertyuiopasdfghj' }
Push: Sent message "blablabla" to 0 ios apps 0 android apps
Push, GUIDE: The "Push.appCollection" is empty - No clients have registred on the server yet...
```
This is intended when logged in on the browser, but not when logged in via the Android app.
The upgrade to Push 3.0.0 included an upgrade from Meteor 1.1 to 1.2 and the inclusion of Crosswalk. Removing Crosswalk didn't help.
What keeps my Android client from registering?
Contributor guide
Research direction
Start by reproducing with Push.debug=true and compare the Android and browser registration paths around Push.send; inspect the upgrade from Push 2.6.12 to 3.0.0, including Meteor 1.2 and Crosswalk. Done means Android registration produces the missing settings log and Push.appCollection contains the client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, javascript
- Domain
- backend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100