I already have a website in Wix that uses a domain that I owned (e.g www.abc.com). At the same time, I wanted to use Firebase Dynamic Link. Is it possible for me to continue to host my website in Wix using the domain and use Firebase Dynamic Link that is set up to the same domain (using www.abc.com for Firebase Dynamic Link)?
I have the same issue with you. I need use firebase dynamic link to my app or website. But I can't move my website A record to firebase since I still need wix services. So I created a subdomain in my wix a record, and point that a record value to firebase host, either with A host or txt, after a few hours, I am able to use it from firebase. Just remember don't change your original WIX A record. Then you should be able to use subdomain.abc.com as dynamic link, also not mess up with original wix service.
Related
My custom domain https://mysub.mydomain.com is registered to Firebase Hosting correctly and I can create dynamic link with using my custom domain.But 3 warning occurs and IOS dynamic link is not open my IOS App.
If I use google default domain "xxx.page.link" , everything is ok.
The dynamic link has 3 warning(s)
We could not find Android package name 'xxxxx' in your Google project. Learn more.
We could not find bundle ID 'xxxxxxx' in your Google project. Learn more.
There is no configuration to prevent phishing on this domain https://mysub.mydomain.com/example. Setup URL patterns to whitelist in the Firebase Dynamic Links console. Learn more.
Issues about package and bundle should be fixed in firebase console project settings. You need to check that your iOS and android apps listed here have package name and bundle Id.
Last issue warns you about whitelisting your domains so that nobody could create dynamic links for you app passing links to random domains.
To handle it you need to tap on three dots near the add dynamic link button in firebase console and add all you domains (regex accepted) that can be used in your dynamic links.
I went through Firebase Dynamic Link(FDL) official documentation and migration guide but could not find any way to use a custom domain.
All I can confirm is we can customize subdomain but not the domain. i.e we can use https://example.page.link/... but not https://example.com/....
Is it possible to have the custom domain? It would work for me if they're providing custom domain support to premium Google API accounts.
I got an update from Firebase support that they have just released a new update to customize domain in the dynamic link in March 2019. Refer documentation.
BACKGROUND
I have an app that was set up using a default branch domain (ex: my.app.link).
Links were created using my.app.link. Many of these links needed to mirror existing links I have in production (with another linking service that we are migrating off of) that use a format not supported in Branch.io, so I had to work around the issue by using a '-' in place of '.' in the link's path. This is a solution recommended by Branch with the assurance that the '.' would be translated to a '-' on the backend at Branch.io (this appears to work fine).
I recently had a custom subdomain CNAMEd over to custom.bnc.lt (ex: myapp.mydomain.com).
The link settings in the Branch.io dashboard have been updated to use the custom subdomain (change is valid: "Domain is correctly set up and SSL is working.").
ISSUES
All pre-existing quick links still have the old default domain, no clicks register even though they 'work' with the new subdomain.
Duplicating one of these links picks up the new subdomain, but the url that gets created is http, not https (which is the default for any other link we created and there doesn't seem to be a way to choose one protocol or the other, nor can it be updated in the dashboard). This also seems to be causing link clicks to not track in the dashboard.
The fact that we mirrored links from another platform using a workaround (replacing '.' for a '-'), also seems to cause link clicks to not track in the dashboard.
QUESTIONS
How does Branch.io handle link clicks for a quick link that has been set up for an app using a custom subdomain? Does the configured link need to match 1:1 to the link that is clicked on the device?
How can I fix the original links, especially if I can't duplicate them (to pick up the custom subdomain) in a way that gives me a 1:1 match to the previous link I created (since the new link is http and the others are https, as would be distributed in a live/production environment)?
Why isn't Branch tracking link clicks for the x.y.z links that I set up as x-y-z? This aliasing works fine, and seemed to be tracking clicks fine in test.
Amruta from Branch.io here:
1. How does Branch.io handle link clicks for a quick link that has been set up for an app using a custom subdomain?
A: For all Branch links, every time a Branch link is clicked the click is is registered by Branch. Using a custom domain (if configured properly) should not cause any problems in registering clicks on the Branch dashboard neither should using Quick links cause any issues. Also Branch links with either schemes http:// or https:// register link clicks. Having Branch links with http:// scheme should not cause any issues with registering link clicks
2.All pre-existing quick links still have the old default domain
A: The old links created on the app.link will not be updated with your custom domain. If you wish to use links with your link domain, you can create new links with the same link parameters. (PS: both links on the old app.link domain and links on your custom domain should work as before if you still have your App configured to support the app.link domain links.)
3. Duplicating one of these links picks up the new subdomain, but the url that gets created is http, not https
A: At present, the Branch API creates Branch links for custom domains with the 'http://'scheme. This is because we are not sure if custom domains have the SSL certificate and creating links with the https:// scheme would break for such domains. Hence by default, all custom domain links are created using the http:// scheme. There is no direct way to create links using the https:// scheme using the Branch API, the only way you can do it is by manually changing the scheme from 'http' to 'https://'.
4. Why isn't Branch tracking link clicks for the x.y.z links that I set up as x-y-z? This aliasing works fine, and seemed to be tracking clicks fine in test.
I believe, the issue here has nothing to do with your custom domain but is maybe related to a key mismatch. You mention that the link clicks were tracked in the test version of the App, which leads me to believe that your app is still using the Branch key from the test version (key format: key_test_XXXXXXXXXXXXXXX). Please ensure that your App is using the correct key. The simple test for this: When you click on the Branch link, you get the link parameters in your app and the link parameters contain +clicked_branch_link:true. If so, the link click will be tracked on Branch's end.
If you still continue to face issues, you could write to integrations#branch.io and our team would be more than happy to help you resolve the issue.
I'm trying to authenticate a desktop application with OAuth. I already asked a question, but I deleted it as I discovered that the method was obsolete (integrated web view).
The idea is to open the browser and then have the page call back my application with a custom:// URI scheme.
Of course it doesn't work, Google asks that the scheme contains a dot (like com.org.myapp), but the native app can only have a fmp:// uri scheme, which I can't change.
The documentation doesn't mention anything, and I can't create a local temporary server.
1- Can I use the fmp:// scheme as a callback in any way?
2- If not, is it possible to redirect the call to another centralised web server? Everything I try generates a 400 error on the google page, saying "redirect_uri_mismatch" or similar stuff.
As stated in the comments above, the only solution is to create an intermediate web server that serves a page which then opens the URL. OR creates a record in the database with the authentication code.
I've a iOS app and I would like my users to upload images to S3 directly.
I need UserX to be able to upload folders to __MY_BUCKET__/UserX/* Only. So that each one of my users have their own folder and only they can modify content in them.
Given that scenario I need to create dynamic permissions to my S3 bucket
Is that possible?
If it is... maybe I am in the right path or not....
What I've done so far is
I am using this guide to create Elastic Beanstalk with a Token Vending Machine. Then I used this other guide to configure the TVM.
Now my issue with that in none of the guides it shows an example of how to register a dynamic user (my app user) or how get the token from the TVM or how to say "Hey TVM, this userID needs upload access to __BUCKET_/ThiUserID/*" from a iOS app.
So I guess what I wonder, is how do I fill the gaps if what I am trying to achieve is possible?
I'm one of the maintainers of the AWS Mobile SDKs. The page you linked to includes projects for both iOS and Android that show how to integrate the customized TVM code in a mobile application. I suggest you look there and if you need further clarification, please update your with specific questions about the code.
You may also want to look at our web identity federation sample which is included with the SDKs. In combination with IAM policy variables, you can generate dynamic policies without the use of a Token Vending Machine.