InDesign CC 2018/High Sierra - Cannot package files
Since updating to High Sierra I am not able to package files. The error message is simply "Unable to package the document. InDesign cannot access '(file name'.indd).
I am using InDesign CC 13.0.1 on macOS High Sierra 10.13.1
Don't know if this is of any use or not, but also if I try using my bulk packaging script, the error I get is "undefined is not an object (line 186)
Hello All,
The issue has been fixed with Apple’s MacOS High Sierra 10.13.4 Beta (17E139).
You can try out the fix by updating your machine to the beta update from Apple.
Let us know if the issue is fixed for you after aforementioned High Sierra beta update.
Thanks,
Abhinav Kaushik
InDesign Team
-
Caitlin commented
Having the same issue. InDesign CC 13.0.1 on macOS 10.13.2. Please fix!
-
Anonymous commented
any luck with the yet??
-
Michelle Griffin commented
Also just found that when reverting back to InDesign v13.0, packaging functionality is restored. So something in the 13.0.1 update broke it.
-
Michelle Griffin commented
This may be an issue specific to v13.0.1 on High Sierra. One of my coworkers is using 13.0 on High Sierra and is able to package files fine using SMB protocol to connect to the server.
-
Michelle Griffin commented
Jakob Gulbrandt after searching some more I've also found that the common thread is the SMB server connection! This is great feedback, thank you! Glad to have a workaround for now, hopefully Adobe will fix this problem (or maybe it's an Apple problem?) so we don't all have to redo all of our shortcuts! It's one thing for one person to do it, but it's an entirely different thing to have an entire creative department have to make this change!
-
Travis Johnson commented
Same issue. Using OSX 10.13.1 (updated), InDesign 12.0.0.81
-
Jakob Guldbrandt commented
HEUREKA!!!
After scratching my head for several weeks, I've found the solution!
I turns out it was the same thing causing my search in finder to F*** up...
My problem was that the server I was trying to package from was mounted using SMB and not AFP...
After mounting the server using AFP I was able to properly search in finder on the server AND package my documents!!!
SHARE THIS, as I can see several desperate people out there!Remember to redo your shortcuts in finder, as these will be linked to the SMB protocol as well, AND your startup servers/folders etc.
-
Justin Griffin commented
We've been working around this issue by copying the .indd file to the desktop, opening, then packaging.
**For whatever reason, the links referencing the server package fine if the InDesign file is opened from the local machine and not opened over the network.
-
Michelle Griffin commented
Hey Adobe Peeps, any update on this yet? I'd consider this to be a really urgent matter.
For those of you also having this issue across the network, are you copying the links over locally as well in order to package it, or just the document? PITA to copy docs over locally; unreasonable/impractical to copy links over as well.
-
Tomas BakOS commented
UPDATE: And I have to add, that on colleague's computer (same OS, same ID version) it works well...
-
Tomas BakOS commented
Same issue - with files on server (strange is that not in all projects...).
Need fix asap!!! -
Doug commented
I am having this issue, but only when saving on the network that I work on. My work-around has been saving the file on the desktop, packaging it there, then copying the packaged file to the network.
I have my fingers crossed that this will be fixed soon..
-
Anonymous commented
Same exact issue, AND I CAN'T CREATE A PDF EITHER!
-
Aaron commented
Any day now would be fine.
-
Anonymous commented
A FULL WEEK to action this? Really?
-
Anonymous commented
I am also having this problem. It's a huge issue, as I work at a publisher and we very frequently have to package entire book files to send to the printer or typesetter.
-
Stephanie F commented
This was working with the fix from 10/18/17 but it no longer works for me. Not fixed!
-
Kelsey Dunn commented
I am having the same issue and am also running Version 13.0.1.
I hope this gets fixed soon!
-
Anonymous commented
This is NOT fixed.
I'm running 13.0.1 and it simply doesn't work.
-
Anonymous commented
We're having exactly the same problem. This and the permission issue are very annoying disruptions.