@Kjuly Any joy/update with your app being shown as released after being approved? I didn't want to wait any longer so I asked an AI agent to create a simplified alternative preview interface to connect to their API. I am using it in tandem with App Store version to continue editing my submission.

@Jeff_A Such is the current broken state of the App Store previews interface I asked an AI agent to write an alternative HTML dashboard connecting via their API to allow me to manage the images.

In my case I can use the App Store API to confirm that images are associated even though they are not visible in the preview edit. I do not want to submit in its current draft state due to all the experiments whilst trying to associate images in recent days and the confusion caused by the problems we are experiencing. Unfortunately there even the API route does not allow me to delete my current draft submission version because of some conflictive state. I'm stuck.

To recap: Images appearing in the App Store Connect Asset Library but many of us are unable to see the images in App Store Connect previews interface. Associations are being made with the previews interface but when you navigate away from the interface the images are not shown and the count text says zero. Trying to upload the images again or associate them with the Browse Assets option result in errors. I went a bit deeper and used the api.appstoreconnect.apple.com (with the help of chatGTP) to view the app store submission draft version. And yes, the image relationships are present for the missing images. When I tried to delete the submission draft using the API, in case it was just a corruption that could be resolved by creating a new draft I got an error message indicating that affected app version is blocked by API state restrictions. At this point like many others I'm stuck. I cannot visualise the preview associations nor update/correct them. Nor can I delete the current draft submission.

As the Apple Engineer stated and as in the stack overflow reply to the same question https://stackoverflow.com/questions/78999756/metal-addcompletedhandler-causes-crash-with-swift-6-ios not having @Sendable is the cause. The work around (adapting the example built into Xcode: New > Project... > Game > using Metal option): let semaphore = inFlightSemaphore commandBuffer.addCompletedHandler { @Sendable (_ commandBuffer)-> Swift.Void in semaphore.signal() } I am using a different flavour of syntax unless I am told that the above is better practice: commandBuffer.addCompletedHandler { @Sendable [weak inflightSemaphore] commandBuffer in inflightSemaphore?.signal() }