Post not yet marked as solved
Was really surprised that Apple still has not fixed this.
We also need the GeneratedAssetSymbols extensions to be public as the asset catalogs are in a shared framework used by multiple targets and widget extensions.
Post not yet marked as solved
Same issues here
Also tried installed the 15.1 RC, which worked, but it fails installing 17.2 Sims with a 403 error.
Post not yet marked as solved
Same issues here
Also tried installed the 15.1 RC, which worked, but it fails installing 17.2 Sims with a 403 error.
Post marked as Apple Recommended
Same issue here with Xcode 13.3 (13E113) release :(
Post not yet marked as solved
Same here, this error started showing up on Jan 17th and I no longer can access Xcode Cloud from Xcode.
Xcode Cloud on the web was working ok yesterday, but today it is acting up for me. Builds fail and most recently they do not even start.
Post not yet marked as solved
Yeah, the initial issue with saving artifacts was fixed about 2 days ago.
But shortly after this new issue came:
Builds just do not start and sit in the queue for hours (now days)
Post marked as Apple Recommended
Same issue for me!
To add insult to injury if you create a brand new Xcode project and try to add ANY package from Github the process hangs immediately on "Preparing to validate"
Come on Apple! Are you for real?
Thanks sooo much. I was able to upload with Xcode cloud workflow. Will test our other CI as well.
Like others have reported I am still unable to upload to App Store Connect a build for a 2nd or 3rd platform with the same bundle version anymore using xcrun altool or directly from Xcode 13.1.
However for ***** and giggles I exported the package from Xcode instead of uploading and then used the Transporter app and lo and behold it uploaded just fine. Now sitting in "processing".
Will report back if it shows up in TestFlight.
Edit: processed fine and showed up in TF
Of course this is hardly practical compared to using a CI.
This same issue started happening for me as well a few days ago.
Post not yet marked as solved
Xcode 13.1 same for me.
Works on the web, but on in Xcode
Post not yet marked as solved
Also tried macOS Catalina 10.15.2 beta 1. Same error 😔
Post not yet marked as solved
I just tried with latest beta of MacOS Catalina 10.15.1 (19B86a) and still having the same issue with extracting the persistableContentKeyFromKeyVendorResponse
