You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which blocks initialization of self.pubsub - however when this is removed, there appears to be no problems. Topics work fine on a standalone watchOS after removing these preprocessor statements.
Is there any particular reason as to why? I'm assuming something else is not working properly with notifications is why - I will gladly help update the code if need be to get this working, as topics are something we need on our end.
The text was updated successfully, but these errors were encountered:
Thanks @jlandrum Good catch on the issue. Yes the topic subscription should be working on watchOS and the macro is not correctly set.
The reason we set it for now is that to prevent direct channel from running as it's not available in watchOS, so uncomment it will have a lot of unexpected code from running the resources. Feel free to comment out the macro for the quick fix for now, I will kick off a PR that refactors the pubsub to be called without relying on direct channel logic.
If you attempt to sub to a topic, the callback never calls indicating a success or failure.
The reason is due to
self.pubsub
being undefined, and a message is being sent toself.pubsub
with the completion without a null check:firebase-ios-sdk/FirebaseMessaging/Sources/FIRMessaging.m
Line 781 in ad06c60
There's this line:
firebase-ios-sdk/FirebaseMessaging/Sources/FIRMessaging.m
Line 273 in ad06c60
Which blocks initialization of
self.pubsub
- however when this is removed, there appears to be no problems. Topics work fine on a standalone watchOS after removing these preprocessor statements.Is there any particular reason as to why? I'm assuming something else is not working properly with notifications is why - I will gladly help update the code if need be to get this working, as topics are something we need on our end.
The text was updated successfully, but these errors were encountered: