Online ANYWHERE and I get the following error when trying to share from Safari is iOS10 "couldn't save content Please check your internet connection and refresh the page"
This hapens on any network.
iPad V5 32gb with AT@T
It does NOT happen in Chrome. It appears Dropbox is not integrated with Firefox. I can use Chrome for the time being and am happy to help with any troubleshooting in Safari. Thanks for the suggestion.
Chrome is not integrated with Dropbox on the ipad as far as I can tell so the work around will not work. Furthermore, it apepars this ONLY happens with a PDF, not a simple website. So when i try to save a webpage to Dropbox it works fine but when I try to save a PDF it gives the error.
Allow me to complicate it more. If I choose the page with up arrow in the upper right corner, and select save to Dropbox I get the error. if I allow the "more" to pop up on the upper left corner, the save to Dropbox function works.
I’ve been using an iPad Pro with iOS 11 and getting increasingly annoyed with not being able to save the contents of web based pdf file to Dropbox due to ‘couldn’t save contents’ message. In Safari, not Chrome, I found in the share menu (box with up arrow) a button called “Create PDF”. I’m not sure if this is a feature of iOS 11 or something added from one othe numerous pdf apps I’ve tried, but in any event, by using this button to create a pdf I am then able to go back to the share button and save to Dropbox without a problem.
I suspect the cause of the problem could be the opened pdf document is reformatted for the screen and is not recognizable as a pdf when trying to be saved to Dropbox. I’m sure someone else can determine that and correct for a future update.
How is this issue solved? The marked solution is just a workaround using another browser...
I've given up on Dropbox for various reasons and moved on . Google Drive it is..
I just tried to save to Dropbox from my iPad and I received the same error. I discovered this thread when investigating the error, I’m amazed that it seems to have been an issue for about 2 years. So clearly not resolved as the thread would have me believe.
I am still experiencing this issue. The workaround shown above (that is marked Solved) does not work for me.