DynamicLink's bare initializer was not intended to be publicly available. Marking it as NS_UNAVAILABLE hides it from both ObjC and Swift callers; resolves#10000.
* Fix implementation.
Fix unit tests.
Remove duplicate method.
Add comment.
Add unit tests.
Use deprecated annotation.
Fix the comment.
* Make changes additive.
* Address review comments.
* Review changes.
* Check data before serialization.
* Minor fix.
* Post rebase fix.
* Post rebase fix 2.
* Fix styling.
* Fix type.
* Post rebase fix.
* Remove kClientID.
* Code review comment addressed. Get rid of code duplication.
Fixed broken callback to AppDelegate after retrieving a dynamic link during fresh app start.
The AppDelegate call was broken in PR : #6517
Reverting to the old implementation of dynamic link passing to App delegate with changes to remove iOS 9 checks.
Using new "openURL" method instead of the deprecated one.
Clean up in the sample app pod file.
Removing client id usage in api call and respective checks
FDL SDK was using client id passed in FIROptions to make API calls. From backend side, we no longer needs client id to be sent. So removing the client id usage in FDL SDK along with parameter no null checks.
-Removed the usage of Client id from FIROptions.
-Removed non null parameter checks for client id.
-Deprecated 1p API method setUpWithLaunchOptions::apiKey:clientID:urlScheme:userDefaults: and added setUpWithLaunchOptions::apiKey:urlScheme:userDefaults:
-Removed Client id usage in Unit tests.
* Fix for internal bug b/154589338
Most of the times, when the app is cold started, we are making api calls to:
https://firebasedynamiclinks-ipv4.googleapis.com/v1https://firebasedynamiclinks-ipv6.googleapis.com/v1
Until we get a successful response. But sometimes, if the device doesn’t have support for v6 endpoint and if the v4 endpoint doesn’t retrieve a valid dynamic link, it will return error. This mostly happens when user directly goes to App Store and installs an app which has fdl sdk integrated.
For dynamic links, we want the app to retrieve the pending dynamic link on the very first start of the app after install so that 3p developers can deeplink to a particular page in the app. If the pending links retrieval failed during the first start, there is no point in retrying the retrieval during next restart since it could result in an un expected deep link for the user when they opens up the app for subsequent restarts (if a valid dynamic link is returned).
Paul Beusterien