FB19959540

This appears to have something to do with the IconComposer .icon file containing png / rasterized layers that have transparency. Making it a single layer .icon file with a single layer with a non-transparent PNG appears to have resolved the app store connect errors.

Sometimes it says this: lstat( /Volumes/workspace/DerivedData/Build/Intermediates.noindex/ArchiveIntermediates/<TARGETNAME>/IntermediateBuildFilesPath/<TARGETNAME>.build/Release-iphoneos/<APPNAME>.build/Metal/PageCurl.dat ): No such file or directory (2)

Oh here's a ticket for this problem that I closed earlier in the beta cycle cause it was fixed once. Feel free to reopen it if you can. FB18269317

Lol could you imagine? Apple actually being a productive middleman and earning that 30% instead of acting like a non-communicative void?

Any updates on this? We’re around 2 days from RC upload and I’m not feeling confident this will be fixed.

Try adding some features like push notifications, Siri, shortcuts or widgets. Apple will reject apps that are just web wrappers.

Still occurring 2 days before when RC app submissions are likely to occur. Maybe this gets fixed via a backend rollout but im not confident. My FB has ”no similar reports”

I don’t think you can undo the creation of a version, but you can change the version number to whatever you want. So maybe you don’t wanna do 4.0.05, but you can change it to 3.4.71. I’m not sure if you can straight up remove it from the list. Maybe there’s a delete button in a special spot you need to hover over, like there are in some other places.

This is still failing on the RC builds on Xcode Cloud. (both Tahoe and Xcode)

FB20647871

I could swear people and places used to be retrievable albums, but I am no longer seeing them as an option in PhotoKit.

We should not be expected to all file feedbacks for Apple to fix a critical bug that should not have shipped in the first place. CloudKit is opaque and difficult enough to implement and test that there is sometimes no way to know if we are at fault or if it’s some quirk of the system. Only apple could have caught this bug with certainty and they should be performing a root cause analysis about why it shipped at all. Apple’s own sample app fails. Why is that not an automated test?

Try taking to social media and “hash tagging” with popular SwiftUI or other App Development related tags. That seems to get traction faster than using official channels.