Any idea what happens when we hit the 1000 hour limit? Will all of our jobs just stop, or will there be some pro-rated add on for hours used until the end of the month?

I assume the ".sh" file extension is suppressed by default in the UI? Also, check file perm on the script is correct and its added to the target that provides the scheme you are building against. The default shell here is 'zsh' and I can't imagine that 'sh' isn't also available.

We are seeing this too in our CI pipelines as well. As of Xcode 14, when uploading to iTC, no Apple generated dSYMS are being generated for download. We found that uploading the dSYM generated locally directly to Firebase was the way forward. As for Firebase not being able to process what you give it is odd. As long as the Bundle ID and MARKETING_VERSION are in sync, there should be no reason the mapping can't occur. I'd reach out Google directly and ask them whats up. I've found their turnaround and quality of support to be pretty good wrt Firebase.

+1 for this. (FB17093798) We've tried all sorts of non-standard workarounds (LLDB init settings), swapping lldb-rpc-server versions. All to no avail. Don't forget to boost the initial post here. Apple does see well bosted issues quicker.

I'm finding good success with the following: echo "settings set plugin.process.gdb-remote.packet-timeout 300" > ~/.lldbinit This is on Sequoia with XC 16.3 (16E140) running an iPhone 16 Pro simulator (18.4) On my M1/64GB laptop, it is unmercifully slow, but I can debug and "work" with things w/o having the debugger crash and disconnect.

I'm seeing this in 16.3 as well. Possibly due to ancient .xcframeworks injected by Carthage. An older version of Xcode should be able to view the offending .profraw files and at least dump some info to show what framework it came from. Now on Sequoia, so going back far enough is no longer an option. Boo!

I've opened Feedback: FB17628220 for this. There appears to be something wrong with the later 18.3, .4 SDKs as the profraw file that is pulled from the Simulator is just in the wrong format. FWIW, also tested in Xcode 16.4 (iOS 18.5) and still no go.