This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 448
Still problems with push messages #225
Milestone
Comments
Perhaps #222 solves this issue. I'm doing my best to review and merge that asap. |
Require the plugin before application.start, call init in application.on(loaded... The null is not an object in my app was caused because iOS sharedApplication singleton was captured before application.start. For android this wont't work as foregroundActivity in the core modules was altered and for android it seems best to call firebase.init before application.start |
EddyVerbruggen
added a commit
that referenced
this issue
Nov 23, 2016
EddyVerbruggen
added a commit
that referenced
this issue
Nov 23, 2016
Please update to 3.8.4 which includes @PanayotCankov which (at least for me) work really well. |
EddyVerbruggen
added a commit
that referenced
this issue
Apr 18, 2017
EddyVerbruggen
added a commit
that referenced
this issue
Apr 18, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi, release 3.8.3 fixed some issues but there are still problems. When I deploy my iOS app the first time, I get push messages, however when there are an existing app on the phone or if I launch the app fresh on the phone, messages are not received, seems to be more "null is not an object" errors
this is the xcode logs when I do a second run... messages are not received
The text was updated successfully, but these errors were encountered: