5/16/2023 0 Comments Massive dynamic link in iconboxSee the screenshot for more details: EDIT1: the web-app's firebase. Create a new variable called dynamiclink (or whatever) Click custom and put in the code above (or similar) Now you'll see dynamiclink in your UI selector. After this setting up Dynamic Links with a custom domain attached to the second Firebase Hosting site worked flawlessly. However, I'm not sure why the Custom Domain configuration didn't work and why it would be the default if there are such complications with projects with existing Hosting configurations and custom domains. The first default one for our web-app and the second one for Firebase Dynamic Links. Using works for me as a workaround for now. This is a little less prominent that I would have liked (as I didn't find it for quite a long time). The tooltip says "or a free Google-provided domain (for example, )" at the end. Update on this: I figured out that I needed to add the subdomain to the page.link URL. I'm happy at this time to use a page.link link, I just need to create a Dynamic Link and get unblocked on this task, but I can't figure out any way in the console to allow me to do that either. Clicking the Check Again button just takes me back to the same error in the first image above. This links to the docs for manually configuring hosting for dynamic links which has some steps that I've already completed. If I manually remove disabled from the Continue button, then I get this error message: I tried using my naked domain instead of but that didn't help. The dynamic links are working fine, and as far as I can tell from all the official documentation, just adding the UTM values in the final optional step when creating dynamic links should cause those values to be sent along with the dynamiclinkappopen event. Note that I have the rewrite to /index.html because I have an Angular Single Page Application hosted at No matter what I do, I keep getting this error and the Continue button stays disabled. I order to try to work around this, I went to my project and added the suggested Hosting configuration and deployed it.Įven after waiting an hour, I keep getting the same error and I don't understand what to do. Put links under a subpath to avoid conflicts with existing content. It looks like you already have content served on this Hosting site. It seems to me that adding the /link path prefix here should accomplish that? But after making that change, I get the same error message. So this message seems to indicate that I need to "Put links under a subpath". Unfortunately, while they provide some helpful examples, they don't explain how to resolve my issue in a way that I can understand. It looks like the docs for custom domains were updated today. However that no longer appears to be an option when enabling Dynamic Links for a new project today. I've created Firebase Dynamic Links in other projects before using the page.link URL prefix (the only option at the time).
0 Comments
Leave a Reply. |