Hi,
Thanks for the response, you are absolutely correct. There was nothing wrong with the AASA file or the entitlements, everything works now that it's present in the AppStore. The Tester did report an additional error message having triggered the AppClip registered in App Store. She was told to upgrade to v14.3 iOS. I wonder if this caused the "Not available in country or region" error when using TestFlight.
Apple really should make this clear, I was chasing rabbits down rabbit holes for days...
Post
Replies
Boosts
Views
Activity
Hi. Im still having problems. The AppClip just shows "Not available in country or region" when using TestFlight (On a non developer phone). It works with a local experience registered.
I think it's the AASA file. The AASA is available at poweredbygs1.co.uk in the root and .well-known directories and and the content looks like this :
{
"appclips": {
"apps": [
"CL7PU7LG73.org.gs1uk.t-k-2.Clip"
]
},
"applinks": {
"apps": [],
"details": [
{
"appID": "CL7PU7LG73.org.gs1uk.t-k-2",
"paths": [ "*" ]
}
]
}
}
and the build metadata like this:
Entitlements
GS1 UK Toolkit.app/AppClips/ARAppClip.app/ARAppClip
com.apple.developer.on-demand-install-capable: true
application-identifier: CL7PU7LG73.org.gs1uk.t-k-2.Clip
beta-reports-active: true
get-task-allow: false
com.apple.developer.associated-domains: ( "appclips:poweredbygs1.co.uk" )
com.apple.developer.team-identifier: CL7PU7LG73
com.apple.developer.parent-application-identifiers: ( "CL7PU7LG73.org.gs1uk.t-k-2" )
GS1 UK Toolkit.app/GS1 UK Toolkit
application-identifier: CL7PU7LG73.org.gs1uk.t-k-2
get-task-allow: false
beta-reports-active: true
com.apple.developer.associated-domains: ( )
com.apple.developer.team-identifier: CL7PU7LG73
Can anybody see anything obviously wrong? The validator https://search.developer.apple.com/appsearch-validation-tool reports Error cannot fetch app site association
Great news. Ill re-install 12.4 and try again. Thanks.
Yep, I did think to add it manually, but because its not available for selection I presumed it's not supported evan though it's asked for in the warning... Will have to wait for Apple...
I don't think your problems will end using 12.4. I was using 12.4 previously and could open the AppClip as a developer, but when I distributed the AppClip using TestFlight, my testers were getting a "This app clip is not currently available in your country or region". I believe this is because of the entitlement file. Let us know if it works for your testers using a phone that is not registered as a development device.
p.s.
You can only test the AppClip in TestFlight if the main App is not installed.
Hi.
May I ask how you added this entitlement, by manually adding the key into your entitlement file? The key is not available for selection in my project, evan if I recreate a new entitlement file.?
I think it is a bug. I have auto manage provisioning profiles switched on; and with this value added to the entitlement file an unknown error is generated. I presume it's because the value is not supported. Therefore I agree, the value cannot/should not be added directly into the entitlement file.
Not sure how to get rid of this warning. I do know that prior to installing 12.5 beta 3, I was having issues with the AppClip in TestFlight. I kept getting "AppCip not available in country". All support posts directed me towards the entitlement file, so I was please to see an error message confirming the absence of something. But now we face this new challenge, how to resolve the warning :)
I have not seen many posts...
Hi Aniol,
I have the same problem.
I select "Show Raw Codes & Values" when viewing the values in my entitlement file and then click + to add the new entitlement "com.apple.developer.associated-appclip-app-identifiers"; but this value doesn't appear as a selectable option in the list?
Im also using Xcode 12.5 beta 3. because I've had so many problems with AppClips, thought I would try the latest Beta...