I set up a deep link,

150 views
Skip to first unread message

D.Y Kang

unread,
Jun 16, 2023, 1:09:06 PM6/16/23
to Firebase Google Group
I set up a deep link,
When there are two apps, the first app did not set the deep link related setting in the manifest file, and the second app was set up with a deep link to enter, but only the first app is called.

How to handle this case?

sumitc...@google.com

unread,
Jun 20, 2023, 5:44:42 PM6/20/23
to Firebase Google Group
Hi D.Y. Kang,

To confirm, are you using Firebase Dynamic Links (versus using App Links or Universal Links directly)? Also, which app platform are you having issues with opening the deep-link?

D.Y Kang

unread,
Jun 27, 2023, 5:57:27 AM6/27/23
to Firebase Google Group
I am using firebase dynamic link.
I created two Android apps in one project,
It started with one app, but later, another app was created and two apps were registered in one project.

At this time, the package name of the first app will be located later in the alphabetical sorting order than the one created later. However, in order to apply dynamic linking to those in the back order, I also set it in manifest.xml.

By the way, the order of registration has come to the second position in the google-services.json file. So, at present, it is forced to be in the first position and redeployed and applied.

There is no way to change the order or do it in fiasebase's console.

I don't know if my experience is correct.

2023년 6월 21일 수요일 오전 6시 44분 42초 UTC+9에 sumitc...@google.com님이 작성:

Sumit Chandel

unread,
Jun 28, 2023, 11:30:25 AM6/28/23
to fireba...@googlegroups.com
Hi D.Y. Kang,

In general, it is a best practice to have separate Firebase projects for the different Android apps. Note however it is recommended to have the same Firebase project for different platform versions of an app (e.g. iOS, Android and web), or for a paid and free version of an app for the same platform.

There are more details on the best practices guide here: https://firebase.google.com/docs/projects/dev-workflows/general-best-practices.

That said, each of your Android projects should have their own google-services.json file each pointing to the same Firebase project configuration information, but having their own app specific information in their respective google-services.json files (e.g. package names).

As for configuring the manifest files, for two separate Android apps I would expect that each would have their own individual manifest files containing their own deep-link configurations separately from each other.

More importantly, I wanted to point out that Firebase Dynamic Links is currently not recommended as the service will shut down in the future. More details are available here: https://firebase.google.com/support/dynamic-links-faq.

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/3f243ee2-7686-41a6-922e-3e596a87cf49n%40googlegroups.com.


--
Sumit Chandel
Developer Advocate, Firebase Team
Reply all
Reply to author
Forward
0 new messages