AdobeFnt.lst automatically reappears after deleting
InDesign version: 15.0.2
Suddenly (after the latest March 2020 InDesign update?) the AdobeFont.lst file created with InDesign packages automatically shows up with folder structure after deleting a package. This is really aggravating for file management. It's as if my team can't fully delete InDesign packages. This is happening with multiple InDesign files on multiple machines.
As confirmed by multiple users, this issue is fixed in latest version of InDesign.
Thanks for your feedback.
165 commentsComments are closed
Tengo actualizada a la ultima versión, y me sigue apareciendo.
This issue is still ocurring, our files are stored on google drive and upon opening documents the AdobeFnt22.lst file constantly uploads, then deletes, then re uploads in an endless cycle. This causes InDesign to eventually slow to an unusable state as even once closed the AdobeFnt22.lst continues to try and sync for all previosly opened docs, meaning a restart of indesign is the only soloution.
We have used google drive and indesign together for 3 years now and only in the last month or two has this problem occoured.
I can confirm this happens on both mac and PC accross varios states of updates, the consistant being Indesign.
Please fix this as a priority!
Tim J commented
Having quite a few issues with InDesign not recognising fonts that are installed on my computer and within packaged files. I've recently upgraded to Catalina Mac OS and am also up-to-date with InDesign v.15.0.3 but still the same issue.
When I open the packaged InDesign file, it's saying that some of the fonts are not installed and need to be substituted - I can select the correct fonts but it doesn't update. Instead, the characters are displayed in place of the correct font. When in the design file and clicking on the characters, it shows that it's the correct font - clearly not.
The packaged folder sits on a Google Drive file stream (synched to offline) which has never caused issues in the past. I also keep seeing multiple files call "AdobeFnt22.lst" appear in my google drive directory, nowhere near the packaged file location. When deleting all these files they just reappear sometime later. Totally stumped and highly frustrated as I'm not able to work on the packaged files.
I can't get the upgrade! I'm on Catalina OS and creative cloud 2020 tells me I'm up to date w/ 15.0.2... Argh!
I'm having this issue too. Another font issue I've had since updating to version 220.127.116.113, is that I'll package an InDesign file, with the fonts, then when I later open the document it tells me the font is missing, even though they are in the packaged file, and I also have the font installed on my computer. This is now happening to every packaged file I have.
Laura Cunz commented
I am having the exact same issue! Please fix this. It is becoming unmanageable.
Completely annoying. This stops from working effectively. I'm spending my time getting rid of this and it keeps popping up, indeed! I have been working with InDesign for a long time but I just encountered this problem recently. What's happening?
J. Thorne commented
Same exact issue as a previous poster, Tony_Seddon, commented:
"...the latest version of InDesign 2020 (15.0.2) is recreating extra folders after files have been packaged with images and fonts? Basically, I just packaged a layout by saving it to an alternative 'work' folder that sits on my desktop. Once that was complete I moved the packaged folder back to the original job folder alongside other material associated with the project.
The issue occurred as soon as I opened that InDesign file once again. After doing this, a new folder (same name as the packaged material) reappeared in the 'work' desktop folder. It only contains a Document Fonts folder, so no duplicate Links or a copy of the InDesign files itself. Weird behavior though, I've not seen anything like this before and it's only started happening after the very recent upgrade."
Has InDesign responded to this issue and offered a solution?? InDesign 2020 (15.0.2) is creating extra folders after packaging files
Maria Paula Poveda commented
This only happens to me when I package a file with the default "folder" at the end and then after rename it to delete the word "folder". Once I do that, a folder with my file name but WITH "folder" at the end appears in addition to my normal packaged folder. Driving me insane. Does not let me organize my files.
When i package a file and delete the word "folder" before packaging, it never happens.
I am having the exact same issue. I package SEVERAL folders all day, so this has been EXTREMELY stressful and annoying. PLEASE FIX @adobe.
Same as Wendy and Monica. This has been driving me insane for months. I also keep really organized files/folders and now there are probably 100 total "ghost" folders spread across all of my parent project folders. It's a nightmare.
Some dude commented
If this issue was fixed in the next Beta, how hard is it to apply it to a quick official patch? wtf... I'm sure a lot of people work for companies that don't allow admin access to manually install programs.
I have a printing company and work on Indesign all day long. This issue needs to be fixed. So afraid I'm deleting the wrong folder so afraid to empty my trashcan. Thought I was losing my mind. It is happening on my assistant's computer as well. All Macs. Please fix soon.
Please fix this issue! It is time consuming because all my packaged files keep reappearing where they were initially saved. I can delete them multiple times but they reappear with empty folders and just the annoying "AdobeFnt21.lst" file in the document fonts folder. This is making file management very difficult. The issue has been going on for at least 2 months now, this is unacceptable.
Monica Tate commented
I agree with Wendy... Extremely annoying and Dangerous! I'm in and out of INDD files all day long and I'm afraid of accidentally deleting needed folders by accident. Please, please fix. I keep a clean desktop and this creates a big headache.
My issue is still not resolved.
Is there a patch for this yet? It has made working with Indesign 15.0.2 a nightmare!
Still occuring for me, May 7, 2020.
Still occurring for me, May 7, 2020.