Bump?

I re-ran the pipeline (without committing any new changes) and the whole pipeline succeeded this time.

@DTS Engineer I also don't think it's anything to do with my code (though I could always be wrong). This pipeline ran for 1hr 33min until I canceled it and none of the 3 targets finished, they all got stuck at 93%: https://appstoreconnect.apple.com/teams/411a63c1-9d73-4245-8bec-d755e3579ec7/apps/6737959724/ci/builds/ac32a2f1-0a28-446b-bae1-c3228612af8b/summary This pipeline ran for 53 minutes until I canceled it but iOS target succeeded, macOS and visionOS were stuck at 93%. https://appstoreconnect.apple.com/teams/411a63c1-9d73-4245-8bec-d755e3579ec7/apps/6737959724/ci/builds/3cb93c56-2eb4-4984-97df-879c0e83c8dd/summary BOTH of these pipeline runs were for the same exact commit, the code didnt change between them yet in one of them iOS succeeded and in the other one it didnt.

@DTS Engineer yes I submitted a request but it was through the contact us form not through feedback assistant: https://developer.apple.com/contact/case/102801901445/solution/select Case 102801901445 As far as sharing the project, here's a direct link to the pipeline: https://appstoreconnect.apple.com/teams/411a63c1-9d73-4245-8bec-d755e3579ec7/apps/6737959724/ci/builds/28aadaf4-68e2-4e10-9a18-fd69a574307d/summary

I came here to make the same post, my Xcode Cloud pipeline runs keep getting stuck at 93% but only for macOS and visionOS builds. iOS was having the same issue earlier but it's now working. I had a build stuck like that for 1.5hrs so I just decided to stop it and try again but all of them keep getting stuck.

I have the same error when using browser.storage.local.set() in my safari web extension. Have you found a fix/workaround?

Just submitted a feedback: FB20510351

@Jainesh91 did you figure this out?

Same issue here. I'll open a bug report shortly.

Similar issue here. I've had to add retry logic into my extension as a workaround. @lumbardhelshani please keep us updated.

SFSafariApplication.dispatchMessage() only guarantees that the native Swift/Obj-C extension process ( SafariWebExtensionHandler / SafariExtensionHandler ) is running. The background script is not woken up if it's already been suspended by the browser. And as far as your companion app is concerned, the message was successful because SafariWebExtensionHandler received it successfully. But the background script didn't receive it. What I've had to do in order to try to work around these limitations is to use a "keep alive" timer within my background script, such as: let keepAliveInterval; function startKeepAlive() { if (keepAliveInterval) return; keepAliveInterval = setInterval(() => { // Simple API call to keep background script alive chrome.runtime.getPlatformInfo(); console.debug('Keep-alive ping'); // eslint-disable-next-line no-magic-numbers }, 25000); // Every 25 seconds } // Start keep-alive system immediately at top level startKeepAlive(); This seems to help keep the background script alive. It's my understanding that Safari on macOS is supposed to support persistent background scripts. See this: https://developer.apple.com/documentation/safariservices/optimizing-your-web-extension-for-safari Which states: Consider making your background page nonpersistent in macOS when it’s primarily event-driven and responds to user interactions. In iOS, you must make your background page nonpersistent. But it doesnt seem to work for me. I get this error: Invalid persistent manifest entry. A manifest_version greater-than or equal to 3 must be non-persistent.

Same issue here with a macOS build

Has anyone figured out how to force quite an app in the Vision Pro simulator?

Did you figure this out? I'm having the same issue, but only for internal testers. External testers have 0 crashes listed.

Also wondering this