Skip to content
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

[BUG] iOS Notifications being registered to background threads #496

Closed
Spenstar opened this issue Sep 21, 2017 · 3 comments
Closed

[BUG] iOS Notifications being registered to background threads #496

Spenstar opened this issue Sep 21, 2017 · 3 comments
Milestone

Comments

@Spenstar
Copy link
Contributor

Spenstar commented Sep 21, 2017

I noticed that when the cloud messaging system is registered for iOS, it is put on a background thread as seen in the image below:
screen shot 2017-09-20 at 11 23 21 pm

I have tried calling firebase.init() in different parts of the application, but still get this error.

If this could be looked into, that would be great.

UPDATE:

After playing around with this, I have found that this happens when I build the Android version of the application. When the Android build is finished, TNS needs to rebuild the iOS app again for some reason. Once that build is finished and installed on the device, push notifications no longer work on the iOS version.

One workaround (not the most ideal solution) is to uninstall the app from the iOS device and then run tns run ios again. This will install a fresh app and push notifications work again.

With that in mind, I'm not sure if this is an issue with the build process of NativeScript, or if this can be fixed within the Firebase plugin.

@b4rtt
Copy link

b4rtt commented Oct 8, 2017

@Spenstar Hi, same problem here. But uninstall app doesn't help. My app can't get any notification message :/

@rhrn
Copy link
Contributor

rhrn commented Oct 11, 2017

Maybe it would be helpful
evollu/react-native-fcm@a2412b8

@EddyVerbruggen
Copy link
Owner

Thanks @Spenstar!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants