-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Associated Domains not getting populated #17727
Comments
Without information what you are actually running / doing, it's hard to help. |
Specifically I'm implementing Firebase Dynamic/Universal links into my iOS app. I've added a list of URLs to the Associated Domains Capability in Xcode that should be recognized by the app as valid Universal Links. If I'm running the debug build off of Xcode, or if I archive the build in Xcode and then upload it myself to Firebase App Distribution, everything works as expected. But if build through fastlane (specifically the distributeToFirebase lane that's in my Fastfile) and download that build via Firebase, the app doesn't recognize the universal links and they always take the user to the app store listing for the app instead of opening the app. The associated domains plist entries that I put in my original description were the result of unzipping both IPAs (the one I built in Xcode vs the one that fastlane built) to validate that the latter wasn't working because it was missing the references to those URLs. Here's the full script that our build pipeline is running for fastlane:
|
You're not setting the entitlements through the scripts. Therefore you are not getting the expected results. |
I added |
New Issue Checklist
Issue Description
If I archive my app locally in Xcode and then upload it to Firebase App Distribution, then my universal links work properly. However, if I run my Azure Devops pipeline that uses fastlane to build the app, the entitlements aren't getting populated correctly. I pulled the ipa and checked the entitlements against the one I generated manually, and the associated domains looks like this:
Fastlane generated ipa:
Manually generated ipa:
I saw a couple of older issues on this that were closed without any resolution, and there was a plugin on the fastlane site that supposedly solved this issue, but the link for it went to a 404 on Github.
Environment
System Locale
fastlane files:
`./fastlane/Fastfile`
`./fastlane/Appfile`
fastlane gems
Loaded fastlane plugins:
Loaded gems
The text was updated successfully, but these errors were encountered: