16 ms·

It appears this is not a bug in the Twitter app but macOS 10.15.1. https://twitter.com/nolanobrien/status/1189623346033381376?s=21 https://twitter.com/nolanobr

• hayksaakian 7y ago
  yikes, the mac OS Catalina seems like a complete trainwreck with more bugs surfacing every week
  • gingericha 7y ago
    Is there a way to step back a release for those who have upgraded to Catalina and subsequently want to go back to Mojave?
    • pubutil 7y ago
      AFAIK there’s no clean downgrade procedure. You have to create a bootable Mojave image, back up, wipe your hard drive, and clean install Mojave
      • MikeBeas 7y ago
        I managed to do it during the beta. Since Catalina installs the OS on a separate partition inside an APFS container, I wiped the OS partition, then booted into one of the recovery modes (there are 3, I think) to reinstall Mojave on the partition containing my data. No data had to be wiped, and most kept working. Music library won’t work with iTunes but I got around that with Apple Music iCloud Library. A few other things won’t work, like Mojave Reminders won’t sync with iOS 13, but otherwise it wasn’t so bad. Think I had to reinstall Homebrew and Node and that was about it. After that I just removed the now-blank partition that formerly housed Catalina and renamed my data partition back to its regular name. Unfortunately I do not recall which recovery mode I booted into. I tried a few, each offering a different OS to install. One would reinstall the current OS, one would reinstall the version that shipped on the Mac, and one would reinstall the current public build, I think. Wish I had a better recollection of which it was, but since Mojave is no longer the latest public build it may be moot. If you have the Mojave installer downloaded you might be able to just install it right on the data partition and wipe the Catalina OS partition afterwards. Whatever you do, have a full backup before you even think about starting just in case, of course.
        • prashnts 7y ago
          Link to the support page for key combos: https://support.apple.com/en-gb/HT204904 https://support.apple.com/en-gb/HT204904
    • oppositelock 7y ago
      Easiest way is to restore from the last time machine backup before the “upgrade”.
    • ken 7y ago
      That won't help you escape Catalyst bugs, except that you won't be able to run any Catalyst apps. But you can just stop running Catalyst apps, now, without reinstalling your OS.
  • ken 7y ago
    This is using Catalyst, right? UIKeyCommand is a UIKit name, not an AppKit one. And Catalyst doesn't exist prior to Catalina. They've added a whole other (temporary?) operating system. It's perhaps not surprising this has a lot of bugs. Classic wasn't perfect, either.
    • dmitriid 7y ago
      It’s perhaps surprising that they pushed Catalyst out with so many bugs and unimplemented features. Just look at Apple’s own apps built with it. On the other hand, it’s not surprising at all. When was the last time Apple cared about quality in MacOS?
      • Wowfunhappy 7y ago
        I don’t understand why Catalyst exists at all when we have SwiftUI coming soon, which seems much better.
        • dmitriid 7y ago
          Catalyst lets you run iOS apps on MacOS, and you don’t need to re-write them in SwiftUI. But I agree with the sentiment.
    • saagarjha 7y ago
      Twitter is a Catalyst app, yes. Catalyst was used in macOS Mojave for select system apps.
  • ulfw 7y ago
    Goes well with their equally horrible hardware. Time to realise the Mac era is over. Sadly. It hasn’t been a focus for the company in over half a decade.