I recently purchased an Ipad Pro 13” (M5) and I wanted to use Dorico for Ipad while I’m trying to get familiar with this new device (never really had a tablet before…).
I’m experiencing some issues with Dorico file managing in my iPad and between my iPad and my MPB.
Starting situation:
Mid-2017 MacBookPro - Monterey - Dorico Pro 6.2
iPad Pro M5 13” - Dorico for iPad lifetime license - Magic Keyboard Case.
So first of all, as I tried to open a project I imported with my AirDrop, it just created some duplicates, but I don’t understand why. This behaviour apparently had stopped.
Secondly: I tried to share a project between the laptop and the iPad. My Idea was to have the single project on my iCloud and I expected that project to be updated in all my devices. Here’s what happens:
I edit my project in Dorico Pro on my MacBook.
Saved it using cmd-S.
Open Dorico for iPad from the dock.
For some reason, it opens directly the last project I’ve worked on, it does not open the hub, like I decided to open Dorico by tapping from the file.
The project doesn’t show any edits.
After some seconds, it loads again (showing my a greyed hub) and this message: “Project File Edited” “The project File has been deleted. Rename the project to keep project edit?” and I can select between “Rename” “Cancel”.
From now on, I obtain this behaviour: If I press “cancel”
It just cancels all of my edits.
iClouds syncs
Opening the project from Dorico I can see I’ve lost the work I’ve done.
If I press “rename”
Error message: “Is a directory Error creating zip file: /private/var/containers/Bundle/Application/Some alpha numeric code I won’t copy/Dorico.app
I press “OK”.
I cannot see any edits. I close Dorico for iPad.
I open again Dorico for iPad from the dock.
All my edits are right there. Everything is fine.
Now I Edit something from my Dorico from Ipad, then close the project
Dorico gives this message when it thinks that the file has been altered by something else while you’re using it. Make sure that the file is closed on your Mac, and not even selected in the Finder.
It maybe that iCloud maybe doing something with the file that Dorico considers a ‘modification’. Perhaps it’s taking longer than expected to transfer the data from the Mac to the Cloud to the iPad?
That looks like the wrong place: that looks like it’s trying to save the file in the application itself. (Don’t worry, revealing the code number is not a security risk.)
Where in iCloud is this file saved? In Dorico’s folder, or somewhere else?
There is a problem with opening projects from a folder inside iCloud Drive other than the default Dorico folder created by Dorico for iPad itself: when you save those projects (e.g. simply by closing the project again), a copy of the project will be created and saved in the application’s own storage, rather than updating the file in iCloud Drive. This will be fixed in the next Dorico for iPad update, which is coming soon. Sorry for the inconvenience caused in the meantime.
@dspreadbury , may it be possible that dorico creates a folder also in the iCloud drive if you tell him to automatically save in it in the preferences?
There is a setting in the preferences to save to iCloud instead of directly on the iPad itself (default setting). It will create a Dorico folder in iCloud Drive. I was using that folder as a workaround. As @dspreadbury mentioned the fix is coming soon in the next update, and I was given a chance to test it, and it works as it should. You could also share the file back out as a Dorico file to the desired folder location in iCloud before closing the project on the iPad in the meantime.
It seems like the update on iPad must have happened. This is not good for me. I moved all my Dorico files to subfolders to get round the problem of Dorico saving (and updating the time stamp) of files when I didn’t want it to. How can I pevent Dorico for iPad from updating the time stamp of a file and prevent it from saving when I don’t want it to? Have I missed something? Thanks very much.
Looks like you must be right on the update. Not sure what I have just done differently to make me think the behaviour had changed again in the last day. Thanks