Open armandoxxx opened 2 years ago
I successfuly subscribed to topic on both flatforms. I had to implement timeout which resets every time registered event is called. After all register events are done subscribtion to topic can be executed. Check angular app.compontent.ts for the latest code. Maybe update to docs: Call subscribe() method after all register events are complete. I dunno why this is not explanied in the docs.
Thank you so much armando! It's now working for me as well, when I subscribe to the topic after registering :smiley:
Bug Report
IOS notifications on subscribed topics are not received by IOS device on first application startup. You have to unsubscribe in subscribe to the topic again to make it work.
Expected Behaviour
When debuging application you start it up, close it and then push FCM message through. Notification is not received or shown on device.
Actual Behaviour
On first start of app when debuging, nothing happens when FCM push message is sent although log messages say that app is subscribed to topic. If you open app, unsubscribe from topic and subscribe to it again, all newly sent push messages appear from now on.
Reproduce Scenario (including but not limited to)
I've created this project to test it. https://github.com/armandoxxx/AngularWithCordova But use your own google-service.json and GoogleService-Info,pllist settings Checkout project, read README cause there are some strange things to consider before build. go into MobileApp folder. Do what readme says you have to do to start app. cordova build ios run app with XCode check logs
Steps to Reproduce
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Ipad with latest IOS 15.x
cordova info
PrintoutSample Push Data Payload
FCM v1
FCM legacy
Sample Code that illustrates the problem
Maybe there is something wrong with how Push plugin is initialized in Angular app app.component.ts
Logs taken while reproducing problem
2022-04-08 12:20:58.527295+0200 MobileApp[23851:695703] Subscribed to [user_topic] this says that app is subscribed to topic.
So either this is a bug or my init process is wrong. yes i'm initializing everything on deviceready main.ts