Post marked as Apple Recommended
Apple is aware of this issue, and thank you filing FB13769072 to bring it to our attention. Please see this post for an easy workaround.
Post marked as Apple Recommended
Apple is aware of this issue. If your Mac is affected, please see this post for an easy workaround.
Post not yet marked as solved
Please file an Enhancement Request in Feedback Assistant for a supported way to build an XCFramework from a Swift Package. Please post the number here once you do. There isn't a supported way to do this with Xcode 15, and as you found, there's lots of interesting corners that supported solution needs to fully consider.
Post not yet marked as solved
The App Store experienced a temporary issue that is now resolved. Please see this other thread.
The circumstances around what you're seeing with these crash reports uncovered multiple issues present in builds of watchOS 9, and also early versions of watchOS 10, and the source of the issue was likely triggered when watchOS updated between watchOS versions with your app already installed.
The complete set of issues is resolved with the watchOS 10.2 beta that is now available. Upgrading to watchOS 10.2 is the best path so you no longer encounter these issues.
If you remain on watchOS 9 as part of testing your app, you can remove and reinstall your app as a workaround. For any of your customers using your app on watchOS 9, you can provide an update to your app, as the process of installing the update will also correct the issue.
Post not yet marked as solved
There is no API available to determine this.
Post not yet marked as solved
0xdead10cc is your key, and there are probably other key clues in background threads regarding dead file locks, such as threads that are clearly doing file or database work. Please see our crash report documentation for the definition of 0xdead10cc and some things you can do.
The simulator installations do not go inside the Xcode application bundle, they exist elsewhere on the system. However, given your download setup, you might prefer to download the simulators from the Developer website, so you can cache the download locally. You can then install them through a documented command.
However, after 3-4 hours of operation, the CPU utilization suddenly drops to around 10%.
From your text, it's unclear if this is a problem — do you see your app's performance significantly impacted in a way that you're concerned about? Also, if your app is expected to do a significant amount of work over a long stretch of time, it's possible you've reached a system thermal threshold, and the system is making adjustments to allow it to cool off. Without knowing much more about your situation here, this is a bit of speculation on my part. APIs like ProcessInfo.ThermalState can be helpful here.
I'm also wondering why the thread count in the picture goes into the 3000s after 3-4 hours. I'm also wondering if this is an issue with asynchronous processing.
You might be witnessing the thread number increasing, but not the overall active thread count, depending on how you use different concurrency APIs, like Swift Concurrency or Dispatch. The system may create and destroy threads over time, so you see this identifier going up over the hours for each new thread that the system creates, but it's also just an identifier. Whether or not this is a crucial problem is an "it depends" situation where the details in your code matter.
The analysis process through Profile in Instruments is also tricky in terms of catching the exact moment of a sudden change in CPU utilization.
What do you find tricky? You can let Instruments run for hours to capture the data, though the resulting trace file will be large. There are also features under File > Recording Options that let you record a rolling window of data, such as keeping only the most recent data of a set time interval that you can choose.
I'm looking for advice from people who have some experience with performance/memory optimization in iOS environments, not necessarily macOS.
If you remain stuck, this is a great use for a Technical Support Incident that's part of the Apple Developer Program. By using opening of those incidents, you'll be able to share your Instruments trace with an Apple Engineer — myself or some of my colleagues — and get deeper insights with the complete data you have available. The trace files collected by Instruments are large, so we can provide you with an upload location to share it with us privately. Further, if you have additional information or context that you can share privately that you've chosen not to share in this forum post, please include it in your TSI.
Post not yet marked as solved
This is called out in the Xcode 15 Release Notes as a known issue:
Interface Builder documents using custom App fonts may load incorrect font at runtime. (113624207) (FB12903371) Workaround: Set font manually in code.
Post not yet marked as solved
Please file an enhancement request through Feedback Assistant and describe how this suggestion is helpful to your app, and then post the FB number here.
Post not yet marked as solved
Please contact Xcode Cloud's support team.
Post not yet marked as solved
This is a known issue, and cited in the iOS 17 beta 8 release notes:
On iOS, using an Observable object’s property as a selection value of a List inside NavigationSplitView may cause a “Simultaneous accesses to …” error when a list selection is made via tap gesture. (113978783)
Workaround: There is no current workaround for Observable properties. Alternatives include factoring out the selection value into separate state stored outside the object, or using ObservableObject instead.
Post not yet marked as solved
Your app has failed due to your third-party runtime throwing an exception. You should consult with support for React Native to address these crashes.
You need the Framework template. All dynamic libraries must be frameworks on iOS.
