Aaron Winters
My feedback
1 result found
-
28 votes
Hello All,
Thank you for your patience all this while.
This issue is now fixed in the latest update (Id 14.0.1) of InDesign CC.
If you are unable to see the update notification yet, open the menu (three dots) from the top-right of Creative Cloud desktop application and click on ‘Check For App Updates’.Once the update button is shown against InDesign CC, click on the button to update your InDesign to Id 14.0.1 for the fix of the issue.
Do let us know in the comments, if you face any problem with the new update.List of fixed issues can be found at: helpx.adobe.com/indesign/kb/fixed-issues.html
Regards,
InDesign TeamAn error occurred while saving the comment Aaron Winters supported this idea ·An error occurred while saving the comment Aaron Winters commented@dale I have that same question … seems like the only thing I havent tried yet.
An error occurred while saving the comment Aaron Winters commentedI also just cleared all prefs and caches as suggested and now InD locks as before, but with no 'recent doc', just a blank workspace frame. Completely locked out of app now.
An error occurred while saving the comment Aaron Winters commentedSimilar issue. First use after upgrade. After launch, 14.0.0.130 aurtomatically opens most recent saved 2018 document as Untitled 1. Saving that as a 2019 document locks app with spinning beachball. Cannot open other docs or do any other actions in the tool.
Have restarted app, then entire system. Interestingly, in Force Quit dialog, Microsoft Teams app and InDesign both show the In icon.
Unlike PS and AI, which save 2018, it appears InD 2018 is overwritten.
Mac Os 10.13.6 iMac 3.4GHz/8 GB RAM
I upgraded to Mojave this morning. InDesign now completes launch and all menus appear to be active. I can open documents, but that is literally all I can do. No selection, can't change tools.
Although I had already restarted twice since the update, I tried again and it appears as though InDesign does in fact work again.
A little scary having to take on an OS upgrade so soon after announced, but seems to have solved this issue for now.