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.
-InDesign Team
-
Anonymous commented
Yes I am having same problem
-
Anonymous commented
I am having this problem suddenly on September 2 and everything is up-to-date.
What gives?
-
Madeleine commented
Hi,
I am working on InDesign through 15.1.1 and I am still having this problem in my Google Drive. I will easily get 100+ "AdobeFnt22.lst" appearing daily. Is there anything the Adobe team can do to fix this?
Thanks
-
Christophe Huget commented
Hi, Just to prevent you the issue is still there with InDesign 15.1.1, on iMac 10.15.6 with Google Drive File Stream 41.0.2.0
-
Anonymous commented
ID v. 15.1.1 - problem with "AdobeFnt22.lst" still exists.
-
Anonymous commented
I have the same issue, nobody at support can help me... I'm using Catalina 10.15.6.
-
Anonymous commented
still an issue with 15.1.1 and catalina 10.15.6
-
Rex commented
The latest version 15.1.1 seems to have fixed the issue for me. I'm on an iMac running macOS Mojave 10.14.6.
However, once in a while, when I open a packaged file, sometimes InDesign doesn't load the fonts in the Document Fonts folder. But if I close the file and reopen it, it will fix the problem.
-
Anonymous commented
Now it still appears automatically...how can I delete this 'AdobeFnt22.lst' ?
-
Anonymous commented
This issue was fixed and with the most recent update it's back. I have been stalled for 45 min while the AdobeFnt.lst uploaded endlessly to our cloud server. This is unacceptable!
-
JD S. commented
This is still an issue for my organization. Commenting to follow situation.
-
JD S. commented
This is still an issue for my organization. Commenting to follow situation.
-
Michael leclair commented
This is bad news, really messing up our file organization. I've updated to the latest version of InDesign. We need to have clean deliverables, and these files keep magically reappearing wherever they've been deleted, Please fix.
-
Alan commented
Hi Adobe, we are still having major issues with a lot of spinning wheels in InDesign version 15.1.1. because of the AdobeFnt22.lst files that are created with every document. Basically when we open a document it resyncs/updates the AdobeFnt22.lst file of every document that was previously worked from that Mac. This is causing a lot of network traffic and spinning wheels in InDesign. The problem is fixed if we restart the Mac or rename the "Document fonts" folder so that InDesign no longer uses the fonts so does not create an "AdobeFnt.lst" file. Can you please sort this out, it is killing our production, some of our designers are reverting back to using QuarkXpress.
-
Anonymous commented
ID Version 15.1.1 - problem still exists. FIX IT!!!
-
Angel commented
FIX THIS !!!!!!!!!!!!!!!!!!!!!!!!
-
Yulia Semenova commented
Just updated to 15.0.3 but the problem is still here. Instead of collecting cashe font files in a random folder they are now saved within their designated Fonts folder, BUT they keep sync with Google Drive every time I open an Indesign file and it slows down Indesign a lot! Please fix it! It was fine before the 15.0.2 version.
-
Tracy Vasquez commented
Still having problems! I cannot package anything with fonts because once I reopen the packaged file, it is telling me all my fonts are missing. Instead of replacing the fonts, I close out of the file and delete the packaged fonts folder. When I open the file after doing this, the fonts are fine again. This is obviously not a solution. I am only doing it in order to stay sane at the moment. Please fix Adobe!
-
Anonymous commented
I was hopeful that the newest update to 15.0.3 would fix this issue but it's still a problem. Anyone else still having issues with this?
-
Pia commented
Why is my MacBook Pro able to get the update, but my iMac (Catalina OS) says we are up to date w/ 15.0.2 ?