Shawn
My feedback
3 results found
-
149 votes
As confirmed by multiple users, this issue is fixed in latest version of InDesign.
Thanks for your feedback.
-InDesign Team
Shawn supported this idea · -
38 votes
Hello All,
We have concluded our investigation into the issue and found that the issue is specific to few versions of MacOS 10.14.×.
As a part of our investigation we had reached out to many of you, where many of you have confirmed that the issue gets resolved after upgrading to MacOS 10.14.5.Note:
If you are NOT using MacOS 10.14.5 and still facing this issue, please upgrade your MacOs to 10.14.5 version.
In case you continue to face the same issue after the upgrade, you may reach out to us at sharewithid@adobe.com.For any other problem related to packaging workflows please create a new thread.
We are closing this thread for now.
Thank you for your patience all this while.
-InDesign Team
An error occurred while saving the comment Shawn supported this idea ·An error occurred while saving the comment Shawn commentedMulitple macs with Mojave Mac, we cannot package files - indesign crashes.
1. We have the latest InDesign
2. Folder and packaged file location is local
4. Is the issue consistently reproducible? Yes every time on 2 iMacs
5. Windows server, but local stored files as well
-
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 TeamShawn supported this idea ·
we downloaded InDesign cc2018(13.1) for MacOs Mojave and packaging works for us as well regardless if it was located on local or windows server. i concur that the bug is 2019(14) related an ETA on a patch for this would be much appreciated!