i need to add associated domain in my iOS App.
I configured the file apple-app-site-association and post it on server.
Now i should add the domain of the server in my app, but when i go to Signing and Capabilities i see this:
what's the problem?
I don't want to publish the app in App Store but only use for test develop
If you just wanna run the app in development mode and don't use paid developer account.
Try this one: Defining a custom URL scheme for your app
Related
I have followed all the steps from the Firebase Dynamic links documentation:
Added Team Id to firebase console
Added custom domain
Enabled Associated domains
Added to Info URL Schemes
However, when I click on dynamic link it always redirect to AppStore not to the app. I have tried to unistall app, restart phone and install again. How to make this deep link work?
P.S: my app is not published to AppStore yet.
In my case the problem was that I made a typo in Associated domains in Xcode, instead of applinks, I typed 'applink'.
We are trying to integrate Universal Links feature in our app.
We have an associated domain and put AASA file to server. However, when we install the app on iOS device and navigate to the url we are being redirected to the app store instead of opening our iOS app.
So the question is: Should the app be published in the AppStore to utilize Universal Links or is there some issue on our side?
You should be able to test universal links with an unpublished app. Since you're ending in the App Store, my guess is that it's an App ID mismatch.
An AASA ties paths on a domain to a particular App ID. The App ID has this format:
{TEAM_IDENTIFIER}.{BUNDLE_ID}
Is it possible you changed the Team in Xcode to something else? You'd still see the same Bundle ID but the resulting App ID would be different.
I have two apps on Appstore Connect with different app identifiers. One is in the app store while the other is on TestFlight. Is it possible to replace the live app with the one on TestFlight?
Locally these apps are built off the same bundle ID and the app identifier is changed when pushed through Fastlane. They share a signing certificate as well. If I want to replace the live app, do I just need to change the app id for my new app to match the live app?
Yes you need to change the app id and then compile the application that you would like to submit.
Off-course it will replace the old binary of the application. So the code and the UI would be updated accordingly.
I need to submit my (in development) app’s bundle identifier as well as a iOS download url to a 3rd party service for some integration keys.
I’ve created an app on the App Store connect. My dashboard shows a bundle id but no download url. How do I get this?
Also where does this url route as the app doesn’t exist in the App Store yet?
App store URL’s will be in the following format:
https://apps.apple.com/[country]/app/[App–Name]/id[App-ID]?mt=8
For example: https://apps.apple.com/us/app/whatsapp-messenger/id310633997
It will not work on Beta testing, so you will get error message because the application is not available in App Store, but when application becomes live, it should work fine.
**As IchBinStudenten mentioned **
The URL will only available when you submit your app to the App store and pass the review and get submitted to the App store.
but you can use a services like diawi to share your app with 3rd party service provider via a share link from diawi if you don't want to use Test flight.
I'm building an app which uses Facebook SDK. Since it's already in production I wanted to install two versions on my device (the App Store Version and the Development version).
I followed this instructions and successfully installed two versions of the app, but when trying to Log in using Facebook I got a problem because the development version bundleID (com.company.app.dev) does not matches the registered one on my Facebook App (com.company.app).
This guide shows how to share the same facebook appID between apps. The guide is quite confusing to me. I registered the two bundle ids (com.company.app.dev and com.company.app) and one URL scheme suffix (dev), and modified mi App.plist file to include the FacebookUrlSchemeSuffix key.
That lead me into another problem, when I logged into the production app, the callback was opening the development app, because both apps had the same URL callbacks registered (fbxxxx and fbxxxxdev, where xxxx is my facebook app id).
I solved it registering a user-defined build setting that adds the FacebookUrlSchemeSuffix when in Build mode and not in Release mode, and also modifying the URL schemes in the App.plist file to append the suffix in the same case.
But this solution seems a bit hacky since it does now follow the Facebook guides. Is there any better solution to this? I think I'm not following the Facebook guide correctly.
What you're doing is fine. You should have fbxxxx registered as a scheme in your production app, and fbxxxxdev in your dev app, and also add the suffix in your dev app.