* Update Auth version to 4.3.0
* Revert "Removes user meta from public API (#308)"
This reverts commit 1602391bf8.
* Revert "Removes metadata from swift sample (#318)"
This reverts commit 804ff523a2.
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.
* 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.
* Modifies unit tests to accommodate event ID check
* Extracts event ID from outgoing URL
* Addresses comments
Checks that the URL is rejected by the callback matcher without the event ID.
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 .
* Removes canHandleURL from FIRAuthInternal
Removes canHandleURL from FIRAuth_Internal and makes small modification to FIRPhoneAuthProvider unit test.
* Addresses comment
* Delete an app from Database when deleted in Core.
When a FIRApp is deleted in Core, it should also be deleted from
the instances array in Database.
See #160 for more details.
* Add tests for deleting databases.
* Add call to clean up deleted FIRDatabase instance.
Ivan