- Messages
- 23,525
- Name
- Toni
- Edit My Images
- No
Just seen on The Register an article suggesting problems with Adobe apps, and not just older 32bit versions
Actually I’ve always found Reminders (etc) synced perfectly desktop/iPad(s)/iPhone(s) and it was more than just not syncing — they were completely deleted from the older version and only appeared in the new. Reminders in iOS 13 is essentially a new app.I didn't do the upgrade procedure for reminders etc I don't think. Them not syncing with the desktop is common. They're always cocking that up.
Yes, I run FileMaker 15 and no intention to upgrade so I run it in a virtual machine in Parallels (could use free VirtualBox) and also on dual boot and an old Windows machine for ‘backup/security’. I’ll probably do that with Aperture too, just in case.Cult of Mac has got a list of 235 apps that won't work
Cult of Mac
(full list in the link)
I run an app based on Filemaker that holds a ton of pottery glazes that has failed before on upgrade so I maintain a very old computer as a legacy brick to run that one piece of software.
I'm having a mare, my HD is Mac Journaled format. So can't install Catalina.
So I converted it it to APFS, and then it wouldn't boot. So I've had to restore from a time machine backup which is...Mac OS Journaled.
Yes, I run FileMaker 15 and no intention to upgrade so I run it in a virtual machine in Parallels (could use free VirtualBox) and also on dual boot and an old Windows machine for ‘backup/security’. I’ll probably do that with Aperture too, just in case.
my golden rule is.
wait at least 4-6 weeks before upgrading software, allow bugs to be sorted first
I guess the difference is that you are running a FileMaker “solution” rather than FileMaker itself. The FileMaker app licence allows use natively on Mac and Windows, no need for Parallels Though the apps are separate downloads of course.Yes, I can also run a version of the FileMaker based app in Windows under Parallels but have not need able to transfer the database from a Mac to a PC version and vice versa so am stuck
I'm having a mare, my HD is Mac Journaled format. So can't install Catalina.
So I converted it it to APFS, and then it wouldn't boot. So I've had to restore from a time machine backup which is...Mac OS Journaled.
Me too
And although I've seen this 'warning' elsewhere re Adobe, loads of folk have replied to those places sayings all works just fine
I'll give it a few weeks anyway, just in case
Dave
Mate I just updated from a journaled external OS ssd, did you have any SSDs or other HDD/SD drives connected at the time? BTW upon finishing install my SSD is now APFS so it converted automatically.
my golden rule is.
wait at least 4-6 weeks before upgrading software, allow bugs to be sorted first
With an unintentional update, goodness knows how I managed that one but hey oh and all that.
You know it's bad when it's being compared to Vista by the public!
Not at all. My Mac syncs with 2 iPads and 3 iPhones (all IOS13 or iPadOS) and it all works perfectly fine. Aperture was discontinued and unsupported by Apple some years ago, so why should it work?if you use any kind of synchronisation between various Apple devices (macs, iPhones, iPads) you need to hold off installing Catalina or iOS13 on ANY of them. Standalone apps seem to work fine (or not at all, Aperture etc).
if you upgrade on any one device it will break the syncing, at least between Apple apps. So far, in my experience this applies to Mail (which is OK but slow to update) Reminders, Notes, Photos. Calendar appears to be OK. Photos is differently affected, a System library of 15K on the Mac has become 20K on all mobile devices, AFAICS by multiple duplications of images, though to be fair all the iOS devices show the same total.
Not complaining about Aperture, just example, could have said 32bit.Not at all. My Mac syncs with 2 iPads and 3 iPhones (all IOS13 or iPadOS) and it all works perfectly fine. Aperture was discontinued and unsupported by Apple some years ago, so why should it work?
Just because it may not work for a few people (people always, rightly, complain when something doesn't work but seldom praise when it does) does not mean it is totally broken.
Did you install the beta on a device with the same Apple ID as your others? There has never (AFAIK) been a warning not to do that. What happened to Reminders when you did that? Reminders is a completely new app so it was not entirely surprising it did not sync but was surprising that it broke (ie ’wiped clean’) all the other old copies.IOS13 beta worked for me after installing on only one device and “broke” nothing else. But then that’s the point of Beta testing. I trust you reported it to Apple.
So my personal experience is different to your personal experience. Just saying.
Yes, it was on the same Apple ID (I use the same across all devices, for better or worse!). As far as I can remember Reminders on all the iOS devices worked fine with the then-Mojave iMac.Did you install the beta on a device with the same Apple ID as your others? There has never (AFAIK) been a warning not to do that. What happened to Reminders when you did that? Reminders is a completely new app so it was not entirely surprising it did not sync but was surprising that it broke (ie ’wiped clean’) all the other old copies.
I think the reason I am banging on about here is it that I agree about ‘personal experience’ but in the examples I’ve given it seems like more of a systemic problem involving synchronisation via iCloud.
Reported, yes.
Don't panic! For some of us it works just fine (to be truthful I can't see any change).AAAaaaa!!!!
I already installed it