I quickly updated the File plugin to do the local file uri stuff in
resolveLocalFileSystemURI in the background using [self.commandDelegate
runInBackground:^{}].
It works and allows my app interface to respond while the FS calls are
resolving. Is this approach crazy or obviously broken in some way?
Cheers,
Mike
On 10/12/13 12:57 PM, Ian Clelland wrote:
Unfortunately, except in a few cases (accessing asset-library urls and
actually reading and writing files) it is blocking.
Creating, finding, deleting and renaming regular files are all currently
synchronous operations on iOS. Reading and writing contents are async, and
shouldn't block anything.
Once I've pushed up the last changes to the File plugin, it's on my list of
things to tackle.
Ian
On Tue, Dec 10, 2013 at 11:45 AM, Michael Gauthier <[email protected]>wrote:
When using the File plugin on iOS I get a lot of "THREAD WARNING Plugin
should use a background thread" messages. Is the iOS plugin actually using
blocking filesystem calls internally?
Cheers,
Mike
