Thanks, but I know that already. What I was trying to ask is something different: When I look at the crashes of my published app in the Xcode Organizer by selecting a crash and then using "Open in Project..." I see on which line of code the crash did happen. But is it also possible for those crashed to get a "terminating app due to..." reason?

I am facing the same issue. The extension does not seem to be able to openURL the main app. Is there a solution for this problem or is it still not possible?

The app is a universal app with just one target. I did open a code level technical support request for this issue. I can work around it with this crazy piece of code: @try { cell = [tableView dequeueReusableCellWithIdentifier:reuseIdentifierTextCell forIndexPath:indexPath]; } @catch(id exception) { NSArray *topLevelObjects = [[NSBundle mainBundle] loadNibNamed:@"ChatTextCellCondensed" owner:self options:nil]; cell = [topLevelObjects objectAtIndex:0]; }

Unfortunately no, we never got any reliable way to fix this.

I'm also affected by this, but only on certain devices. If you search the forums you'll find other users reporting it. However it is not clear whether this is an iOS bug that is being worked on or not.Did you find any workaround yet?

I'm affected by the same issue: only on certain devices and only since iOS 13.3. Currently only on iPads.My deployment target is iOS 12.4. What deployment target are you using? Probably that's what's different from those apps that are not affected?

I have the same problem. Did everything according to the WWDC video and I can trigger execution via lldb _simulateLaunchForTaskWithIdentifier, but other than that, it's never executed. Is there any way to analyze whats going on?

I have the same problem. Did everything according to the WWDC video and I can trigger execution via lldb _simulateLaunchForTaskWithIdentifier, but other than that, it's never executed. Is there any way to analyze whats going on?