[Zubersoft]

LittleReg1 - when it comes to errors with cloud services, I usually output the error the service returned me, but a lot of the time this is going to just be an exception message that is not going to be meaningful to users in any way and according to the book you felt the need to quote, is "technical jargon". These cloud service libraries can have tens of thousands of lines of code, which is all obfuscated and hidden from me, so I don't have any more information about the error than what is returned (which is sometimes very little). It sounds to me, based on the small amount of information you provided, that the upload failed for some reason. My code is probably triggering a single line of code, which may be something like: service.upload(file). If that fails, what other information do you think I have access to that I could be providing to the user? The upload failed, the service may not have provided any meaningful information, so I output that the upload failed. Implying that my lack of messaging to the user is because of my "attitude toward my customers" is quite an aggressive thing to say considering I always make my customers my number one priority. There are certainly areas where I can try to improve the error reporting and add additional logging options, but everything comes at a cost. If I'm focused on working on improving those things, then I'm not working on implementing the features that users are asking for. I will certainly try to make time for improving the error reporting where possible in the future though.

A simple workaround is to use the "Local File" option, create the backup on the device, and then optionally upload it to the service using the Google Drive app or web browser to see if that works better for you. If you select "Local File", with Apple's file picker, there is a "On my iPad" option on the left side. Selecting that will let you save on the device itself, not on iCloud. 

Mike