Indeed that solved it, thanks for letting us know!

@DTS Engineer Thanks a lot!

Jordan and I chatted on Mastodon and turns out I can still reproduce the issue on subsequent runs. First run works alright, next time I run the sample project it breaks like the OP. See: https://mastodon.social/@xmollv/115136387611606344 // @DTS Engineer

Yeah I had tried them but none of them seem to give me the results I want. Did it work on your end? The code is the one I shared above, tried many modifiers on that one and nothing seems to work for me...

Here's the FB number: FB18598206. Also put up a sample project to easily reproduce the issue: https://github.com/xmollv/ShortcutsOptionalSelectionBug. Thanks!

Hi @DTS Engineer, thanks for your response! I do believe this should work as expected without the need for pagination. On UIKit + CoreData you don't need pagination, using an NSFetchedResultsController allows you to display as many items as you wish on a UITableView/UICollectionView without any hangs whatsoever. I've filed FB15507372 and put up the project for anyone to download and run here: https://github.com/xmollv/SlowData

@alexcason Are you getting the same backtrace as me? Indeed disabling Thread Performance Checker allows us to not have this spike, but it also means we're opting out of something that seems really useful. If the backtrace you get is the same as us, I'm pretty sure Apple will need to fix this internally 😬

@1gor We had been releasing before. It broke today when they released the RC, you can of course change the Xcode used to the latest that's not a RC (what we did to unblock us) but this means we have to keep switching which version of Xcode our builds use instead of using the latest stable (non-RC one). Hopefully somebody on the Xcode Cloud team will pick this up and allow us to select latest (non-RC) ones!

Thanks for the reply! Yeah, I did check but at that point everything was green... seems to have been solved now tho!

Seems to be working fine again now!

Seems to be working fine on our end now, thank you!

No, I ended up not using Core Data on extensions, had to many issues with that.

Yes, it seems to be working fine now. PS: I marked by mistake a comment as the solved answer, and there's no way to change that nor delete my response. If you (or anyone at Apple) could fix it, that'd be great.

Thanks for such a detailed response, it helped me a lot to learn more about how the presentation of Share Extensions works. I believe that I'd be able to achieve what I want using the NSExtensionActionWantsFullScreenPresentation, but ideally there should be a way to customize the detents as suggested. I've opened a feedback for it: FB9762713. Thank you!

Thank you!