Obj-C V2 disk error after uploadUrl

Thanks for the post! I'm glad to hear you were able to work around this issue, though I'm not sure I understand exactly what the issue was. When using uploadUrl, the SDK should upload the data from whatever URL you supply, but as far as I'm aware it shouldn't then affect the local file, e.g., in a way to cause an error like this.

Is that the entirety of the output you got when you ran in to that issue?

I will give you as much info as I can. First off I upload the file using a method like this:

 

[client uploadUrl:@"/File.sqlite" mode:[[[DBFILESWriteMode alloc] initWithOverwrite] autorelease] autorename:@NO clientModified:nil mute:@YES inputUrl:inputUrl];

Then, when I next do a 

[NSFetchedResultsController performFetch:]

against the database, I get the following error:

2017-03-31 15:53:59.022073 App[12260:3128970] [error] error: (6922) I/O error for database at /var/mobile/Containers/Data/Application/172114D0-4346-48F1-ACAE-23A76EC9C339/Documents/File.sqlite.  SQLite error code:6922, 'disk I/O error'
CoreData: error: (6922) I/O error for database at /var/mobile/Containers/Data/Application/172114D0-4346-48F1-ACAE-23A76EC9C339/Documents/App.sqlite.  SQLite error code:6922, 'disk I/O error'
2017-03-31 15:56:29.270469 App[12260:3128970] [error] error: -executeRequest: encountered exception = I/O error for database at /var/mobile/Containers/Data/Application/172114D0-4346-48F1-ACAE-23A76EC9C339/Documents/File.sqlite.  SQLite error code:6922, 'disk I/O error' with userInfo = {
    NSFilePath = "/var/mobile/Containers/Data/Application/172114D0-4346-48F1-ACAE-23A76EC9C339/Documents/File.sqlite";
    NSSQLiteErrorDomain = 6922;
}
CoreData: error: -executeRequest: encountered exception = I/O error for database at /var/mobile/Containers/Data/Application/172114D0-4346-48F1-ACAE-23A76EC9C339/Documents/File.sqlite.  SQLite error code:6922, 'disk I/O error' with userInfo = {
    NSFilePath = "/var/mobile/Containers/Data/Application/172114D0-4346-48F1-ACAE-23A76EC9C339/Documents/File.sqlite";
    NSSQLiteErrorDomain = 6922;
}

Thanks for the additional information! We'll take a look to see if we can figure out what's going on here.

Hi Mark, thanks for bringing this up. Unfortunately, based on the SDK design, there isn't a great way for the SDK to expose file move errors to the end user, without seriously cluttering up the interface.

 

If your solution of manually moving the files to a temp location is feasible for you, then I'm inclined to hold off on adding this feature to the SDK itself, for the moment.

 

Sorry I can't be more helpful! Let us know if you run into any other issues, or have additional feedback for the SDK. Good luck!