iCloud syncing and pythonista.
I never had any issues before. I could edit a script on my phone and jump over to the iPad and grab it almost instantly. I always had to be careful to try and not edit it in two places at once, which happened occasionally but recovered quite easily.
I have decidedly kept my phone on iOS 12 given the hassles others have had with (lucky for some) 13, but accidentally updated my iPad with iPadOS. Ever since it's been a right royal PITA getting scripts between devices.
Like, non existent. Not happening.
I suspect it's an iOS related issue, but wondered what others have done about it?
I can open the pythonista folder in the phone and see files I've created there. Likewise I can see them for the iPad on the iPad. They are just not syncing.
Of I try and create something with a name that exists on the other, then I get the "_1" at the end indicating there's some communication going on.
The only work around I have in place that actually seems to work (I discovered this last night), I have created a sync folder within working copy and pointed it to the pythonista folder. When I sync that and jump back to pythonista, the files exist and I'm in a happy place :)
@cvp I always found it to be ok when everything was on iOS 12, however, now they just don’t synchronize at all... ever.
It would be interesting to see the comparison when two devices are on iOS 12 or iOS 13 (ie on the same iOS). Give the issues Apple has with iOS and cloud , it’s quite possible something changed between the two iOS.
Regardless, using working copy and forcing a sync, always works. It would be very handy if pythonista had the same functionality, yet at least we have that (if you have it installed!)
@madivad I don't use Working Copy. I always program on my iPad and save the code on iCloud to transfer it to my iPhone, always without any problem, except a (usually little) delay.
@cvp are all your devices on iOS 13?
I have a hunch that because the latest beta was compiled under Xcode with iOS 13 in mind, that the issue is with my iOS 12 iPhone. I’ll update it probably soon, and see how we go then.
@madivad no,no, see one of my posts above, my iPhone 5S is in iOS 12
Lol, I had missed that! iPhone 5S. OMG, the code area would be so small! Lol
the code area would be so small!
I never code on my iPhone but sometimes I run scripts written on my iPad and shared via iCloud.
I think I may have solved this issue...
I’ve created dozens of files over the last couple of weeks trying to get to the bottom of this. But syncing between the iPad and iPhone has just stopped working for pythonista (only, everything else has been fine)
It IS a shame pythonista doesn’t have a “pull down” refresh option at the top of the iCloud folder, but what I have found is that if I go to the file explorer on the left and go down to “Open External” and then select files (as opposed to folder, it’s not guaranteed to work there), I can see all the files, even newly created files on either device. The iCloud folder in that location is up to date, it’s just that pythonista’s version of it hasn’t refreshed (at least in my case) for whatever reason...
But now, after having done that, it seems this may be fixed! So far so good!
Wanted to poke this one as well, since I am seeing very similar behavior having recently updated two devices to Pythonista 3.3. In my case, one is on iOS 12, and one on iOS 13, so I can see how they behave differently.
The iOS 12 device seems to work fine with iCloud syncing. When I directly access and modify files in the "Script Library/iCloud" area, changes propagate quickly. If I edit a file in Pythonista on the iOS 12 device, updates appear quickly in an open editor on my macOS laptop, and vice versa: edits on the laptop appear quickly on the iOS 12 device in Pythonista. The same is true when I open the same folder in the "External Files" area and make edits to files there.
On the iOS 13 device, things are not as reliable. When editing files in the "Script Library/iCloud" area, modifications made there from within Pythonista are propagated back to macOS, and to the iOS 12 device. However, when changes are made on macOS, or on the iOS 12 device, they don't always propagate to the iOS 13 device - this seems to happen most often if the file is open in Pythonista 3.3 on the iOS 13 device, but that device is locked/asleep.
Worse, when the iOS 13 device misses an update, and I unlock it so the previous version of the file comes back up in Pythonista, it is that version, without the most recent updates, which is propagated to the other devices...so they lose the more recent changes.
Then I tried the solution @madivad suggested, opening the same folder in the "External Files" area of Pythonista on the iOS 13 device. From there, modifications seem to be more reliable, though it still is the case that if the iOS 13 device is locked/asleep when the changes are made to a file open in Pythonista, it will often (though not always in this case) do the wrong thing when unlocked and propagate the version it has (without the most recent change) to the other devices.
This behavior is very bad, since it means that editing cannot be relied on to maintain the changes safely.
I am having this problem as well. Not all of my files in the Pythonista iCloud folder is showing up in Pythonista. If I go into the Files app and open the Pythonista 3 folder, I can see that it is only the files that are downloaded to the device (not having a cloud icon next to them) that shows up in Pythonista. If I manually download the files in the Files app, they will then show up in Pythonista.
I really hope for a fix to this bug, since Pythonista is useless to me if I can't trust the syncing to work reliably.
This post is deleted!last edited by
Just downloaded today and having syncing issues. Nothing is syncing between iPhone and iPad. Both iOS 15. Like previously mentioned, if I name a folder the same as name of file created on other device, it amends with ‘1’. So it does seem it is aware of the file but that’s as far as it goes. Off to bed now. Let’s see if it’s synced by the morning. Shame this is still happening two year after it’s been highlighted.