Hello,
tl;dr: SOLUTION via Adobe Japan 🎉:
About the problem that synchronization became impossible in macOS 10.11 or earlier (Adobe Support Community – Japan)
- You'll probably have to run this post through a translator.
- The text in the screenshots will still be in Japanese.
- I summarize the steps (in English) below.
---
Thank you to everyone in here. I ran into this a few weeks ago and finding this thread was heartening. Well, as much as an unsolvable, work-interrupting, difficult to work around bug can be 🙂
This thread was the only place I was able to find with any information related to this specific issue (I'm on 10.11.6). I basically gave up and planned to:
- Find the individual fonts I needed and install them manually so I could work.
- Upgrade to some newer version of the OS or possibly get a new computer.
Long story short, I posted this question on another forum, and someone* kindly responded with this exact problem and a solution... FROM ADOBE JAPAN!!
Note to self: When researching a problem like this, instruct the search engine to include non-English message boards!
(*This person is an Adobe Plug-in developer. They were familiar with this issue because they have to run their plug-ins in a number of different environments, including *older* ones.
I told them I was going to post this information in *this* forum, and asked if they would like credit. They said "no". But if you read this: Thank you again so much!!)
If you go to the link above, you'll find very thorough instructions (along with some very polite and courteous comments) from Adobe Japan (@KingPenguin94 | Adobe Staff | Sep 15, 2020).
ex:
> We apologize for the inconvenience and inconvenience caused.
> We will be careful not to cause such problems in the future.
I'll summarize the procedure here for English-translated-posterity and cross-referencing. But you should definitely go to the original post and read through that:
---
Cause:
- Creative Cloud.app updated at some point ~September 2020.
- 2 utility apps (that are needed for "Fonts" syncing) were automatically updated to versions that are not compatible with Mac OS 10.11.6.
- This should not have happened. But I guess CC.app got a little overzealous 🙂
Instructions (overview):
- In Creative Cloud.app: Disable "Keep your Creative Cloud desktop up to date"
- Download the linked .DMG which contains the following patch files (older versions of these utility apps that work with 10.11.6):
- ACCFinderBundleLoader.app (4.3.51.3) [Modified: Monday, July 13, 2020 at 2:14 AM]
- Core Sync.app (4.3.51.3) [Modified: Monday, July 13, 2020 at 2:15 AM] - Relevant Paths:
- `/Applications/Utilities/Adobe Sync/CoreSyncExtension/` ⬅ ACCFinderBundleLoader.app
- `/Applications/Utilities/Adobe Sync/Core Sync/` ⬅ Core Sync.app - Quit all Adobe processes via Activity Monitor.app
- Remove the old versions of these apps
- Copy in the new versions
Now you can launch Creative Cloud.app and the Fonts panel should load.
Additional Information:
- The first time I attempted to copy the 2x older versions of ACCFinderBundleLoader.app and Core Sync.app, the Finder indicated that they were STILL not compatible. Icon + white circle with a slash. But ONLY when they were in the exact location that they needed to be in. I *could* double click them, and they would open from their mounted .DMG, the Desktop, etc. I tried a number of things that I won't bore anyone with. Because I eventually just restarted and then the files appeared to be fine (not circle with a slash), launched, and everything worked as expected. So if you run into this, save yourself some time, and restart first, to see if that clears it up.
- I didn't need to do Step 5: Rename the CoreSync folder.
- To reiterate Step 1 above: Probably don't update Creative Cloud.app if you can help it. In fact, I just re-tested, and am seeing a blue bar at the top of the app: "Creative Cloud app updates available" and a "Proceed" button. The "Files" and "Fonts" panels are greyed out with a message telling me to upgrade. Which is different than when I first applied this fix. I'm not going through with this update because I don't want anything to break. But I wouldn't be surprised if it broke "Fonts" again BUT I was able to re-apply the patch files and get back to work. But I can't chance that right now 🙂
---
I hope this helps everyone who's posted in this thread and anyone that stumbles onto it (like me).