| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |\
| |
| | |
Updating Changelog for 4.1.2 RTDB release
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
* Adds AuthDataResult to anonymous sign in
* Fixes typo
* Addresses comments
* addresses comment on PR
|
| | |
|
| |\
| |
| | |
Using deferred init to ensure that we init FEmptyNode only once
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
| |
* Make all FIRLogger functions extern "C"
* Make FSTIntegrationTestCase Objective-C++
Keep external interface to FSTIntegrationTestCase Objective-C
* Add explicit dependency on Firebase/Community/Core from Tests
This fixes a linkage error on a missing _FIRSetLoggerLevel symbol
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Enumerator using generic. Cleaner for .. in .. loop in Swift
So
for childSnapshot in snapshot.children {
you don't need to cast each child. Each cild is already known as DataSnapshot
* Update FIRDataSnapshot.h
* Update FIRMutableData.h
* Update FIRMutableData.m
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* Updates change log for 4.3.2
* Small improvement
* Updates podspec as well
|
| |
|
|
| |
Handles possible errors after linking phone number.
Also sets anonymous ivar to NO if linking succeeded.
|
| |
|
| |
Fixing a bug where isFromAppStore would return YES for TestFlight apps
|
| | |
|
| | |
|
| |\
| |
| |
| | |
fix-reason-parameter
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
* Updates the changelog for M20.
* Updates podspec version
* uses correct single quote character
|
| | | |
|
| |/
|
|
|
| |
Also fixes a crash in the Auth sample app in an error case.
This addresses *Auth* part of #385 .
|
| |
|
| |
This isn't referenced anywhere internally or externally.
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Update Auth version to 4.3.0
* Revert "Removes user meta from public API (#308)"
This reverts commit 1602391bf8a9b6d3247716e3bf7b9f27dec8d2b6.
* Revert "Removes metadata from swift sample (#318)"
This reverts commit 804ff523a20072fb958e9137c76b9c0e14dda870.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
FCM's swizzling of the user notification center currently swizzles only one of the two optional delegate methods (userNotificationCenter:willPresentNotification:withCompletionHandler:), but not the other (userNotificationCenter:didReceiveNotificationResponse:withCompletionHandler:).
The didReceiveNotificationResponse, if implemented by the delegate, is the sole receiver of all user action on a notification, including simply tapping on the notification itself. Prior to this change, if the developer had implemented didReceiveNotificationResponse, then FCM would not be able to collect this event for analytics.
Additionally, I changed the logic in FIRMessagingRemoteNotificationsProxy to check whether these methods are actually implemented before swizzling them. It was always swizzling, which meant it was adding an implementation if the method didn't exist. This would confuse iOS into thinking the developer did implement these methods and NOT fall back to delivering the notifications to the application delegate.
With this change, if the developer did not implement these methods, then FCM will not swizzle those methods. That keeps the behavior true to what the developer intended.
|
| |
|
|
|
|
|
|
|
|
| |
* Fixes reference docs
Fixes reference docs for FIRAuthErrorUserInfoEmailKey.
* Modfies error code
Modifies the error code where the FIRAuthErrorUserInfoDataKey key is set.
|
| |
|
|
| |
applied more consistently now. (#325)
|
| |
|
|
| |
Initial release of Firestore at 0.8.0
Bump FirebaseCommunity to 0.1.3
|
| | |
|
| |
|
|
|
|
| |
* Disambiguates known errors from web context
- Disambiguates known errors possibly returned by verifyPhoneNumber:UIDelegate:completion:
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Adds operation to verify PhoneNumber requests
* Improvements and unit tests
* Fixes typo
* Addresses comments
- Removes the FIRAuthOperation class.
- Defines the FIRAuthOperationType as an enum in a class of the same name.
- Passes the FIRAuthOperationType value down to the verifyPhoneNumber RPC where it is translated to a string.
* Fixes unit tests
* Actually fixes the unit tests.
|
| |
|
|
|
|
| |
* RTDB Changelog for v4.1.0
* Update CHANGELOG.md
|
| |
|
|
| |
- Adds Swift stubs for the new API.
- Shows the `isNewUser` bit in the sample app.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
* Removes user meta from public API
* remove unused import
removes unused import
* Removes Swift Name
|
Paul Beusterien
Sebastian Schmidt
Zsika Phillip
Gil
Ibrahim Ulukaya
Ryan Wilson
davidair
Ivan
Xiangtian Dai
Riz