| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
| |
When subscribeToTopic or unsubscribeFromTopic are called, they should
not be passed in with the prefix "/topic/". Calling those functions with
a string prefixed with "/topic/" will now print a warning.
|
| |
|
|
|
|
| |
(#1094)
* remove a call that is triggered by IID, but no longer possible once we remove the deprecated method in IID
|
| | |
|
| |
|
|
|
|
| |
This new delegate method will be called generally once per app start, to always provide a current token. This token may change over time. This simpler method makes integration much simpler, as:
* Developers no longer have to check for a current token using the `.fcmToken` property, and also check for token changes using the `-messaging:didRefreshRegistrationToken:` delegate method.
* There is a single code path for when a token is available, making operations that depend on a token being available easier to implement. For example, this is the right method to always upload your FCM token to your application server, or to subscribe to topics, etc.
|
| |
|
|
|
|
| |
This removes the `FIRMessaging_FAIL` macro which was using `__builtin_trap()`, and replaced with `NSAssert` calls. These `NSAssert` calls may not get called in release builds, and so we also log them with FIRLogger error messages.
The RMQ database open error result code is now parsed and included in the error message to help us identify causes for #199 .
|
| |
|
|
| |
This should address the issue filed at: https://github.com/firebase/quickstart-ios/issues/242, where a topic name containing a `%` character was failing. It turns out that the topic name was never being url-encoded.
|
| |
|
|
|
| |
This seems to be a holdover from some old code, and it's not being used anywhere in the component. Plus it's better not to be saving anything in `[NSUserDefaults standardUserDefaults]` as that is the developer/app's domain.
Also renamed the messaging code while I was in there to be something meaningful ("000" → "PrintLibraryVersion").
|
| |
|
|
| |
Currently Messaging will use the most recent FIRApp configured which
isn't obvious. This will limit it to only the defualt FIRApp.
|
| | |
|
| |
|
| |
Maybe it was already swizzled, or some other issue. Either way, it would be good to log this error, as it might help us / developers diagnose an issue.
|
| |
|
Chen Liang
Alex Ames
Riz
Ryan Wilson
Paul Beusterien