How can I ignore it? the build was not accepted, not even showing up in TestFlight.
Post not yet marked as solved
With Xcode 13.2.1, Mac Monterey 12.2, this issue is still unfixed on M1 MBP. So annoying! Had to switch back to Intel Mac Mini quite often. What a waste.
Still having this same issue on M1 mac.
Seems Xcode 12.5.1 has largely fixed it. I've been using it for 3 hours it's improved from 15 seconds frozen to 3 seconds frozen post launch.
Not sure if this is exactly the same issue but my App will be unresponsive to mouse click for about 10 seconds after run in simulator. I've tried everything the only one worked was to delete the simulator then add it back. It only worked for maybe half a day then it'll come back unfortunately.
Post not yet marked as solved
Same question...have you found a solution?
Post marked as Apple Recommended
I faced a similar issue after enabled DarkMode - yes we've only enabled it recently. Turned out when the App went to background it was trying to take a snapshot of the top view, which I suspect is required by DarkMode, and will layout the views again, hence calling the NSAttributedString initWithData in my cell constructing method. I could see that this crash happened during App is backgrounded in Crashlytics, even tho it's still on main thread. I could also reproduce it easily once I figured it out.
The fix is pretty straightforward: to use a lazy var to init that attributedStr to prevent it from being called again when the App goes to background.
