I can confirm I am experiencing the same issue with exactly the same tool versions, just different mac version: altool version: 4.071.1221 Xcode version: 13.2.1 (13C100) macOS version: Monterey 12.1 (21C52)

A workaround that seems to be valid is to use the altool binary from another version of Xcode. I am using the one from Xcode 12.5.1, so far successfully. See: https://github.com/revolut-mobile/altool-binary

Also experiencing the same problem. Builds upload correctly but they do not show up in appstore connect. Seems it happens since late Wednesday. Apple shows there is an ongoing incident: App Store Connect - Issue App Store Connect - App Processing - Issue https://developer.apple.com/system-status/

Thanks! Will old builds appear, or is it only fixed for new builds?

Experiencing the same problem here: earliestReleaseDate is always nil

EDIT: earliestReleaseDate seems to be the date selected when configuring automatic release in appstoreconnect. Seems like currently it is not possible to obtain the release date for a specific AppStoreVersion using the REST API. The closest I have come, is to obtain the phasedRelease StartDate

Sorry to bring back to life this thread after 5 years, but is the best reference I could find. I experience the same: I have the association file hosted at www.domain.com/.well-known/apple-app-site-association (with www) The url domain.com/.well-known/apple-app-site-association (without www) redirects with code 301 to link above My app has in the entitlements the url domain.com (without www), and does NOT have the url www.domain.com (with www) Universal link domain.com/something (without www) works as expected, opening the app I would expect universal link domain.com/something to not work, following the documentation that says: Separately, if you’re proxying the subdomain, make sure iOS doesn’t see that as any sort of redirect. Otherwise the apple-app-site-association file won’t be scraped at all (common Universal Link implementation issue). Would greatly help if Apple could provide some more information about this given the difference in documentation VS implementation.