Same here. In addition, when I opened Console, there were a constant stream of Xcode errors similar to this:
"found no value for key DVTShowAllSimulatorRunDestinations in CFPrefsSearchListSource<0x600000679780> (Domain: com.apple.dt.Xcode, Container: (null))"
Switching off the "Execute in parallel (if possible)" option helped to run tests, but the errors stream in console didn't stop.
Xcode Version 15.0 (15A240d).
Post
Replies
Boosts
Views
Activity
We're experiencing thousands of NO_CRASH_LOG crashes like the one described in this thread. This all started with iOS 15 release. When you open a .crash file it shows just a couple of dyld calls and then EXC_CORPSE_NOTIFY with a system watchdog killing the app during launch after 1 minute of inactivity. Binary images section only contains .dyld and sometimes a few other system .dylib-s - no modules from our app. I'm attaching an example here? I filed a bug to Apple via feedback.apple.com, but they replied that they need system logs from affected devices, which we cannot provide because the issue (according to the Apple's Xcode reporting system) happens on our AppStore users devices, but we can't reproduce it by ourselves. My radar is still in "open" status bus since then there hasn't been any activity. I know that a lot of people also reporting this, and there're also a lot of forum discussions, eg this one: https://developer.apple.com/forums/thread/710463
Does anybody have an answer for this?
2022-07-24_11-09-56.9474_-0500-131fd7580c89bb6093b56e883161e3bb6182838c.crash
We're experiencing thousands of NO_CRASH_LOG crashes like the one described in this thread. This all started with iOS 15 release. When you open a .crash file it shows just a couple of dyld calls and then EXC_CORPSE_NOTIFY with a system watchdog killing the app during launch after 1 minute of inactivity. Binary images section only contains .dyld and sometimes a few other system .dylib-s - no modules from our app. I'm attaching an example here? I filed a bug to Apple via feedback.apple.com, but they replied that they need system logs from affected devices, which we cannot provide because the issue (according to the Apple's Xcode reporting system) happens on our AppStore users devices, but we can't reproduce it by ourselves. My radar is still in "open" status bus since then there hasn't been any activity. I know that a lot of people also reporting this, and there're also a lot of forum discussions, eg this one: https://developer.apple.com/forums/thread/690514
Does anybody have an answer for this?
2022-07-24_11-09-56.9474_-0500-131fd7580c89bb6093b56e883161e3bb6182838c.crash