Hello, I am looking to develop a relationship with a developer that has experience running through the IOS build approval process. To elaborate, my team and I have designed and built a software application which is working through the Apple Developer review process to have the app approved and released to the App Store. Unfortunately, there has been some challenges, simple challenges in my eyes with our interface preventing Apple from approving our application. Happy to elaborate further. A primary problem and solution I have seen is the software build was testing solely on the iPhone but as recently directed it seem the application must be accessible on iPad as well. With this the case, I have experience some software platforms where on the ipad the interface is not displayed on the whole screen. I am looking for direction on how to implement this setup for the 1st IOS build. Another concern from Apples Developer Review team is the App Tracking Transparency kit may need to be imple
Search results for
build disappears
49,347 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
This is happening to our team as well. We had a build run overnight last night, stuck archiving. As well as several yesterday that ran for many hours (more than 2 hours) and had to be manually canceled. It was failing because the version string in our Info.plist was the same as an approved, Pending Developer Release version submitted on App Store Connect. We received (and missed) emails about this, until one of us noticed them this morning. Usually that sort of failure is reported in Xcode Cloud logs, and results in a failure of the job on-time. We should be refunded for the hours that the job spent idling, however applicable. Feedback assistant ticket: FB20279578
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
Steps to Reproduce: Connect a MacBook Pro (lid closed) to a large external monitor. Run the SDL3 testwm test application. git clone https://github.com/libsdl-org/SDL.git cmake -S . -B build -DBUILD_SHARED_LIBS=OFF -DSDL_TESTS=ON cmake --build build The testwm binary will be located in the build/test directory. Move the application window around the left edge of the external display. Observed Result: WindowServer crashes. System Configuration: MacBook Pro M3 Max, macOS Sequoia 15.6.1 LG GX9, 5120x2160 resolution, running at 165 Hz refresh rate Lid closed, single external display Panic Log: panic(cpu 7 caller 0xfffffe0027f61d5c): mismatched swapID's 6386399 vs 6386400n @UnifiedPipeline.cpp:14570 Debugger message: panic Memory ID: 0xff OS release type: User OS version: 24G90 Kernel version: Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:55 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6031 Fileset Kernelcache UUID: 8AA69CD2038CD2BAE2ED364428F4DBEA Kernel UUID: 75A21406-D046
@storj Cool story. For whatever reason I'm not getting email notifications when people respond to my threads. Still think it would be great if building with the 'Debug Configuration' caused the same permission error to accurately simulate the behavior you'll get in the wild but maybe there is a good reason why Apple doesn't want to do this. I dk.
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
Thank you for your response! Attached are some crash reports that represent attempts to merge in two separate branches that take our relatively stable (not crashing in the ways described above) main branch and introduce (or reintroduce) the observed crashes. Also, ASan is enabled for two out of four of the reports (one per branch) and disabled for the others. Did you try doing this incrementally? If you have a bunch of them, it’d be interesting to see which combinations do and don’t reproduce the problem. I will try this, but one of the primary issues with tracking these crashes down has been not knowing if/when they are truly eliminated as they tend to come and go after minimal code changes. It seems that almost any change to the code, or which files/libraries/frameworks are included in the build will change how the crashes manifest, or in some cases do not manifest. This is a bit of a long shot, but are there any things in particular (in crash reports or otherwise) we can look for in the future tha
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
We have had 2 Builds so far stuck archiving. Both indicate in their logs that Build Archive took a normal amount of time (9m and 19m) but the step Archive - iOS never finished. One of them ran for more than 6 days until we noticed and canceled it. The other one ran for 18 hours, and also had to be canceled manually. They were in two different projects, with no significant changes. The first build ran on Xcode 16.4 (16F6) and macOS Sequoia 15.6 (24G84), which we had had no issues like this with until just now, and the second ran on Xcode 26 (17A324) and macOS Tahoe 26 (25A354). We tested our app on the newest Xcode version and had no issues. Submitted report using feedback assistant: FB20279737.
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
In a new document-based macOS app project created in Xcode, some of the default system-provided menu commands appear without their standard icons in the menu bar. Steps to Reproduce: 1. In Xcode, create a new macOS “Document App” project (using Swift/SwiftUI or AppKit template). 2. Build and run the project. 3. Open the app’s main menu bar and examine the default items such as New Document, Open…, Save, Duplicate, etc. Expected Results: System-provided menu items (e.g. Open…, Save, Duplicate) should display their standard SF Symbol–based icons automatically, as they do in TextEdit and other system apps. Actual Results: Some of these menu items display only text, with no icon namely: Services Open Recent Revert To Share This happens even though the items are the system-managed defaults generated by the document-based app template. Notes: • No code modifications were made — this occurs in a fresh, unedited template project. • Behavior seen on macOS 26.0 (25A354). • Xcode Version 26.0 (17A324) used.
I reported this same issue back in January, we haven't been able to run our automated tests in our build infrastructure for 9 months now.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
The app “Wi-Fi Aware Sample” on Bojie的iPhone quit unexpectedly. Domain: IDEDebugSessionErrorDomain Code: 20 Failure Reason: Message from debugger: The LLDB RPC server has crashed. You may need to manually terminate your process. The crash log is located in ~/Library/Logs/DiagnosticReports and has a prefix 'lldb-rpc-server'. Please file a bug and attach the most recent crash log. User Info: { DVTErrorCreationDateKey = 2025-09-17 10:26:56 +0000; IDEDebugSessionErrorUserInfoUnavailabilityError = Error Domain=com.apple.dt.deviceprep Code=-10 Fetching debug symbols for BojieU7684iPhone UserInfo={NSLocalizedRecoverySuggestion=Xcode will continue when the operation completes., NSLocalizedDescription=Fetching debug symbols for BojieU7684iPhone}; IDERunOperationFailingWorker = DBGLLDBLauncher; } Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { device_identifier = 00008101-001E29E01E63003A; device_isCoreDevice = 1; device_model = iPhone13,3; device_osBuild = 26.0 (23A341); device_osBuild_monotonic = 23000
Hi there, My app update submission was stuck in Waiting for Review state for over 80 hours. Yesterday I canceled and resubmitted it again after 3.5 days of inactivity, but this time it still hasn’t moved forward. I'd like to be sure that there is no issues on my side during sending build to review, cuz I noticed that submit app flow was slightly changed a week ago. Usually app update was verified in 10-20 hours, but now it's stuck. Thank you in advance.
just watched the Build an appkit app with the new design video. There is a section on the scroll edge effect but there is no mention how to deal with it. How can I customize my drawing when my view is inside the scroll edge effect There was stuff about Split View, toolbar items, but nothing about collection view.
Topic:
UI Frameworks
SubTopic:
AppKit
Tags:
This has all the hallmarks a subtle memory management bug, possibly one that triggered by threading issues. These often result in weird behaviour like this. It looks like you’ve already tried ASan and TSan, which is a good. The other most popular tool for such issue is zombies. You should try that. See Standard Memory Debugging Tools for info and documentation references. One thing to note here is that ASan and TSan only work with code that you build. If the problem lies in a third-party library that you get as a binary rather than source code, these tools won’t help. And so… [quote='800689021, reidly, /thread/800689, /profile/reidly'] Removing all 3rd party libraries or frameworks … mostly worked in that the crashes went away [/quote] Did you try doing this incrementally? If you have a bunch of them, it’d be interesting to see which combinations do and don’t reproduce the problem. Finally, please post some example crash reports. I don’t need dozens, but a few that illustrate the more common crash sc
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
Sadly, I can’t read Chinese, so I’m answering based on a machine translation. I tried this out here in my office and saw exactly the same problem: Using Xcode 26.0, I created a new project from the iOS > App template. In one of the Swift files, I added the line import AssetsLibrary. The compiler errors with Failed to build module 'AssetsLibrary'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 6.2 effective-5.10 (swiftlang-6.2.0.17.14 clang-1700.3.17.1)', while this compiler is 'Apple Swift version 6.2 effective-5.10 (swiftlang-6.2.0.19.9 clang-1700.3.19.1)'). Please select a toolchain which matches the SDK. This is obviously a bug and I encourage you to file a report about it. Please post your bug number, just for the record. Having said that, Assets Library was deprecated in iOS 9 and Xcode 26’s minimum supported deployment target, per the table on this page, is iOS 15. There is literally no way to use Xcode 26 to build an app for an iOS version whe
Topic:
Media Technologies
SubTopic:
General
Tags:
So, lemme see if I have this right: You’re building a Mac app. That ships on the Mac App Store. And you want to be able to let the user select another app… And then delete that app. Is that right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
Core OS
Tags:
The code is shown as follows. Once the tabViewBottomAccessory is enabled, the tabViewSidebarBottomBar disappears. TabView { Text(tab a) .tabItem { Image(systemName: a.square) Text(Tab A) } .ignoresSafeArea(edges: [.all]) Text(tab b) .tabItem { Image(systemName: b.square) Text(Tab B) } .ignoresSafeArea(edges: [.all]) } //.tabViewBottomAccessory { // Text(tabViewBottomAccessory) //} .tabBarMinimizeBehavior(.onScrollDown) .tabViewStyle(.sidebarAdaptable) .tabViewSidebarBottomBar { Text(tabViewSidebarBottomBar) }