Dynamic Link received event gets triggered every time on resuming app from background in latest Android devices with Android OS version 9

[Sanket Kale]

Hello,

I have a firebase project made with Unity 2019.2.0 and recently I upgraded to firebase version 6.8.1. With the upgrade, I am seeing a weird issue where the Dynamic link received event is called every time the app is resumed from the background in the latest Android devices with the Android OS version 9. This used to work with the same Unity version but older firebase version 5.4.4 and, it seems to work as expected on the iOS app of the same project but in the new Android devices I am seeing this issue of continuous call of Dynamic link received event and app resume. 

I also saw an issue raised on the Quickstart examples of firebase (https://github.com/firebase/quickstart-unity/issues/502) raised about a few months ago and I seem to experience the same with the latest version 6.8.1. Now, the solution is not mentioned there and the person who raised the issue also seemed to have abandoned the thread.

Could somebody from the firebase team please tell me why could this be happening? And, most importantly how to solve it?

Please reply sooner, I have an app update to roll out and this issue is a blocker for us.

I look forward to any help regarding this.

Thanks in advance,

Sanket.

[Rick Knowles]

Hi - did this get resolved at all ? I've hit the same problem, but with Firebase 6.13.0. Similarly it calls the event on every wake and some scene changes too. 

How did you get around it Sanket ? 

Thanks in advance.

Rick Knowles

[Sanket Kale]

Hi Rick,

Actually, it hasn't been resolved as of yet. I chased the Firebase support team for this, but they asked me to reproduce it with the Firebase's sample project available on GitHub. Now, I couldn't reproduce the issue with the sample project but I am still having the issue with my project.

Temporarily, I have setup a work around where I am saving the previous URL in a class variable and checking if the new URL is the same as the previous one. If the URL is same as the previous one then I ignore it. Its a dirty work around with its own limitations but works against the horrible issue of same behavior happening again and again on app resume. Even the guy who had raised this issue the first on GitHub also resorted to this after spending days together with the Firebase support team on explaining them the issue.

[Rick Knowles]

Ok that's good to know, thanks. I've worked around this temporarily by downgrading my version of firebase to 6.4 (which works fine), after trying 5.4, 6.0, 6.6, 6.8, 6.10, and 6.13. It failed on every version I tried after 6.4 and worked on every version I tried including and before it. 

Would really love someone in firebase team to pick this up now and actually get it fixed. You know the versions of the phone OS to test on, the version of the code it started in and what the effect is ... If that's not enough to get started on it, I don't know what is. Having to reproduce this into a sample project is frankly busy work, and more suitable to expect from bug reports to an open-source project than a vendor backed paid product.