Just wanted to gently follow up on this topic. We are still trying to determine the recommended production strategy for supporting both newer and older macOS versions while relying primarily on Apple-hosted Background Assets. In particular, any clarification regarding: whether the 200GB hosting limit is per app or per developer account and whether hybrid/self-hosted approaches are officially expected would be greatly appreciated. Thank you!

Hi @DTS Engineer Apologies for the delay in my response. It took some time to test multiple cases and gather meaningful logs to provide a clear picture of the situation. As you suggested, I have filed a formal bug report via Feedback Assistant: Feedback ID: FB21856584 ([Notarization] Excessive notarization processing time for large app bundle (100GB+)) I have attached a ZIP file containing logs for 9 separate cases. All 9 submissions consistently show the same pattern: a reasonable upload time (~30 minutes) followed by 4 to 6 hours of server-side processing. This delay is a critical bottleneck in our distribution logic. I would greatly appreciate it if the relevant engineering team could investigate the cause of this lengthy processing time. Specifically, we would like to know if there are factors in our app’s structure causing these delays, or if there are improvements we can make on our side to optimize the process. Furthermore, we would be grateful if Apple could investigate whether there are any opportunities to optimize or improve the processing on the Apple side to help resolve this bottleneck. Thank you again for your time and for your continuous support for the developer community. Best regards, JE-H

Just following up to kindly request an update on this issue. This notarization delay is directly impacting our production release schedule, so we would greatly appreciate it if you could let us know whether this is currently under investigation or if there is any update available. We recently had a notarization submission that took close to 5 hours to complete. For reference, the submission ID is: ab36cbca-e553-4dc6-ac7e-1fcdb7b2bc9a. If possible, could someone check whether there were any unusual conditions or delays associated with this submission? Additionally, if there were any notable factors involved, we would really appreciate your guidance on what we could do on our side to mitigate or improve notarization times for future submissions. Even a brief confirmation would be very helpful for us to plan our next release steps. Thank you in advance for your time and support.

Hello, Thank you for your response. I’ve submitted a detailed bug report including the full description, reproduction steps, expected and actual results, and the Xcode/macOS build information, along with a sample Xcode project demonstrating the issue. Feedback ID: FB20788084 (Game Center sign-in alert appears on macOS 26 even without Game Center capability or entitlement) I’d greatly appreciate it if the team could review this report at your earliest convenience, as this behavior affects our current macOS app build and testing workflow. Please let me know if any additional information or logs would be helpful for further investigation. Best regards, JE

Hello, thank you for your response. After trying one more bundle synchronization, the macOS device still does not load any Game Center data (including Achievements) from the Manage Game Progress debugging tool. My app is a non-live game, and the bundle I tested on iOS is also an identifier that hasn’t gone live yet. On iOS, the same configuration works as expected, but on macOS, no data is shown. I even created a fresh project with the same Bundle Identifier, built both iOS and macOS versions, and confirmed that Game Center data loaded correctly on iOS but not on macOS. Since the issue only occurs on macOS, should I proceed with submitting a bug report through Feedback Assistant? Thank you.