Yesterday we upgraded to 10.14 Mojave and I am not able to package files from windows server. Indesign freezes every time.
I can make packeges from my MAC or from external hard drives. The network is working correctly. On High Sierrea everything worked properly.
Indesign CC 2018: 13.0
Mac: 10.1438 votes
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.
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 email@example.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.
Problem: Open any ID file and links that should be "OK" are labeled as "modified". I do not get any error window that pops up notifying me this. Without taking any action, I close the ID file and reopen it and links are now labeled as "OK". Open it up a third time and links are "OK". I QUIT out of ID and open that same file and see links as "OK" and now they are labeled as "modified". This process repeats. Attached video to show. All links in these ID files are not modified or changed. This poses a quality control problem. Please advise.
Problem: Open any ID file and links that should be "OK" are labeled as "modified". I do not get any error window that pops up notifying me this. Without taking any action, I close the ID file and reopen it and links are now labeled as "OK". Open it up a third time and links are "OK". I QUIT out of ID and open that same file and see links as "OK" and now they are labeled as "modified". This process repeats. Attached video to show. All links in these ID files are not modified or…10 votes
Thank you for your patience all this while, We have concluded our investigation into the issue and below is our finding.
This issue is due to the use of a specific version of Extensis Universal Type client: version 6.1.6.
The issue is reproducible only with Id 2018 as Extensis UTC 6.1.6 is not compatible with Id 2019.
If you are using Extensis UTC 6.1.6 with InDesign 2018 please use any other version of Extensis UTC which is compatible with Id 2018 to avoid this issue.
Or you can upgrade to Id 2019 and used compatible version of Extensis UTC.
InDesign Version: 13.1
To reproduce issue, create an InDesign document with some styles, map styles to tags and export to PDF with tags (accessible pdf).
Expected result is that in the Reading Order panel (and Content pane), each paragraph is wrapped in an appropriate container.
The actual result is that each line of text within a paragraph is wrapped in a span container.
Although this doesn't seem to directly affect the accessibility of the file, it makes additional remediation difficult because of the many containers found in the PDF file.16 votes
We acknowledge that the issue is slowing you down and we regret the same.
Our investigation suggests that the issue lies in the latest update of Acrobat and there is little that can be done at our end to resolve the issue.
The problem has been communicated to the relevant team.
In the meanwhile we are closing this thread for InDesign.
Hand tool freezes and no other tool can be selected. It won't unfreeze unless I shut down entire computer. This is a recurring issue.32 votes
In order to reproduce the issue we sent information to all the affected users who have either voted or commented on this thread.
Based on the replies we got we could infer that the issue is occurring when a third party software or application is also running in parallel. Some examples of the software used include Global Auto-correct, Google Chrome,
Moreover, when the issue occurs it seems to hamper all CC applications such as Illustrator, InDesign and Photoshop.
A possible fix for the solution includes restarting the application or restarting the system.
In the absence of any consistent reproducible steps, we are currently closing this thread as “not reproducible”. In case you again encounter the issue, please create a new thread mentioning the steps with which we can reproduce the issue and additional softwares, if in case any, that you are using.
- Don't see your idea?