Post

Replies

Boosts

Views

Activity

Nothing Works
App Store Connect does not work. These forums do not work. Xcode does not work. Mac OS 26 navigation bars do not work. It's getting a little frustrating. App Store Connect: "Unable to Submit for Review To submit your items for review, add an app version for the selected platform." How? I added a new app build (are "builds" and "versions" the same, I thought they were different, but why would I create a new version of my product?) and submitted it for review. It did not take the "Ready for Review" subscription items with it. They're stuck in a separate draft review. There is no control anywhere to "add an app version." Useless error, pathetic UI, designed by people who have never used this product themselves before, clearly. These forums: Try searching for "Unable to Submit for Review To submit your items for review, add an app version for the selected platform." Get a 403 Forbidden error. Fun. Very useful. Xcode does not work. Spent a good part of my day debugging why Xcode will automatically mask Mac OS 12 icons when there is no Mac app icon specified in an asset collection in a Catalyst context, but will not mask the icon when there is a Mac icon specified. There's no messaging, no warnings, no errors, no nothing. It just does random things. The entire Catalyst idea is nice in theory but there are gotchas like these everywhere. Should you build for iOS, Mac, or iOS + Mac? The answer is "Good luck." Mac OS 26 navigation bars do not work. I'm getting black text on black backgrounds, white text on white backgrounds, sometimes, depending on whether a view loads. Seems like another Apple bug. Support is useless as always, and my record on these forums so far is that no one answers any of my questions. So I'm not sure why I bother. But maybe something I've written will help someone.
9
1
396
1w
Xcode MTL Validation Crashes App
I don't really know the terminology around this very well, but I was trying to test my Mac OS Catalyst app on Mac OS Sequoia, and the app kept crashing apparently due to MTL validation. I was trying to debug why using a menu (as in File, Edit, View, etc.) would crash. The stack looked roughly like this: 6 -[MTLDebugComputeCommandEncoder setBuffer:offset:attributeStride:atIndex:] MetalTools 5 _CF_forwarding_prep_0 CoreFoundation 4 ___forwarding___ CoreFoundation 3 -[NSObject doesNotRecognizeSelector:] CoreFoundation 2 objc_exception_throw libobjc.A.dylib 1 __cxa_throw b 0 _Unwind_RaiseException libunwind.dylib Both Claude and Gemini indicated that there was no flaw in my code, but rather that Xcode was responsible. Sure enough, unchecking the MTL validation checkbox in Xcode stopped the crash from happening.
3
0
223
2w
App Reviewers Keep Responding With Nonsense Rejections
I built what Apple would describe as a "reader" app. Because it involves legal and financial information, however, it doesn't qualify as a standard "news" reader, so Apple is not treating as a reader app. That means it needs to have in-app subscriptions. Fine. I think that's a better UI choice for the user anyway. The problem is that the App Store Connect UI for subscriptions and the training materials for Apple's reviewers on subscriptions are horrendous. As my other posts on these forums have documented, they literally do not work. Now with the app in the review process, the reviewers keep sending back rejections because they keep trying to sign up for a subscription with the provided demo account that is already signed up. Why is the demo account already signed up? Because it's a demo account! And that's what Apple wants (to test each and every feature)! Fortunately, there are additional in-app subscription sandbox accounts I've provided credentials for so that from a clean slate, the reviewers can choose a plan and test signing up using those. But they apparently either don't understand that it makes no sense to sign up twice for a subscription or they refuse to do it without explaining why. Instead, they claim that there is some UI problem with the app because it won't let a signed-up account sign up again. This is bonkers. The obvious solution is that if Apple wants each subscription to have a dedicated test sandbox account, then when you add a subscription plan, the credentials for such an account for the reviewers to use should be required fields. But they're not, and now I've wasted two weeks dealing with a feature that technically should not be required for the app at all by Apple's own guidelines. Apple has been less than helpful when trying to sort this out. The entire process is hugely inefficient. If you could just set up a block of 10-20 minutes as an appointment to speak to your reviewer(s) instead of a round-robin that gets you a response once per day at best, it would eliminate probably 80% of the needless back-and-forth that the current process yields.
1
0
170
2w
App Store Connect Shows Subscription Errors
See below screenshot. App Store Connect is making this process next to impossible. And I'm sure this has been said a thousand times before by other developers but this UI, even when it "works," provides absolutely no guidance for developers about what Apple expects. It does not render the strings in context or provide reasonable examples so developers understand what Apple is even asking for here. What should a good subscription group description be? It's completely unclear. If the point Apple is trying to drive home is that developers need to be clear with customers, then it should take some of its own advice and explain to developers what it actually wants here.
0
0
251
3w
App Store Connect Shows Conflicting Statuses
This is a screenshot of my App Store Connect right now (in Safari): An app version should not be able to display as simultaneously "Waiting For Review" and "In Review". Nor is it clear why the "macOS 1.0.0" version shows "Unresolved Issues" when I responded to the reviewer and the response is recorded. A different status like "Unresolved pending correspondence" would be more helpful.
0
0
205
3w
App Store Connect Does Not Allow Reply
This will be the fifth bug I have found in Apple's code in two weeks that is preventing me from distributing my app. I cannot reply to the reviewer who reviewed my app. Why? Another unspecified error. What did I do wrong? I attached a screenshot. Then nothing happened. So I tried to attach it again. Then I tried to remove the second attachment. Then I got this error. The level of pervasive flaws in Apple's systems is really unacceptable.
0
1
159
3w
"Sandbox Apple Account" Developer Setting Does Not Work
I am trying to test a sandbox account for an in-app subscription. It will not work. When I try to check out in my app, I'm told... 2026-07-08 14:41:59.282977-0700 PlainSite[1364:48033] [Default] [StoreKit] Purchase did not return a transaction: Error Domain=ASDErrorDomain Code=500 "Unhandled exception" UserInfo={NSUnderlyingError=0x2835d21f0 {Error Domain=AMSErrorDomain Code=100 "Authentication Failed" UserInfo={NSMultipleUnderlyingErrorsKey=( "Error Domain=AMSErrorDomain Code=2 \"An unknown error occurred. Please try again.\" UserInfo={NSLocalizedDescription=An unknown error occurred. Please try again.}", "Error Domain=AMSServerErrorDomain Code=-5000 \"(null)\" UserInfo={failureType=-5000, m-allowed=false, pings=(\n), cancel-purchase-batch=true, customerMessage=Check the account information you entered and try again.}" ), NSLocalizedDescription=Authentication Failed, NSLocalizedFailureReason=The authentication failed.}}, NSLocalizedFailureReason=An unknown error occurred, NSLocalizedDescription=Unhandled exception} [CreateAccountView] purchaseForSignup threw: userCancelled This is false. The user (me) did not cancel. This is with me manually typing in the sandbox credentials as the Apple ID and password at the point of completing the transaction on both iOS 15 and iOS 26. So I try to make sure that my sandbox account is properly set in iOS 26's Settings -> Developer -> Sandbox Apple Account screen. It says Sign In. Then it says "Apple Account Sign in Requested". What does this actually mean? Who knows. It could mean my App Store Connect credentials are what it wants so that it can query which sandbox accounts are available to use—after all, that is where they are set up. It could also mean that you should type in the sandbox account's credentials directly because a sandbox account is basically a fake Apple ID. I try both. Neither works. No matter what I do, it just goes back to the Developer view and says "Sign In". Have I signed in? I don't know. Maybe, but probably not, given that nothing works. Is the problem that I didn't confirm the sandbox account's e-mail address? No. It doesn't work before or after I've confirmed the e-mail. Is the problem that I don't have two-factor authentication on for the sandbox account? No. It doesn't work whether or not two-factor authentication is enabled. I am not the only one having this problem. People on a certain Reddit thread I'm for some reason not allowed to link to here (sandbox_accounts_simulator_help) have been having it for the past year it looks like, except they got it to work on a real device, and I'm using an iPhone 17, which is a real device, and it doesn't work. This is the third bug in Apple's code I've found in the past couple of weeks that is preventing me from getting my app published and it's getting frustrating. Any assistance would be appreciated. Fix your code, Apple.
2
0
370
3w
App Store Connect HTTP 500 Errors
Hi, App Store Connect does not work, which is preventing me from re-submitting my app after a reviewer incorrectly interpreted Apple's rules and rejected it. My Safari browser console: [Error] Failed to load resource: the server responded with a status of 500 () (6779518190, line 0) [Error] {appName: "appstore", payload: Array, eventKit: "logger", env: "PROD"} (anonymous function) (container.243b4934f1512a8c.js:2:335294) execute (334.088309ca37150264.js:1:30102) (anonymous function) (334.088309ca37150264.js:1:32316) process (334.088309ca37150264.js:1:48276) ae (container.243b4934f1512a8c.js:2:204904) (anonymous function) (container.243b4934f1512a8c.js:2:215186) (anonymous function) (container.243b4934f1512a8c.js:2:189103) (anonymous function) (container.243b4934f1512a8c.js:2:188923) (anonymous function) (container.243b4934f1512a8c.js:2:191222) [Error] Failed to load resource: the server responded with a status of 500 () (6788522984, line 0) [Error] {appName: "appstore", payload: Array, eventKit: "logger", env: "PROD"} (anonymous function) (container.243b4934f1512a8c.js:2:335294) execute (334.088309ca37150264.js:1:30102) (anonymous function) (334.088309ca37150264.js:1:32316) process (334.088309ca37150264.js:1:48276) ae (container.243b4934f1512a8c.js:2:204904) (anonymous function) (container.243b4934f1512a8c.js:2:215186) (anonymous function) (container.243b4934f1512a8c.js:2:189103) (anonymous function) (container.243b4934f1512a8c.js:2:188923) (anonymous function) (container.243b4934f1512a8c.js:2:191222) [Error] Failed to load resource: the server responded with a status of 500 () (planAvailabilities, line 0) [Error] Failed to load resource: the server responded with a status of 500 () (prices, line 0) [Error] Failed to load resource: the server responded with a status of 500 () (introductoryOffers, line 0) [Error] Failed to load resource: the server responded with a status of 500 () (offerCodes, line 0) [Error] {appName: "appstore", payload: Array, eventKit: "logger", env: "PROD"} (anonymous function) (container.243b4934f1512a8c.js:2:335294) execute (334.088309ca37150264.js:1:30102) (anonymous function) (334.088309ca37150264.js:1:32316) process (334.088309ca37150264.js:1:48276) ae (container.243b4934f1512a8c.js:2:204904) (anonymous function) (container.243b4934f1512a8c.js:2:215186) (anonymous function) (container.243b4934f1512a8c.js:2:189103) (anonymous function) (container.243b4934f1512a8c.js:2:188923) (anonymous function) (container.243b4934f1512a8c.js:2:191222) App Store Connect should not be yielding HTTP 500s, ever. Developer phone support could not help and said to post here, so here I am. Please advise.
1
1
432
3w
Safari 17.6 (17618.3.11.11.7, 17618) Crashes on Attempt to Run Extension in Developer Mode
Hi, I'm trying to test out an extension I'm building in Xcode and every time I try to test it, Safari crashes immediately. On later versions of Mac OS, e.g. Sequoia, there's no problem. I'm building this extension as part of a Mac Catalyst app that is a hybrid iPad/Mac OS app. On Safari 26.3 (20623.2.7.18.1) I can just add the source tree as a temporary extension and it works fine. But the .appex file for the same thing is causing the older Safari 17.6 (17618.3.11.11.7, 17618) to throw a fit. Trying to get through this with LLMs has focused on whether the extension target is for iOS and Mac OS or just Mac OS alone, and futzing with UIDeviceFamily the Build Settings. But basically it just doesn't work no matter what I do, and Safari shouldn't crash. Here's the .appex's Info.plist after compilation: % defaults read /Users/[username]/Library/Developer/Xcode/DerivedData/PlainSite-[gibberish]/Build/Products/Debug-maccatalyst/PlainSite.app/Contents/PlugIns/PlainSiteRecycler.appex/Contents/Info.plist { BuildMachineOSBuild = 21H1320; CFBundleIdentifier = "com.thinkcomputer.[product].[extension]"; CFBundleShortVersionString = "1.0"; CFBundleSupportedPlatforms = ( MacOSX ); CFBundleVersion = 2; DTCompiler = "com.apple.compilers.llvm.clang.1_0"; DTPlatformBuild = 14C18; DTPlatformName = macosx; DTPlatformVersion = "13.1"; DTSDKBuild = 22C55; DTSDKName = "macosx13.1"; DTXcode = 1420; DTXcodeBuild = 14C18; LSMinimumSystemVersion = "12.0"; NSExtension = { NSExtensionAttributes = { SafariWebExtensionPath = src; }; NSExtensionPointIdentifier = "com.apple.Safari.web-extension"; NSExtensionPrincipalClass = "PlainSiteRecycler.SafariWebExtensionHandler"; }; UIDeviceFamily = ( 2, 6 ); } Crash log: Hardware Model: MacBookPro12,1 Process: Safari [44241] Path: /Applications/Safari.app/Contents/MacOS/Safari Identifier: com.apple.Safari Version: 17.6 (17618.3.11.11.7) Code Type: X86-64 (Native) Role: Background Parent Process: launchd [1] Coalition: com.apple.Safari [1098] Date/Time: 2026-06-12 13:29:10.8546 -0700 Launch Time: 2026-06-12 13:27:27.7047 -0700 OS Version: macOS 12.7.6 (21H1320) Release Type: User Report Version: 104 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_PROTECTION_FAILURE at 0x00007ff7b77d1ff8 Exception Codes: 0x0000000000000002, 0x00007ff7b77d1ff8 VM Region Info: 0x7ff7b77d1ff8 is in 0x7ff7b3fd2000-0x7ff7b77d2000; bytes after start: 58720248 bytes before end: 7 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL MALLOC_SMALL 7fa313000000-7fa313800000 [ 8192K] rw-/rwx SM=PRV GAP OF 0x54a07d2000 BYTES ---> STACK GUARD 7ff7b3fd2000-7ff7b77d2000 [ 56.0M] ---/rwx SM=NUL ... for thread 0 Stack 7ff7b77d2000-7ff7b7fd2000 [ 8192K] rw-/rwx SM=PRV thread 0 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: SIGNAL 11 Segmentation fault: 11 Terminating Process: exc handler [44241] Highlighted by Thread: 0 Backtrace not available No thread state (register information) available Binary Images: 0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ??? Error Formulating Crash Report: dyld_process_info_create failed with 5 Failed to create CSSymbolicatorRef - corpse still valid ¯_(ツ)/¯ thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port EOF Full Report {"app_name":"Safari","timestamp":"2026-06-12 13:29:12.00 -0700","app_version":"17.6","slice_uuid":"af2262af-647d-3262-adc8-e52c3ef7579e","build_version":"17618.3.11.11.7","platform":0,"bundleID":"com.apple.Safari","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 12.7.6 (21H1320)","incident_id":"8F871759-8566-49DE-A6F9-EE73128BB836","name":"Safari"} { "uptime" : 100000, "procLaunch" : "2026-06-12 13:27:27.7047 -0700", "procRole" : "Background", "version" : 2, "userID" : 503, "deployVersion" : 210, "modelCode" : "MacBookPro12,1", "procStartAbsTime" : 102649791496150, "coalitionID" : 1098, "osVersion" : { "train" : "macOS 12.7.6", "build" : "21H1320", "releaseType" : "User" }, "captureTime" : "2026-06-12 13:29:10.8546 -0700", "incident" : "8F871759-8566-49DE-A6F9-EE73128BB836", "bug_type" : "309", "pid" : 44241, "procExitAbsTime" : 102752878214260, "cpuType" : "X86-64", "procName" : "Safari", "procPath" : "/Applications/Safari.app/Contents/MacOS/Safari", "bundleInfo" : {"CFBundleShortVersionString":"17.6","CFBundleVersion":"17618.3.11.11.7","CFBundleIdentifier":"com.apple.Safari"}, "buildInfo" : {"ProjectName":"Safari","SourceVersion":"7618003011011007","ProductBuildVersion":"618G22","BuildVersion":"12"}, "storeInfo" : {"deviceIdentifierForVendor":"28124F28-A4EB-556C-A50C-D710162ABDA6","thirdParty":true}, "parentProc" : "launchd", "parentPid" : 1, "coalitionName" : "com.apple.Safari", "crashReporterKey" : "134BE33B-9612-8725-73E0-95998174507F", "wakeTime" : 67008, "sleepWakeUUID" : "F942DC6A-04DF-4EE2-AA9F-DB3EDCB24AC3", "sip" : "enabled", "isCorpse" : 1, "exception" : {"codes":"0x0000000000000002, 0x00007ff7b77d1ff8","rawCodes":[2,140701912080376],"type":"EXC_BAD_ACCESS","signal":"SIGSEGV","subtype":"KERN_PROTECTION_FAILURE at 0x00007ff7b77d1ff8"}, "termination" : {"flags":0,"code":11,"namespace":"SIGNAL","indicator":"Segmentation fault: 11","byProc":"exc handler","byPid":44241}, "usedImages" : [ { "size" : 0, "source" : "A", "base" : 0, "uuid" : "00000000-0000-0000-0000-000000000000" } ], "sharedCache" : { "base" : 140703277129728, "size" : 19331678208, "uuid" : "246818c3-4b9f-3462-bcaf-fdf71975e5fe" }, "legacyInfo" : { "threadHighlighted" : 0 }, "trialInfo" : { "rollouts" : [ { "rolloutId" : "61301e3a61217b3110231469", "factorPackIds" : { "SIRI_FIND_MY_CONFIGURATION_FILES" : "652886aa2c02f032beae8316" }, "deploymentId" : 240000028 }, { "rolloutId" : "5ffde50ce2aacd000d47a95f", "factorPackIds" : { }, "deploymentId" : 240000550 } ], "experiments" : [ ] }, "reportNotes" : [ "dyld_process_info_create failed with 5", "Failed to create CSSymbolicatorRef - corpse still valid ¯\(ツ)_/¯", "thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port", "thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port", "thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port" ] } Any help would be greatly appreciated!
2
0
974
Jun ’26
App Store Connect IAP Catch-22
Well, here we go again. The subscription items are rejected because I have not submitted a binary. (Except I have, of course.) The binary is rejected because I have not submitted the IAP subscription items. (Except I have, of course.) Neither lets me submit the other again alongside it. Brilliant system.
Replies
9
Boosts
0
Views
675
Activity
11h
Nothing Works
App Store Connect does not work. These forums do not work. Xcode does not work. Mac OS 26 navigation bars do not work. It's getting a little frustrating. App Store Connect: "Unable to Submit for Review To submit your items for review, add an app version for the selected platform." How? I added a new app build (are "builds" and "versions" the same, I thought they were different, but why would I create a new version of my product?) and submitted it for review. It did not take the "Ready for Review" subscription items with it. They're stuck in a separate draft review. There is no control anywhere to "add an app version." Useless error, pathetic UI, designed by people who have never used this product themselves before, clearly. These forums: Try searching for "Unable to Submit for Review To submit your items for review, add an app version for the selected platform." Get a 403 Forbidden error. Fun. Very useful. Xcode does not work. Spent a good part of my day debugging why Xcode will automatically mask Mac OS 12 icons when there is no Mac app icon specified in an asset collection in a Catalyst context, but will not mask the icon when there is a Mac icon specified. There's no messaging, no warnings, no errors, no nothing. It just does random things. The entire Catalyst idea is nice in theory but there are gotchas like these everywhere. Should you build for iOS, Mac, or iOS + Mac? The answer is "Good luck." Mac OS 26 navigation bars do not work. I'm getting black text on black backgrounds, white text on white backgrounds, sometimes, depending on whether a view loads. Seems like another Apple bug. Support is useless as always, and my record on these forums so far is that no one answers any of my questions. So I'm not sure why I bother. But maybe something I've written will help someone.
Replies
9
Boosts
1
Views
396
Activity
1w
Xcode MTL Validation Crashes App
I don't really know the terminology around this very well, but I was trying to test my Mac OS Catalyst app on Mac OS Sequoia, and the app kept crashing apparently due to MTL validation. I was trying to debug why using a menu (as in File, Edit, View, etc.) would crash. The stack looked roughly like this: 6 -[MTLDebugComputeCommandEncoder setBuffer:offset:attributeStride:atIndex:] MetalTools 5 _CF_forwarding_prep_0 CoreFoundation 4 ___forwarding___ CoreFoundation 3 -[NSObject doesNotRecognizeSelector:] CoreFoundation 2 objc_exception_throw libobjc.A.dylib 1 __cxa_throw b 0 _Unwind_RaiseException libunwind.dylib Both Claude and Gemini indicated that there was no flaw in my code, but rather that Xcode was responsible. Sure enough, unchecking the MTL validation checkbox in Xcode stopped the crash from happening.
Replies
3
Boosts
0
Views
223
Activity
2w
App Reviewers Keep Responding With Nonsense Rejections
I built what Apple would describe as a "reader" app. Because it involves legal and financial information, however, it doesn't qualify as a standard "news" reader, so Apple is not treating as a reader app. That means it needs to have in-app subscriptions. Fine. I think that's a better UI choice for the user anyway. The problem is that the App Store Connect UI for subscriptions and the training materials for Apple's reviewers on subscriptions are horrendous. As my other posts on these forums have documented, they literally do not work. Now with the app in the review process, the reviewers keep sending back rejections because they keep trying to sign up for a subscription with the provided demo account that is already signed up. Why is the demo account already signed up? Because it's a demo account! And that's what Apple wants (to test each and every feature)! Fortunately, there are additional in-app subscription sandbox accounts I've provided credentials for so that from a clean slate, the reviewers can choose a plan and test signing up using those. But they apparently either don't understand that it makes no sense to sign up twice for a subscription or they refuse to do it without explaining why. Instead, they claim that there is some UI problem with the app because it won't let a signed-up account sign up again. This is bonkers. The obvious solution is that if Apple wants each subscription to have a dedicated test sandbox account, then when you add a subscription plan, the credentials for such an account for the reviewers to use should be required fields. But they're not, and now I've wasted two weeks dealing with a feature that technically should not be required for the app at all by Apple's own guidelines. Apple has been less than helpful when trying to sort this out. The entire process is hugely inefficient. If you could just set up a block of 10-20 minutes as an appointment to speak to your reviewer(s) instead of a round-robin that gets you a response once per day at best, it would eliminate probably 80% of the needless back-and-forth that the current process yields.
Replies
1
Boosts
0
Views
170
Activity
2w
App Store Connect Shows Subscription Errors
See below screenshot. App Store Connect is making this process next to impossible. And I'm sure this has been said a thousand times before by other developers but this UI, even when it "works," provides absolutely no guidance for developers about what Apple expects. It does not render the strings in context or provide reasonable examples so developers understand what Apple is even asking for here. What should a good subscription group description be? It's completely unclear. If the point Apple is trying to drive home is that developers need to be clear with customers, then it should take some of its own advice and explain to developers what it actually wants here.
Replies
0
Boosts
0
Views
251
Activity
3w
App Store Connect Shows Conflicting Statuses
This is a screenshot of my App Store Connect right now (in Safari): An app version should not be able to display as simultaneously "Waiting For Review" and "In Review". Nor is it clear why the "macOS 1.0.0" version shows "Unresolved Issues" when I responded to the reviewer and the response is recorded. A different status like "Unresolved pending correspondence" would be more helpful.
Replies
0
Boosts
0
Views
205
Activity
3w
App Store Connect Does Not Allow Reply
This will be the fifth bug I have found in Apple's code in two weeks that is preventing me from distributing my app. I cannot reply to the reviewer who reviewed my app. Why? Another unspecified error. What did I do wrong? I attached a screenshot. Then nothing happened. So I tried to attach it again. Then I tried to remove the second attachment. Then I got this error. The level of pervasive flaws in Apple's systems is really unacceptable.
Replies
0
Boosts
1
Views
159
Activity
3w
"Sandbox Apple Account" Developer Setting Does Not Work
I am trying to test a sandbox account for an in-app subscription. It will not work. When I try to check out in my app, I'm told... 2026-07-08 14:41:59.282977-0700 PlainSite[1364:48033] [Default] [StoreKit] Purchase did not return a transaction: Error Domain=ASDErrorDomain Code=500 "Unhandled exception" UserInfo={NSUnderlyingError=0x2835d21f0 {Error Domain=AMSErrorDomain Code=100 "Authentication Failed" UserInfo={NSMultipleUnderlyingErrorsKey=( "Error Domain=AMSErrorDomain Code=2 \"An unknown error occurred. Please try again.\" UserInfo={NSLocalizedDescription=An unknown error occurred. Please try again.}", "Error Domain=AMSServerErrorDomain Code=-5000 \"(null)\" UserInfo={failureType=-5000, m-allowed=false, pings=(\n), cancel-purchase-batch=true, customerMessage=Check the account information you entered and try again.}" ), NSLocalizedDescription=Authentication Failed, NSLocalizedFailureReason=The authentication failed.}}, NSLocalizedFailureReason=An unknown error occurred, NSLocalizedDescription=Unhandled exception} [CreateAccountView] purchaseForSignup threw: userCancelled This is false. The user (me) did not cancel. This is with me manually typing in the sandbox credentials as the Apple ID and password at the point of completing the transaction on both iOS 15 and iOS 26. So I try to make sure that my sandbox account is properly set in iOS 26's Settings -> Developer -> Sandbox Apple Account screen. It says Sign In. Then it says "Apple Account Sign in Requested". What does this actually mean? Who knows. It could mean my App Store Connect credentials are what it wants so that it can query which sandbox accounts are available to use—after all, that is where they are set up. It could also mean that you should type in the sandbox account's credentials directly because a sandbox account is basically a fake Apple ID. I try both. Neither works. No matter what I do, it just goes back to the Developer view and says "Sign In". Have I signed in? I don't know. Maybe, but probably not, given that nothing works. Is the problem that I didn't confirm the sandbox account's e-mail address? No. It doesn't work before or after I've confirmed the e-mail. Is the problem that I don't have two-factor authentication on for the sandbox account? No. It doesn't work whether or not two-factor authentication is enabled. I am not the only one having this problem. People on a certain Reddit thread I'm for some reason not allowed to link to here (sandbox_accounts_simulator_help) have been having it for the past year it looks like, except they got it to work on a real device, and I'm using an iPhone 17, which is a real device, and it doesn't work. This is the third bug in Apple's code I've found in the past couple of weeks that is preventing me from getting my app published and it's getting frustrating. Any assistance would be appreciated. Fix your code, Apple.
Replies
2
Boosts
0
Views
370
Activity
3w
App Store Connect HTTP 500 Errors
Hi, App Store Connect does not work, which is preventing me from re-submitting my app after a reviewer incorrectly interpreted Apple's rules and rejected it. My Safari browser console: [Error] Failed to load resource: the server responded with a status of 500 () (6779518190, line 0) [Error] {appName: "appstore", payload: Array, eventKit: "logger", env: "PROD"} (anonymous function) (container.243b4934f1512a8c.js:2:335294) execute (334.088309ca37150264.js:1:30102) (anonymous function) (334.088309ca37150264.js:1:32316) process (334.088309ca37150264.js:1:48276) ae (container.243b4934f1512a8c.js:2:204904) (anonymous function) (container.243b4934f1512a8c.js:2:215186) (anonymous function) (container.243b4934f1512a8c.js:2:189103) (anonymous function) (container.243b4934f1512a8c.js:2:188923) (anonymous function) (container.243b4934f1512a8c.js:2:191222) [Error] Failed to load resource: the server responded with a status of 500 () (6788522984, line 0) [Error] {appName: "appstore", payload: Array, eventKit: "logger", env: "PROD"} (anonymous function) (container.243b4934f1512a8c.js:2:335294) execute (334.088309ca37150264.js:1:30102) (anonymous function) (334.088309ca37150264.js:1:32316) process (334.088309ca37150264.js:1:48276) ae (container.243b4934f1512a8c.js:2:204904) (anonymous function) (container.243b4934f1512a8c.js:2:215186) (anonymous function) (container.243b4934f1512a8c.js:2:189103) (anonymous function) (container.243b4934f1512a8c.js:2:188923) (anonymous function) (container.243b4934f1512a8c.js:2:191222) [Error] Failed to load resource: the server responded with a status of 500 () (planAvailabilities, line 0) [Error] Failed to load resource: the server responded with a status of 500 () (prices, line 0) [Error] Failed to load resource: the server responded with a status of 500 () (introductoryOffers, line 0) [Error] Failed to load resource: the server responded with a status of 500 () (offerCodes, line 0) [Error] {appName: "appstore", payload: Array, eventKit: "logger", env: "PROD"} (anonymous function) (container.243b4934f1512a8c.js:2:335294) execute (334.088309ca37150264.js:1:30102) (anonymous function) (334.088309ca37150264.js:1:32316) process (334.088309ca37150264.js:1:48276) ae (container.243b4934f1512a8c.js:2:204904) (anonymous function) (container.243b4934f1512a8c.js:2:215186) (anonymous function) (container.243b4934f1512a8c.js:2:189103) (anonymous function) (container.243b4934f1512a8c.js:2:188923) (anonymous function) (container.243b4934f1512a8c.js:2:191222) App Store Connect should not be yielding HTTP 500s, ever. Developer phone support could not help and said to post here, so here I am. Please advise.
Replies
1
Boosts
1
Views
432
Activity
3w
Safari 17.6 (17618.3.11.11.7, 17618) Crashes on Attempt to Run Extension in Developer Mode
Hi, I'm trying to test out an extension I'm building in Xcode and every time I try to test it, Safari crashes immediately. On later versions of Mac OS, e.g. Sequoia, there's no problem. I'm building this extension as part of a Mac Catalyst app that is a hybrid iPad/Mac OS app. On Safari 26.3 (20623.2.7.18.1) I can just add the source tree as a temporary extension and it works fine. But the .appex file for the same thing is causing the older Safari 17.6 (17618.3.11.11.7, 17618) to throw a fit. Trying to get through this with LLMs has focused on whether the extension target is for iOS and Mac OS or just Mac OS alone, and futzing with UIDeviceFamily the Build Settings. But basically it just doesn't work no matter what I do, and Safari shouldn't crash. Here's the .appex's Info.plist after compilation: % defaults read /Users/[username]/Library/Developer/Xcode/DerivedData/PlainSite-[gibberish]/Build/Products/Debug-maccatalyst/PlainSite.app/Contents/PlugIns/PlainSiteRecycler.appex/Contents/Info.plist { BuildMachineOSBuild = 21H1320; CFBundleIdentifier = "com.thinkcomputer.[product].[extension]"; CFBundleShortVersionString = "1.0"; CFBundleSupportedPlatforms = ( MacOSX ); CFBundleVersion = 2; DTCompiler = "com.apple.compilers.llvm.clang.1_0"; DTPlatformBuild = 14C18; DTPlatformName = macosx; DTPlatformVersion = "13.1"; DTSDKBuild = 22C55; DTSDKName = "macosx13.1"; DTXcode = 1420; DTXcodeBuild = 14C18; LSMinimumSystemVersion = "12.0"; NSExtension = { NSExtensionAttributes = { SafariWebExtensionPath = src; }; NSExtensionPointIdentifier = "com.apple.Safari.web-extension"; NSExtensionPrincipalClass = "PlainSiteRecycler.SafariWebExtensionHandler"; }; UIDeviceFamily = ( 2, 6 ); } Crash log: Hardware Model: MacBookPro12,1 Process: Safari [44241] Path: /Applications/Safari.app/Contents/MacOS/Safari Identifier: com.apple.Safari Version: 17.6 (17618.3.11.11.7) Code Type: X86-64 (Native) Role: Background Parent Process: launchd [1] Coalition: com.apple.Safari [1098] Date/Time: 2026-06-12 13:29:10.8546 -0700 Launch Time: 2026-06-12 13:27:27.7047 -0700 OS Version: macOS 12.7.6 (21H1320) Release Type: User Report Version: 104 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_PROTECTION_FAILURE at 0x00007ff7b77d1ff8 Exception Codes: 0x0000000000000002, 0x00007ff7b77d1ff8 VM Region Info: 0x7ff7b77d1ff8 is in 0x7ff7b3fd2000-0x7ff7b77d2000; bytes after start: 58720248 bytes before end: 7 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL MALLOC_SMALL 7fa313000000-7fa313800000 [ 8192K] rw-/rwx SM=PRV GAP OF 0x54a07d2000 BYTES ---> STACK GUARD 7ff7b3fd2000-7ff7b77d2000 [ 56.0M] ---/rwx SM=NUL ... for thread 0 Stack 7ff7b77d2000-7ff7b7fd2000 [ 8192K] rw-/rwx SM=PRV thread 0 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: SIGNAL 11 Segmentation fault: 11 Terminating Process: exc handler [44241] Highlighted by Thread: 0 Backtrace not available No thread state (register information) available Binary Images: 0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ??? Error Formulating Crash Report: dyld_process_info_create failed with 5 Failed to create CSSymbolicatorRef - corpse still valid ¯_(ツ)/¯ thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port EOF Full Report {"app_name":"Safari","timestamp":"2026-06-12 13:29:12.00 -0700","app_version":"17.6","slice_uuid":"af2262af-647d-3262-adc8-e52c3ef7579e","build_version":"17618.3.11.11.7","platform":0,"bundleID":"com.apple.Safari","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 12.7.6 (21H1320)","incident_id":"8F871759-8566-49DE-A6F9-EE73128BB836","name":"Safari"} { "uptime" : 100000, "procLaunch" : "2026-06-12 13:27:27.7047 -0700", "procRole" : "Background", "version" : 2, "userID" : 503, "deployVersion" : 210, "modelCode" : "MacBookPro12,1", "procStartAbsTime" : 102649791496150, "coalitionID" : 1098, "osVersion" : { "train" : "macOS 12.7.6", "build" : "21H1320", "releaseType" : "User" }, "captureTime" : "2026-06-12 13:29:10.8546 -0700", "incident" : "8F871759-8566-49DE-A6F9-EE73128BB836", "bug_type" : "309", "pid" : 44241, "procExitAbsTime" : 102752878214260, "cpuType" : "X86-64", "procName" : "Safari", "procPath" : "/Applications/Safari.app/Contents/MacOS/Safari", "bundleInfo" : {"CFBundleShortVersionString":"17.6","CFBundleVersion":"17618.3.11.11.7","CFBundleIdentifier":"com.apple.Safari"}, "buildInfo" : {"ProjectName":"Safari","SourceVersion":"7618003011011007","ProductBuildVersion":"618G22","BuildVersion":"12"}, "storeInfo" : {"deviceIdentifierForVendor":"28124F28-A4EB-556C-A50C-D710162ABDA6","thirdParty":true}, "parentProc" : "launchd", "parentPid" : 1, "coalitionName" : "com.apple.Safari", "crashReporterKey" : "134BE33B-9612-8725-73E0-95998174507F", "wakeTime" : 67008, "sleepWakeUUID" : "F942DC6A-04DF-4EE2-AA9F-DB3EDCB24AC3", "sip" : "enabled", "isCorpse" : 1, "exception" : {"codes":"0x0000000000000002, 0x00007ff7b77d1ff8","rawCodes":[2,140701912080376],"type":"EXC_BAD_ACCESS","signal":"SIGSEGV","subtype":"KERN_PROTECTION_FAILURE at 0x00007ff7b77d1ff8"}, "termination" : {"flags":0,"code":11,"namespace":"SIGNAL","indicator":"Segmentation fault: 11","byProc":"exc handler","byPid":44241}, "usedImages" : [ { "size" : 0, "source" : "A", "base" : 0, "uuid" : "00000000-0000-0000-0000-000000000000" } ], "sharedCache" : { "base" : 140703277129728, "size" : 19331678208, "uuid" : "246818c3-4b9f-3462-bcaf-fdf71975e5fe" }, "legacyInfo" : { "threadHighlighted" : 0 }, "trialInfo" : { "rollouts" : [ { "rolloutId" : "61301e3a61217b3110231469", "factorPackIds" : { "SIRI_FIND_MY_CONFIGURATION_FILES" : "652886aa2c02f032beae8316" }, "deploymentId" : 240000028 }, { "rolloutId" : "5ffde50ce2aacd000d47a95f", "factorPackIds" : { }, "deploymentId" : 240000550 } ], "experiments" : [ ] }, "reportNotes" : [ "dyld_process_info_create failed with 5", "Failed to create CSSymbolicatorRef - corpse still valid ¯\(ツ)_/¯", "thread_get_state(PAGEIN) returned 0x10000003: (ipc/send) invalid destination port", "thread_get_state(EXCEPTION) returned 0x10000003: (ipc/send) invalid destination port", "thread_get_state(FLAVOR) returned 0x10000003: (ipc/send) invalid destination port" ] } Any help would be greatly appreciated!
Replies
2
Boosts
0
Views
974
Activity
Jun ’26