Search results for

“build disappears”

51,332 results found

Post

Replies

Boosts

Views

Activity

App Store version stuck after Pending Developer Release – cannot add builds or create new versions
Hello everyone, I’m running into a situation in App Store Connect that appears to be a backend lock related to an approved version, and I’m looking for confirmation or similar experiences. Context: App had version 1.2.6 Version progressed to Pending Developer Release Before releasing to users, I chose Developer Reject I then edited the version number (to 1.2.7) Current State / Issue: After this, App Store Connect is effectively blocked: ❌ Cannot associate any builds to the version ❌ Uploading a build with the same version and higher build number does not help ❌ Cannot create a fresh version (no “+ Version” button is visible) ❌ App Store Connect API returns: ENTITY_ERROR.RELATIONSHIP.INVALID ❌ Remove Version / Delete Version is not available Even attempting brand‑new version numbers does not work. It looks like App Store Connect still considers the previously approved Pending Developer Release version to be active and locked internally. What I understand so far From my understanding:
0
0
20
1d
App crashes on launch for iOS 12 users after App Store release (Xcode 16.4) — BKSProcessErrorDomain bootstrap-failed
Hi everyone, I'm building an app in Xcode 16.4 with a minimum deployment target of iOS 12. The last time I built with this configuration was November 2025 — that build worked perfectly fine. I'm aware that builds from Xcode 16.4 will no longer be accepted by Apple after April 28, 2026, so I decided to push one final update before that deadline. Here's what I did: Built the app with no changes to build settings Uploaded to TestFlight Tested on iOS 12, iOS 26, and a few other versions — everything looked good Passed App Review Published to the App Store Now users on iOS 12 are reporting that the app crashes immediately on launch. Users on iOS 13-26 are unaffected. We've effectively lost a significant portion of our users overnight. We'd really like to restore functionality for them before April 28 — after that we plan to raise the minimum deployment target anyway. There are no crash logs available, as the app appears to never reach application code at all. Below are the relev
11
0
500
1d
Reply to Local Network permission on macOS 15 macOS 26: multicast behaves inconsistently and regularly drops
[quote='882610022, VictorPetitjean, /thread/809211?answerId=882610022#882610022, /profile/VictorPetitjean'] The just released 26.5 beta (build 25F5042g) seems to … solve FB21858319 [/quote] That’s great news. Thanks for testing on the beta seeds. [quote='882610022, VictorPetitjean, /thread/809211?answerId=882610022#882610022, /profile/VictorPetitjean'] when multiple versions of the app coexist on a machine, the latest … won't receive Local Network traffic after macOS reboot until its socket is closed and reopened [/quote] Hmmm. First up, as you’re aware, having multiple copies of an app installed is an ongoing source of local network privacy grief. I wish there was a better story on that front )-: However, your specific case sounds interesting. Lemme see if I understand it: You have Mac with multiple copies of your app installed. You restart the Mac. You launch one copy of the app. It’s immediately able to access the local network. You quit that. You launch the other copy of the app. It’s unable to a
1d
App rejected 13+ times for UIRequiredDeviceCapabilities after adding DeviceActivity extensions — what am I missing?
I've been stuck on Guideline 2.3 for two weeks now and I'm running out of ideas. My app is iPhone-only (UIDeviceFamily = [1]) and has been on the App Store since January. Version 2.1.9 passed review fine. The only change in 2.1.10 is adding two DeviceActivity extensions — a DeviceActivityMonitor and a DeviceActivityReport — for screen time-based stress detection. Every build since then gets rejected with the same message: The UIRequiredDeviceCapabilities key in the Info.plist is set up in such a way that the app will not install on the device used in review. Review devices: iPhone 14 Pro, iPhone 17 Pro Max, iPad Air M3. Here's what I've tried across 13+ submissions: UIRequiredDeviceCapabilities as [arm64] (array) — rejected Empty array [] — rejected Removed the key entirely — upload validation fails, Xcode re-injects arm64 anyway Post-build script to force [arm64] — rejected Dictionary format {arm64: true} — rejected Added com.apple.developer.family-controls to extension entitlements — rejec
1
0
51
1d
Reply to `NEProxySettings.matchDomains` / `exceptionList` not working as expected in `NEPacketTunnelProvider` (domain-scoped proxy not applied, and exceptions not bypassed)
Are you actually building a VPN product? I suspect that’s not the case, given that you’re using a placeholder for tunnelRemoteAddress. And if that’s true then… well… there are limits to how much I can help you here. My experience is that developers often try to use a packet tunnel provider for things that are not VPN. DTS doesn’t support those efforts because they tend to be very brittle. One of my erstwhile colleagues even wrote a technote about this, namely, TN3120 Expected use cases for Network Extension packet tunnel providers. If you’re trying to use a packet tunnel provider for something that isn’t VPN, I recommend that you watch WWDC 2025 Session 234 Filter and tunnel network traffic with NetworkExtension, where one of the engineers from the NE team explains the various alternatives that are available to you, including the new URL filter provider. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
1d
Reply to 26.4 RC documentation omits Foundation?!
Yep, seeing the same thing. There's a lot of other stuff broken with Xcode 26.4. For example, the Swift symbol NSTextAttachment.character is gone and we have to use NSAttachmentCharacter which in turn produces an error when compiling with Xcode 26.3 and earlier. (FB22341879). And then there's the broken Claude Agent support which forces you to re-login every few hours. Paired with the fact that macOS 26.4 cannot run Address Sanitizer builds from Xcode 26.3 and earlier, and you thus HAVE to use Xcode 26.4, I'm very frustrated with Apple's software quality right now.
1d
Reply to iOS 12.5.8 fails to bootstrap app
Addendum: I’ve created a simple minimal UIKit app that produces the same bootstrap error on the iPhone 5s with iOS 12.5.8. Launch storyboard shows, then suddenly disappears. The project is configured for automatically managed signing. My provisioning team profile expires in 11 months, my dev certificate in Oct 2026, and all other items in the details have checkmarks.
Topic: App & System Services SubTopic: General Tags:
1d
Looking for a visionOS collaborator (brief + feedback for spatial prototype)
Hi everyone, I’m a mixed reality designer currently building visionOS experiences (RealityKit + SwiftUI), and I’m working on a course at Arizona State University where we develop a project in response to a real-world client. I’m looking to collaborate with someone in the visionOS ecosystem who would be open to sharing a simple prompt or brief (nothing confidential), which I can use to create a proposal response. The outcome would include: Spatial concept + storyboard Interaction design direction Rough scope, timeline, and team structure Optional small prototype in visionOS The goal on my side is to better understand how spatial work is framed and communicated in real-world scenarios, especially within Apple’s ecosystem. The ask is very lightweight: 1–2 short check-ins during April or async feedback via email A bit about my work: Built Spatial Synesthesia for Apple Vision Pro Eye tracking interaction that isolates instruments in a live orchestral mix based on color perception Working with computer vis
0
0
185
1d
iOS 12.5.8 fails to bootstrap app
Hello, I released a new build for my app but it fails to run on iOS 12.5.8 (tested on iPad Air, iPhone 6, iPhone 5s). The launch storybard is shown, then the app stops abruptly. There is no crash log. It runs fine on iOS 13 or higher. Xcode 26.3 was showing a call stack (something with UIView) that did not include any app code. Now with Xcode 26.4 (and its new command line tools) there is an info popup with a debug metadata dump. However, I don’t intend to focus on Xcode here because it officially does not support iOS 12. It’s ok if I cannot debug, I just want the app to run on the device like the previous build did. Since there is no crash log, and the console is showing a bootstrap error, I believe my app code has not been executed and is therefore not at fault. Build 674 released on 23-Mar-2026: worked fine on iOS 12, built with Xcode 26.3 Build 675 released on 29-Mar-2026: Bootstrap error as described, with both Xcode 26.3 and 26.4 Deployment target = 12.4 Tried Instrum
5
0
239
1d
Unable to change build attached to version in App Store Connect
I have an app version (1.2.1) in App Store Connect that is showing Ready for Review status. It has an old build (1.2.0, build 4) attached to it. I uploaded a new build today (1.2.1, build 5) and need to swap it in, but there is no + or - button in the Build section of the version page, and clicking the current build number just navigates to its metadata page. I have tried: Creating a new version (1.2.1) — it auto-populated with the old build Uploading a new build with the correct version string — still no option to swap Looking for a Remove from Review button — it does not exist on my page Is there a way to detach the current build and attach the new one, or do I need to delete the version and start fresh? If so, will that affect my existing review thread with Apple? Any help appreciated.
0
0
53
1d
Unable to change build attached to version in App Store Connect
I have an app version (1.2.1) in App Store Connect that is showing Ready for Review status. It has an old build (1.2.0, build 4) attached to it. I uploaded a new build today (1.2.1, build 5) and need to swap it in, but there is no + or - button in the Build section of the version page, and clicking the current build number just navigates to its metadata page. I have tried: Creating a new version (1.2.1) — it auto-populated with the old build Uploading a new build with the correct version string — still no option to swap Looking for a Remove from Review button — it does not exist on my page Is there a way to detach the current build and attach the new one, or do I need to delete the version and start fresh? If so, will that affect my existing review thread with Apple?v
1
0
81
1d
Reply to Unable to Control Optical Zoom via USB (UVC) in Custom Swift App, While Prebuilt App Works
I suggest you get in touch with the maintainer of the project you cite. I tried building it, but it went off into the weeds when trying to parse the USB descriptor of three different UVC cameras. Have you found the code which enables/disables the zoom control? That should give you some clue. You said tt seems that the zoom control commands are not successfully sent or recognized by the camera - which is it - sent, or recognized? Does your code send the command? How? (show code). Does the camera or the USB stack return an error, and if so, which error? You're not giving us much to go on here.
1d
Production Mac app becomes progressively unusable in Issues workspace; Mac_Dev remains fast
The production macOS build is showing severe performance problems, while Mac_Dev performs normally. Observed behavior in production Mac build: Issue board scrolling becomes inconsistent or nearly unusable Changing an issue status in detail view is very slow Scrolling the status menu/options can be slow Typing in issue description/notes fields becomes sluggish Dragging issues between milestones/statuses on the board can lag badly Observed behavior in Mac_Dev: Board scrolling is smooth Status changes are immediate Typing in description fields is responsive Drag/drop between milestones works well Important comparison: Mac_Dev appears to run against an isolated local SwiftData store Production Mac app uses the normal CloudKit-backed store Because the same UI is fast in Mac_Dev, this does not look like a pure rendering problem Most likely cause is production store / CloudKit sync churn amplifying existing SwiftUI invalidation and save behavior Current hypothesis: The production app is saving or o
2
0
43
2d
App Store version stuck after Pending Developer Release – cannot add builds or create new versions
Hello everyone, I’m running into a situation in App Store Connect that appears to be a backend lock related to an approved version, and I’m looking for confirmation or similar experiences. Context: App had version 1.2.6 Version progressed to Pending Developer Release Before releasing to users, I chose Developer Reject I then edited the version number (to 1.2.7) Current State / Issue: After this, App Store Connect is effectively blocked: ❌ Cannot associate any builds to the version ❌ Uploading a build with the same version and higher build number does not help ❌ Cannot create a fresh version (no “+ Version” button is visible) ❌ App Store Connect API returns: ENTITY_ERROR.RELATIONSHIP.INVALID ❌ Remove Version / Delete Version is not available Even attempting brand‑new version numbers does not work. It looks like App Store Connect still considers the previously approved Pending Developer Release version to be active and locked internally. What I understand so far From my understanding:
Replies
0
Boosts
0
Views
20
Activity
1d
App crashes on launch for iOS 12 users after App Store release (Xcode 16.4) — BKSProcessErrorDomain bootstrap-failed
Hi everyone, I'm building an app in Xcode 16.4 with a minimum deployment target of iOS 12. The last time I built with this configuration was November 2025 — that build worked perfectly fine. I'm aware that builds from Xcode 16.4 will no longer be accepted by Apple after April 28, 2026, so I decided to push one final update before that deadline. Here's what I did: Built the app with no changes to build settings Uploaded to TestFlight Tested on iOS 12, iOS 26, and a few other versions — everything looked good Passed App Review Published to the App Store Now users on iOS 12 are reporting that the app crashes immediately on launch. Users on iOS 13-26 are unaffected. We've effectively lost a significant portion of our users overnight. We'd really like to restore functionality for them before April 28 — after that we plan to raise the minimum deployment target anyway. There are no crash logs available, as the app appears to never reach application code at all. Below are the relev
Replies
11
Boosts
0
Views
500
Activity
1d
Reply to Local Network permission on macOS 15 macOS 26: multicast behaves inconsistently and regularly drops
[quote='882610022, VictorPetitjean, /thread/809211?answerId=882610022#882610022, /profile/VictorPetitjean'] The just released 26.5 beta (build 25F5042g) seems to … solve FB21858319 [/quote] That’s great news. Thanks for testing on the beta seeds. [quote='882610022, VictorPetitjean, /thread/809211?answerId=882610022#882610022, /profile/VictorPetitjean'] when multiple versions of the app coexist on a machine, the latest … won't receive Local Network traffic after macOS reboot until its socket is closed and reopened [/quote] Hmmm. First up, as you’re aware, having multiple copies of an app installed is an ongoing source of local network privacy grief. I wish there was a better story on that front )-: However, your specific case sounds interesting. Lemme see if I understand it: You have Mac with multiple copies of your app installed. You restart the Mac. You launch one copy of the app. It’s immediately able to access the local network. You quit that. You launch the other copy of the app. It’s unable to a
Replies
Boosts
Views
Activity
1d
App rejected 13+ times for UIRequiredDeviceCapabilities after adding DeviceActivity extensions — what am I missing?
I've been stuck on Guideline 2.3 for two weeks now and I'm running out of ideas. My app is iPhone-only (UIDeviceFamily = [1]) and has been on the App Store since January. Version 2.1.9 passed review fine. The only change in 2.1.10 is adding two DeviceActivity extensions — a DeviceActivityMonitor and a DeviceActivityReport — for screen time-based stress detection. Every build since then gets rejected with the same message: The UIRequiredDeviceCapabilities key in the Info.plist is set up in such a way that the app will not install on the device used in review. Review devices: iPhone 14 Pro, iPhone 17 Pro Max, iPad Air M3. Here's what I've tried across 13+ submissions: UIRequiredDeviceCapabilities as [arm64] (array) — rejected Empty array [] — rejected Removed the key entirely — upload validation fails, Xcode re-injects arm64 anyway Post-build script to force [arm64] — rejected Dictionary format {arm64: true} — rejected Added com.apple.developer.family-controls to extension entitlements — rejec
Replies
1
Boosts
0
Views
51
Activity
1d
Reply to `NEProxySettings.matchDomains` / `exceptionList` not working as expected in `NEPacketTunnelProvider` (domain-scoped proxy not applied, and exceptions not bypassed)
Are you actually building a VPN product? I suspect that’s not the case, given that you’re using a placeholder for tunnelRemoteAddress. And if that’s true then… well… there are limits to how much I can help you here. My experience is that developers often try to use a packet tunnel provider for things that are not VPN. DTS doesn’t support those efforts because they tend to be very brittle. One of my erstwhile colleagues even wrote a technote about this, namely, TN3120 Expected use cases for Network Extension packet tunnel providers. If you’re trying to use a packet tunnel provider for something that isn’t VPN, I recommend that you watch WWDC 2025 Session 234 Filter and tunnel network traffic with NetworkExtension, where one of the engineers from the NE team explains the various alternatives that are available to you, including the new URL filter provider. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Replies
Boosts
Views
Activity
1d
Reply to 26.4 RC documentation omits Foundation?!
Yep, seeing the same thing. There's a lot of other stuff broken with Xcode 26.4. For example, the Swift symbol NSTextAttachment.character is gone and we have to use NSAttachmentCharacter which in turn produces an error when compiling with Xcode 26.3 and earlier. (FB22341879). And then there's the broken Claude Agent support which forces you to re-login every few hours. Paired with the fact that macOS 26.4 cannot run Address Sanitizer builds from Xcode 26.3 and earlier, and you thus HAVE to use Xcode 26.4, I'm very frustrated with Apple's software quality right now.
Replies
Boosts
Views
Activity
1d
Reply to iOS 12.5.8 fails to bootstrap app
Addendum: I’ve created a simple minimal UIKit app that produces the same bootstrap error on the iPhone 5s with iOS 12.5.8. Launch storyboard shows, then suddenly disappears. The project is configured for automatically managed signing. My provisioning team profile expires in 11 months, my dev certificate in Oct 2026, and all other items in the details have checkmarks.
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1d
Looking for a visionOS collaborator (brief + feedback for spatial prototype)
Hi everyone, I’m a mixed reality designer currently building visionOS experiences (RealityKit + SwiftUI), and I’m working on a course at Arizona State University where we develop a project in response to a real-world client. I’m looking to collaborate with someone in the visionOS ecosystem who would be open to sharing a simple prompt or brief (nothing confidential), which I can use to create a proposal response. The outcome would include: Spatial concept + storyboard Interaction design direction Rough scope, timeline, and team structure Optional small prototype in visionOS The goal on my side is to better understand how spatial work is framed and communicated in real-world scenarios, especially within Apple’s ecosystem. The ask is very lightweight: 1–2 short check-ins during April or async feedback via email A bit about my work: Built Spatial Synesthesia for Apple Vision Pro Eye tracking interaction that isolates instruments in a live orchestral mix based on color perception Working with computer vis
Replies
0
Boosts
0
Views
185
Activity
1d
iOS 12.5.8 fails to bootstrap app
Hello, I released a new build for my app but it fails to run on iOS 12.5.8 (tested on iPad Air, iPhone 6, iPhone 5s). The launch storybard is shown, then the app stops abruptly. There is no crash log. It runs fine on iOS 13 or higher. Xcode 26.3 was showing a call stack (something with UIView) that did not include any app code. Now with Xcode 26.4 (and its new command line tools) there is an info popup with a debug metadata dump. However, I don’t intend to focus on Xcode here because it officially does not support iOS 12. It’s ok if I cannot debug, I just want the app to run on the device like the previous build did. Since there is no crash log, and the console is showing a bootstrap error, I believe my app code has not been executed and is therefore not at fault. Build 674 released on 23-Mar-2026: worked fine on iOS 12, built with Xcode 26.3 Build 675 released on 29-Mar-2026: Bootstrap error as described, with both Xcode 26.3 and 26.4 Deployment target = 12.4 Tried Instrum
Replies
5
Boosts
0
Views
239
Activity
1d
Unable to change build attached to version in App Store Connect
I have an app version (1.2.1) in App Store Connect that is showing Ready for Review status. It has an old build (1.2.0, build 4) attached to it. I uploaded a new build today (1.2.1, build 5) and need to swap it in, but there is no + or - button in the Build section of the version page, and clicking the current build number just navigates to its metadata page. I have tried: Creating a new version (1.2.1) — it auto-populated with the old build Uploading a new build with the correct version string — still no option to swap Looking for a Remove from Review button — it does not exist on my page Is there a way to detach the current build and attach the new one, or do I need to delete the version and start fresh? If so, will that affect my existing review thread with Apple? Any help appreciated.
Replies
0
Boosts
0
Views
53
Activity
1d
Unable to change build attached to version in App Store Connect
I have an app version (1.2.1) in App Store Connect that is showing Ready for Review status. It has an old build (1.2.0, build 4) attached to it. I uploaded a new build today (1.2.1, build 5) and need to swap it in, but there is no + or - button in the Build section of the version page, and clicking the current build number just navigates to its metadata page. I have tried: Creating a new version (1.2.1) — it auto-populated with the old build Uploading a new build with the correct version string — still no option to swap Looking for a Remove from Review button — it does not exist on my page Is there a way to detach the current build and attach the new one, or do I need to delete the version and start fresh? If so, will that affect my existing review thread with Apple?v
Replies
1
Boosts
0
Views
81
Activity
1d
Reply to App Store Connect crashes when configuring App Clip default experience (appClipDefaultExperience undefined)
@azdzadazsqsx Thanks for this, We're unable to share any updates on specific reports on the forums, however I would encourage you to try the new 26.5 beta and let me know if that build fixes your issue. Let me know! Albert Pascual
  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
1d
Can I drop universal support?
Hi. I have a universal app in the AppStore. Can I drop the Intel support and build the app as M only and still have it distributed in the app store? This was a problem the last time I set up my build environment but I am not sure if that is still the case. Regards
Replies
0
Boosts
0
Views
61
Activity
1d
Reply to Unable to Control Optical Zoom via USB (UVC) in Custom Swift App, While Prebuilt App Works
I suggest you get in touch with the maintainer of the project you cite. I tried building it, but it went off into the weeds when trying to parse the USB descriptor of three different UVC cameras. Have you found the code which enables/disables the zoom control? That should give you some clue. You said tt seems that the zoom control commands are not successfully sent or recognized by the camera - which is it - sent, or recognized? Does your code send the command? How? (show code). Does the camera or the USB stack return an error, and if so, which error? You're not giving us much to go on here.
Replies
Boosts
Views
Activity
1d
Production Mac app becomes progressively unusable in Issues workspace; Mac_Dev remains fast
The production macOS build is showing severe performance problems, while Mac_Dev performs normally. Observed behavior in production Mac build: Issue board scrolling becomes inconsistent or nearly unusable Changing an issue status in detail view is very slow Scrolling the status menu/options can be slow Typing in issue description/notes fields becomes sluggish Dragging issues between milestones/statuses on the board can lag badly Observed behavior in Mac_Dev: Board scrolling is smooth Status changes are immediate Typing in description fields is responsive Drag/drop between milestones works well Important comparison: Mac_Dev appears to run against an isolated local SwiftData store Production Mac app uses the normal CloudKit-backed store Because the same UI is fast in Mac_Dev, this does not look like a pure rendering problem Most likely cause is production store / CloudKit sync churn amplifying existing SwiftUI invalidation and save behavior Current hypothesis: The production app is saving or o
Replies
2
Boosts
0
Views
43
Activity
2d