Hi,
I upgraded my iPad pro to the new iOS 9.3.3 and now when I open my Scrivener it crashes. Is anyone else having this problem? How do I fix this?
Thank you in advance!
Have you tried deleting the app and re-installing it?
Hi!
I don’t know if this will be helpful, but as a test, I downloaded Scrivener iOS to my original iPad Mini, which I had already upgraded to ios 9.3.3. Scrivener opened, but crashed when I tried to sync to Dropbox. I then exited the app, and closed all other apps, and tried again. Scrivener crashed again. Then, I remembered that on my iPad Pro, I’d updated Dropbox itself in the last couple of days, so I updated it on the mini. When I opened Scrivener again [making sure it was the only app open] it synced very nicely with my Dropbox ‘Scrivener Projects’ folder and all seems to be well, at a quick glance.
I’m hoping that Scrivener will be okay on my iPad Pro too, with updated Dropbox, but I think I might hang fly, to wait and see how others get on with their iPad Pros and iOS 9.3.3
I run Scrivener on my 12" iPad Pro. Installed it as soon as it became available, pointed the sync to my previously created ‘Active projects’ folder, and eveything worked like a charm. Not a single hickup in spite of my intentionally trying to trick it by editing on both the iPad and Mac simultaneously.
Thanks, lunk! I do have Scrivener on my iPad Pro, but I’ve not yet updated the iOS to to 9.3.3. Are you using 9.3.3?
I’m loving Scrivener for iOS, and have not had a single problem. I should probably just bite the bullet and upgrade the iOS on the Pro. Judging by what happened with the iPad mini, and with my iPad Air 2, which I just checked also, it’s a non updated Dropbox that was causing the problem, not Scrivener.
Thank you so much for your replies. I deleted it, re-downloaded it and that did the trick. It synced perfectly with my dropbox! So excited to have it on my iPad so I can work on it when my ideas come to me.
So glad you got it working. Now I can update my iOS with confidence and know that there’s a fix if Scriv does crash. 
I’m finding that having Scrivener on my iPad is really increasing my productivity!
Edited to add: Just updated my iPad Pro to 9.3.3 and opened Scrivener. All fine. No crashes. Hurray!
I usually update iOS as soon as it is available (without having to be a beta tester 
).
Glad it works for you all!
Regarding the comments/suggestions about upgrading the DropBox app on an iOS device… someone from L&L correct me if I’m wrong, but the presence or absence or version of the DropBox app on the device is irrelevant. That is for two reasons.
- iOS sandboxes (isolates) apps and their associated data so that that apps cannot access other apps (launch, yes, access, no). The iOS DropBox app is a sandboxed app, not a iOS level driver or service accessible to other apps at the operating system as is common on Mac OS X and Windows.
- All Scrivener for iOS interaction with DropBox cloud services is accomplished via DropBox API code within Scrivener for iOS itself, rather than via the DropBox for iOS app (since such is not permitted by iOS as discussed above).
This is substantiated by various L&L postings and documents, and by the following portion of a post by L&L’s AmberV.
“The macOS and Windows versions of Scrivener have not a single bit of Dropbox code in them. There is nothing specific to it. The limitation is on the iOS side, where there is no such thing as a global file system that all apps can access and work with together. You can’t have something like Dropbox running in the background on your phone, keeping it constantly up to date, like your computer does. Every single developer has to write their own interface and they all work in isolation from one another—and for stuff like Scrivener which goes beyond simple use cases, we’ve even had to recreate whole batches of what Dropbox even does at a core level.”
viewtopic.php?f=31&t=35242
Despite being experienced in PC/network deployment and support, I’m still working on wrapping my mind around this difference. I had naively/lazily assumed that the DropBox app needed to be present on my iPhone and iPad in order to be able to use Scrivener for iOS on them. Experimentation (removing theDropBox app and then using Scrivener and having it sync) proves that to not be the case.
Just to subtantiate, you’re entirely right about this.
I looked into the technical details Keith had to work with, which tally, but first I’d removed the Dropbox app from my iPad.
Result: Scrivener synced, perhaps even slightly better in noting when there were changes to sync from the laptop world, and automatically doing the sync. Actually that shouldn’t happen, because of the separation, but as often in the real world, it may, as Dropbox trying to communicate with two apps on the same iPad may end up favoring one first.
Anyway, I’d leave Dropbox on the iPad for your usual reasons if you already have it, as I did. I am experimenting with ‘hiding’ the Apps/Scrivener folder on the Windows machine, which you can do from the Account portion of the Windows Dropbox app, using the item called Selective Sync to uncheck. Seems so far fine, as it appears to affect only the Dropbox folder UI view of things - Scrivener gets its sync anyway. I feel pretty sure, in testing, anyway. Time will tell, and it’s on your own head to experiment with this. I wouldn’t unless you’re technically able and calm, and ready for risks. Also, I am not sure yet if I see any visible advantage. Felt to allow it was there, and put in the caution, as no doubt someone will run into it.
Kind regards,
Clive
Just a detail – the “Dropbox” trying to communicate with an iPad would in this case be the Dropbox server (as opposed to the company, app, logtype, or anything else named Dropbox), and the server actually doesn’t know if I have a Dropbox app installed or not. The server responds to valid requests, whether these come from an iOS Dropbox app, an OS X Droppbox app, or some completely different app using the correct commands to communicate with the Dropbox server. iOS Scrivener is far from the only third-party app capable of reading the filesystem on the Dropbox server.
@lunk, yes, of course – the traffic and multithread, multitasking problem is with the laptop etc. end.
Windows, never too clever about these things, even with a robust processor.
Anyway, the gain I thought to be seeing was in functionality due to lowered same-event traffic, not resource management.
I seem to see more dependable and accurate uptake of changes on either end of sync than when both are running, rather than needing to manually push the sync button.
Not absolutely certain of it, and not time at present to better test, but it seemed to be there.
Edited: there was a crucial ‘than’ missing…