I had redirect my new domain to old domain in firebase hosting, Everything fine in this except dynamic short url is not working, it shows dynamic url is not found, Long url is working good, Please help me on this
Related
I'm using a custom domain for Firebase Dynamic Links in my Unity app. The domain is in the format https://mywebsite.com/deeplink/
On Android, this all works fine. Going to mywebsite.com by clicking a link in an email or the browser, opens the URL in the browser and mywebsite.com/deeplink opens the app. On iOS, however, both open the app. This includes, most troubling, the mywebsite.com/_/ URL which Firebase uses for its confirm your email and reset password logic.
My app is configured with applinks:mywebsite.com in the associated domains section and the PList has an entry for FirebaseDynamicLinksCustomDomains with an array that has https://mywebsite.com/deeplink as an entry.
mywebsite.com/apple-site-association has this
{"applinks":{"apps":[],"details":[{"appID":"LK3H8YP4D2.com.help.stressfree","paths":["NOT /_/*","/*"]}]}}
Does anyone have an idea why this is happening and how I can get the app to only open URLs at mywebsite.com/deeplink?
The root domain of your custom Dynamic Link mywebsite.com shouldn't be added in the Associated Domains list. That's the reason why mywebsite.com opens the app in iOS.
Only Google-provided domains (*.page.link) should be added in the Associated Domains list.
https://firebase.google.com/docs/dynamic-links/ios/receive#open-dynamic-links-in-your-app
I'm new in ios sdk and English. Therefore, sorry for my Eng.
I try to do authentication through github using OAuthSwift.
In the registration of the application (https://github.com/settings/apps), there is need a redirect URL. In the tutorial from raywenderlich.com was an example, they did authorization through Google. They wrote a unique domain in this line that does not work: com.raywenderlich.Incognito. And in Info.plist, we added a Scheme URL with com.raywenderlich.Incognito, so that (as I understood it) when we go to this address after authentication, we’ve got into our application. But if you try to add in the application settings (https://github.com/settings/apps) the Redirect URL: something like com.raywenderlich.Incognito, will generate an error, because github wants the URL to have to be valid. If we put the Valid URL there, then when we will be redirected to this address, we will simply go to it and will not return to the application.
I would be grateful for any help.
Sorry for my English.
Redirect url in OAuth is the url that the authentication provider navigates to when authentication is successful.
For mobile apps it is the link that launches the app (a sort of deep linking)
For websites it is the website home screen
Salutations all!
I purchased a Google Domain to make my app slightly more professional than just a bare Herokuapp. I'm running into issues with Oauth2 on that particular branch of the site.
I'm running rails on the back and a bit of react on the front.
I'm not sure what all you'll need, but I'll start with some bits of code and see what comes up.
The Oauth2 works just fine on the herokuapp portion and on localhost.
The error (redirect_uri_mismatch)
My authorized redirect URIs
Again, attempting to login with google on either Localhost or on Heroku works just fine.
You have a comma , after your specified domain name.
It's showing up as:
http://www.stitchinti.me/users/auth/google_oauth2_callback,
It should be
http://www.stitchinti.me/users/auth/google_oauth2_callback
I am working with universal app links. I had put my apple-app-site-association on my server root https://www.example.net/
It works fine for all links except https://www.portal.example.net/
When i validate this link in https://search.developer.apple.com/appsearch-validation-tool it gives fetch request timeout.
Note : In portal we redirect page to website homepage (https://www.example.net/)
This is expected, due to the design of the Universal Links specification.
Here's why: https://www.example.net/ and https://www.portal.example.net/ are completely different subdomains of https://example.net/.
The Universal Links specification says each subdomain must be verified with its own apple-app-site-association file, which means a file hosted at https://www.example.net/apple-app-site-association will not work for any link on https://www.portal.example.net/. Redirects are not followed.
To fix this, simply host a file at https://www.portal.example.net/apple-app-site-association with no redirects.
I am an ios app developer. We have implemented a custom URL scheme 'my_app://section_name' or so where if the link is opened in the user's mobile browser, it will redirect the user to a specific section in the app.
We would like to be able to tweet these URLs and have users on their mobile device click on them to open up the app, however it just can click once
(when you click close , maybe you click wrong then you want to click it second but it does not work )
I hope this isn't too silly of a question. Thanks
Make sure to check the tweet body after it have been posted.
This may be due of an URL shortener, especially if the tweet is posted from the iOS 5 Twitter framework.
I'm having a similar issue with url schemes. We can include them in emails and text messages, and they highlight and work properly.
Unfortunately, when we do the same with a tweet, the iOS Twitter client fails to recognise the special URL scheme and so the user cannot tap on it to open our app.
Pretty big oversight, methinks. Anyone else had any joy including special URL scheme links in tweets?
A solution that you should consider involves not sharing the URI scheme directly, but rather creating a page on your web server to handle this. In fact, if you want to be able to share full URI schemes with paths, you're better off building a web server to dynamically generate a page with a URI scheme redirect.
This is a over-simplified representation of what we built at Branch. This includes some code to get you started though the web server will require a bit of setup not described here.
instead of testapp://some.data.here, you'll link to http://yoursite.com/hosted-redirect/some.data.here.
your server should listen at the route /hosted-redirect, grab some.data.here and build the following page (body here):
(source: derrrick.com)
So your server will have to generate and respond with this page, filling in some.data.here, anytime http://yoursite.com/hosted-redirect/some.data.here is requested.
A lightweight node app could do this with a single file.