0

I'm working on a document-based app and hence also working on the FileProvider extension for the app, as Apple suggests it

I've pretty much achieved all the basic functionalities for the extension(listing, previewing files, performing certain user-actions and stuff)

So far, to debug the extension, I'll either attach it to process(from the 'Debug' menu) or run the FileProvider scheme through the Files app. Both of these methods are usable only to an extent and results in a 'frozen Files app' after a couple of tries. (Breakpoints don't work properly too, at times)

I'll have to restart my device or force-quit Xcode for this to work again(every couple or more tries!) and this is so annoying!! (Files app bug?!)

Is there a fix or some better way to debug the extension? I've tried the same with multiple devices just to ensure if I'm not the only one but happens on every single device I tried

Lokesh SN
  • 1,583
  • 7
  • 23
  • Show us some code, plz! Maybe you're blocking the main thread completely? Hard to tell without your code. – d4Rk Dec 26 '18 at 11:04
  • Hey! Thanks a lot for your response! I don't have any problems with code. All of these start when I try to debug my code to better understand the process(callbacks at places and stuff). All I need is to know is if there is a better debugging solution/method available for the extension – Lokesh SN Dec 26 '18 at 11:45
  • And when I'm talking about Files app getting frozen, it's the whole app itself and not just my section of the app(maybe that's why you're confused with threading and all) – Lokesh SN Dec 26 '18 at 11:48

0 Answers0