Post

Replies

Boosts

Views

Activity

Apple should improve the App Review process for new app submissions
I’d like to suggest an improvement to the App Review process, particularly around Guideline 2.1 – Information Needed for new app submissions. Recently, I submitted a new app and received a request asking for a screen recording demonstrating the app’s core functionality, along with information about tested devices, target audience, external services, regional differences, and other details. The problem is that I had already uploaded a screen recording when submitting the app. This makes the process frustrating and inefficient for both developers and Apple. If the information has already been provided, reviewers should ideally check the submitted materials before requesting them again. Otherwise, developers have to spend additional time responding, and Apple reviewers also spend additional time handling unnecessary back-and-forth. If a screen recording and these additional details are now effectively required for most new app submissions, I think Apple should make this part of the App Store Connect submission workflow. For example, App Store Connect could provide dedicated fields for: App demonstration video Tested devices and OS versions App purpose and target audience Test/login instructions External services and AI services used Regional differences Regulatory or licensing information, where applicable This would be much clearer than putting everything into a general “App Review Notes” field. In the AI era, the number of apps being created and submitted is likely to increase significantly. Apple’s App Review process needs to evolve alongside this. Repeatedly requesting information that developers have already supplied wastes time on both sides and creates unnecessary hurdles for developers trying to bring new ideas and innovations to the iOS ecosystem. I hope Apple can consider making these requirements more structured, transparent, and automated within App Store Connect. The goal should be to make App Review both more thorough and more efficient — for Apple reviewers as well as developers.
1
3
580
Aug ’26
I'm currently using macOS 26 and Xcode 26, but I'm unable to download iOS 26 simulators.
Download failed. Domain: DVTDownloadableErrorDomain Code: 41 User Info: { DVTErrorCreationDateKey = "2025-10-26 06:59:38 +0000"; } Download failed. Domain: DVTDownloadableErrorDomain Code: 41 Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime), serverParameters ({ RequestedBuild = 23A8464; }) Domain: DVTDownloadsUtilitiesErrorDomain Code: -1 Download failed due to a bad URL. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime) Domain: com.apple.MobileAssetError.Download Code: 49 User Info: { checkConfiguration = 1; } System Information macOS Version 26.0.1 (Build 25A362) Xcode 26.0.1 (24229) (Build 17A400) Timestamp: 2025-10-26T17:59:38+11:00
17
2
1.3k
Jan ’26
Cannot download 18.5 simulator
Cannot download 18.5 simulator Download failed. Domain: DVTDownloadableErrorDomain Code: 41 User Info: { DVTErrorCreationDateKey = "2025-07-12 08:12:00 +0000"; } Download failed. Domain: DVTDownloadableErrorDomain Code: 41 Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime), serverParameters ({ RequestedBuild = 22F77; }) Domain: DVTDownloadsUtilitiesErrorDomain Code: -1 Download failed due to a bad URL. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime) Domain: com.apple.MobileAssetError.Download Code: 49 User Info: { checkConfiguration = 1; } System Information macOS Version 15.5 (Build 24F74) Xcode 16.4 (23792) (Build 16F6) Timestamp: 2025-07-12T18:12:00+10:00
1
1
660
Nov ’25
Apple should improve the App Review process for new app submissions
I’d like to suggest an improvement to the App Review process, particularly around Guideline 2.1 – Information Needed for new app submissions. Recently, I submitted a new app and received a request asking for a screen recording demonstrating the app’s core functionality, along with information about tested devices, target audience, external services, regional differences, and other details. The problem is that I had already uploaded a screen recording when submitting the app. This makes the process frustrating and inefficient for both developers and Apple. If the information has already been provided, reviewers should ideally check the submitted materials before requesting them again. Otherwise, developers have to spend additional time responding, and Apple reviewers also spend additional time handling unnecessary back-and-forth. If a screen recording and these additional details are now effectively required for most new app submissions, I think Apple should make this part of the App Store Connect submission workflow. For example, App Store Connect could provide dedicated fields for: App demonstration video Tested devices and OS versions App purpose and target audience Test/login instructions External services and AI services used Regional differences Regulatory or licensing information, where applicable This would be much clearer than putting everything into a general “App Review Notes” field. In the AI era, the number of apps being created and submitted is likely to increase significantly. Apple’s App Review process needs to evolve alongside this. Repeatedly requesting information that developers have already supplied wastes time on both sides and creates unnecessary hurdles for developers trying to bring new ideas and innovations to the iOS ecosystem. I hope Apple can consider making these requirements more structured, transparent, and automated within App Store Connect. The goal should be to make App Review both more thorough and more efficient — for Apple reviewers as well as developers.
Replies
1
Boosts
3
Views
580
Activity
Aug ’26
I'm currently using macOS 26 and Xcode 26, but I'm unable to download iOS 26 simulators.
Download failed. Domain: DVTDownloadableErrorDomain Code: 41 User Info: { DVTErrorCreationDateKey = "2025-10-26 06:59:38 +0000"; } Download failed. Domain: DVTDownloadableErrorDomain Code: 41 Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime), serverParameters ({ RequestedBuild = 23A8464; }) Domain: DVTDownloadsUtilitiesErrorDomain Code: -1 Download failed due to a bad URL. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime) Domain: com.apple.MobileAssetError.Download Code: 49 User Info: { checkConfiguration = 1; } System Information macOS Version 26.0.1 (Build 25A362) Xcode 26.0.1 (24229) (Build 17A400) Timestamp: 2025-10-26T17:59:38+11:00
Replies
17
Boosts
2
Views
1.3k
Activity
Jan ’26
Cannot download 18.5 simulator
Cannot download 18.5 simulator Download failed. Domain: DVTDownloadableErrorDomain Code: 41 User Info: { DVTErrorCreationDateKey = "2025-07-12 08:12:00 +0000"; } Download failed. Domain: DVTDownloadableErrorDomain Code: 41 Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime), serverParameters ({ RequestedBuild = 22F77; }) Domain: DVTDownloadsUtilitiesErrorDomain Code: -1 Download failed due to a bad URL. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime) Domain: com.apple.MobileAssetError.Download Code: 49 User Info: { checkConfiguration = 1; } System Information macOS Version 15.5 (Build 24F74) Xcode 16.4 (23792) (Build 16F6) Timestamp: 2025-07-12T18:12:00+10:00
Replies
1
Boosts
1
Views
660
Activity
Nov ’25