@fanarchy Thank you for the post. It appears that the file is syncing to the servers without any issues. This is excellent news, and I appreciate you providing additional information regarding the problem. Your discovery of removing the “/next-game” from the AASA file, which causes it to fall back to Safari, is brilliant. This effectively isolates the issue, but still we have the issue in the App Store App Clip publishing. Safari Smart App Banners do not rely on the App Store Connect Advanced Experience database. When Safari loads your page, it reads the tag and cross-references your AASA file locally. Because your AASA and meta tags are perfect, this works flawlessly. In any case I see the issue is in the configuration on the App Store and you should file a bug for them to take a look at the process with your App Clip. The issue here is the status of the App Clip should eventually become published. Once you open the bug report, please post the FB number here for my referen
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect