Unable to package a file to a server after upgrading to Mojave.
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
Thanks for reporting the issue to us. We need some more information from you to narrow down the problem.
1. Is this issue reproducible with id 13.1 as well? If you are on id 13.0, please upgrade to Id 13.1.
2. Does the issue happen when the document is present on Mac machine but the packaged folder is saved on a network?
3. Does the issue happen when the document is on a network location and the package folder is made on the network location?
4. Is the issue consistently reproducible?
5. What kind of server are you using? Is it shared folder on a Windows machine? Or a dedicated storage hosted on a Windows server?
Lindsay Kristel commented
I have been having issue packaging since upgrading as well. Whether on server or just on desktop even small files take over 1/2 hour to package. This is unacceptable as one of the main features of InDesign is to package everything up. Is this going to be resolved anytime soon??
Jen Lucas commented
I also have been unable to package files to our Google Drive since upgrading to InDesign 14.0.2, Running Mac OS High Sierra 10.13.6. I get an error message telling me that it cannot copy the necessary fonts. If I package to my desktop, and then copy over it's fine. But it's an irritating extra step, and also forces me to work off my computer instead of Drive.
Debbie Mason commented
Also experiencing this issue today. Mac OS 10.14 (18A391), ID v14.0.1, packaging to a windows server (dedicated storage on a windows server).
2 - Same freeze issue regardless.
3 - Yes, it froze when the indd and package location were both on the server.
Reem Alaa commented
Michelle Bell commented
This has been an issue for 6 months now. Come on, can't we get this resolved! It is beyond irritating (and unproductive) that we can't package files anymore.
Dear Adobe I am unable to package an Indesign document that needs to go to Printing now.
In the Package there are "64 links found and 0 missing". I then get a pop up saying "Indesign could not package the document. cannot copy necessary links".
I wondered if it has to do with links from Apple photo? I most of the times was unable to access the photos from apple photos.
This unfortunately renders Indesign completely useless for me.
My art team had this issue and another issue. While resolving the other issue, we seemed to have resolved this issue. This MAY work for you. Have everyone on your team chance their folder view to "list view mode" and have every one stop using "column view mode" make sure everyone sets it to default on their mac.
I've been having the same problem after upgrading to Mojave. I can't package ANYTHING to the server or my desktop. I even had a reinstall of Mojave and all Adobe programs on my Mac, and it's still not working. I'm using Mojave 10.14 and InDesign CC 2019.
I was able to without issue before Mojave, and have tried a number of things posted in this thread without success. I package things constantly, so this is really affecting my ability to get projects done.
Thiago Ribeiro commented
I found the reason to me!
Here one more chapter of my quest to discover the error:
I can't package from server with Indesign 2019 and Mojave because the "Documents fonts" folder is in there! When you uncheck this in the package option works! I even can open files normally when there is not that folder in my Indesign file root folder. So .. What Adobe can do now ?? It's a font problem! Hope this help everyone, do a test.
SAME ISSUEs on High Sierra. Both saving and packaging
1. For me, this issue has been reproducible on 14.0 and 13.1. Before I updated the OS to Mohave, I had no issue.
2. I already have issues writing to our Windows based network (IT team is working on it), so I was trying to export the file to my local desktop to transfer over to the network later.
3. The document I was pulling on is on the network location, but I was exporting it to my desktop to avoid potentially not being able to write it on the network, which is a reaccuring issue.
4. Yes. I've tried restarting my machine and installing an earlier version of ID.
5. No idea. And yes.
We have the same problem with Mojave and Indesign (both Indesign CC 2019 and CC 2018), it doesn't crash but takes a very long time to package. 45 mins to package a 20pp document, 20 mins to package a 1pp the other day. Everything worked fine before installing Mojave.
Also same problem InDesign crashes when I go to package something. Packaging to same folder.
Using InDesign 14.0.1 and Mohave 10.14.2
Having a similar issue, trying to package a file that is hosted on a server to the desktop, and indesign freezes when packaging links, using mojave and latest indesign.
Same thing happened to me -- Save/Save As/ Undo all greyed out. Interestingly, it only applied to my 21-pg doc with text and images -- not the single pages images. All docs + images are stored in cloud. I am using InDesign 13.1 on Mac El Capitan 10.11.6. I had saved a previous version, so didn't lose all work. I quit ID and reopened and all seemed to be working again.
Any update on when this is going to be fixed? I can't package to my local MacBook or server
I have the same problem when my stupid IT person upgraded to Mojave while I was away, I am unable to package Indesign files where I use 2019 Indesign CC or 2018 v13.1
I have the latest 2019 CC packages on my laptop using High Sierra and I have no issues.
So when is this going to be fixed, as I don't want to have to manually collate my files, we aren't living in the early 2000s...
Guido Meyer commented
We've got the same issue. we stored our graphics on a windows SMB storage and if we select "refresh linked graphics" indesign gets freezed.
I Just wasted an entire morning trying to package one file....InDesign keeps freezing on me...I am beyond disgusted right now.
Same here, please fix this soon!