If an error occurs during media upload, there is no direct way for my app to detect that an error has occurred.
Instead, we infer that an error has occurred by checking the info parameter for the delegate method - (void)fpPickerController:(FPPickerController *)picker didFinishPickingMediaWithInfo:(FPMediaInfo *)info. If info.remoteURL, info.filename, or info.mediaType is nil, then we know that the upload was unsuccessful.
However, it would be cleaner if the FilePicker API were to explicitly indicate that an error has occurred. It would also be useful if the API returned the NSError.
A possible solution would be to add a new property to FPMediaInfo for an NSError. Then, the connection error could be set on mediaInfo, i.e.:
mediaInfo.error = error;
failure(error, mediaInfo);
at these two lines:
|
failure(error, mediaInfo); |
|
failure(error, mediaInfo); |
If an error occurs during media upload, there is no direct way for my app to detect that an error has occurred.
Instead, we infer that an error has occurred by checking the
infoparameter for the delegate method- (void)fpPickerController:(FPPickerController *)picker didFinishPickingMediaWithInfo:(FPMediaInfo *)info. Ifinfo.remoteURL,info.filename, orinfo.mediaTypeis nil, then we know that the upload was unsuccessful.However, it would be cleaner if the FilePicker API were to explicitly indicate that an error has occurred. It would also be useful if the API returned the NSError.
A possible solution would be to add a new property to FPMediaInfo for an NSError. Then, the connection error could be set on mediaInfo, i.e.:
at these two lines:
ios-picker/FPPicker/Platforms/iOS/FPLocalController.m
Line 681 in a6357f3
ios-picker/FPPicker/Platforms/iOS/FPLocalController.m
Line 723 in a6357f3