Morgan Chen

Duplicate of #5503. We've never been able to repro this crash, but had something similar happen with a partner who was using a custom version of sqlite3.

Have you tried the steps described in https://github.com/firebase/quickstart-js/issues/209?

Hey @sspogra, this is crashing in `_Block_release`, which is usually a sign of memory corruption. Can you try reproducing this crash with memory diagnostics on?

Looks like you're running into the default universal links behavior. You can override the open-in-app behavior by long-pressing the link and tapping "Open in Safari".

The "Open in Safari" behavior is supposed to be provided by the system, and if it opens Safari successfully then your app's code shouldn't be executed at all. Can you...

If it's a bug in iOS, we have no ability to fix it in the SDK because link opening in Safari should bypass your app completely.

I suspect there's something else going on here, since I wasn't able to find a substantial amount of similar reports, which would be expected for a universal linking Apple bug....

You can also try to see if you can replicate this behavior in our [Dynamic Links quickstart](https://github.com/firebase/quickstart-ios/tree/master/dynamiclinks).

@siddeshpillai are you able to receive notifications sent directly via APNs?

It does solve a real problem, but it got lost in the auth/firestore cross team comms. I'll try to pick this up again in Q1.