6 Commits

Include renames

Author	SHA1	Message	Date
chliangGoogle	44a2bc0db0	Adding enable/disable property to FCM token auto Initialization	2018-01-24 11:57:27 -08:00
Ryan Wilson	7386f00178	Replacing FIR_SWIFT_NAME macro with NS_SWIFT_NAME. (#476) ... * Replacing FIR_SWIFT_NAME macro with NS_SWIFT_NAME. This pushes the minimum Xcode version to 7.3, as NS_SWIFT_NAME was limited before that version (which is why the macro was introduced in the first place). * Fixed FIRMessaging header	2017-11-28 06:59:07 -08:00
Riz	2b40693be4	Add simpler delegate method for FCM tokens (#375) ... 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.	2017-10-12 16:09:07 -07:00
Riz	91fee9d66d	Add comment about how multiple senders are supported (#158) ... This is a slight tweak to the block comment describing `-retrieveFCMTokenForSenderID:completion:`, to more explicitly mention that this can be used to support the scenario of allow multiple senders to send notifications to the same client app.	2017-07-31 15:23:53 -07:00
Riz	bc4667ff58	Fix formatting inconsistencies in Messaging header (#61) ... The header comments are directly reflected in Firebase documentation, so this improves that as well.	2017-06-02 14:03:17 -07:00
Paul Beusterien	98ba64449a	Initial	2017-05-15 12:27:07 -07:00