BUG: Seeing out-of-date PDF in Acrobat
If I update a PDF (Export from InDesign) on the server or the desktop, I use View After Exporting, and despite closing the PDF between updates Acrobat always and only shows the previous PDF - until I quit Acrobat. So I'm quitting and reopening Acrobat 20 or more times a day which is REALLY annoying. Only started happening with version 17.012.20095 on a Mac Pro running CS2015 onwards.
Jeremy
shared this idea
11 comments
-
Viv Berger
commented
Dear Adobe,
Our corporation has multiple users (100s) using Acrobat DC Reader or Acrobat Pro DC to read pdf files.
I am the programmer of a corporate intranet web site and there we have programs that create pdf files from our database. The file names used for the pdf files are fairly generic and will be the same file name when creating a pdf file for the same data. However the users use these pdf files for BEFORE and AFTER pictures when they change the database. Starting with your recent update to Acrobat Reader DC & Acrobat Pro DC of version 2019.021.20056 your products now shows a cached version of the LAST PDF FILE with the SAME NAME and not the actual file contents from the directory specified. There is no pdf file anywhere in our entire database that contains this redundant data and this pdf display cannot be from any actual data in the file system. To verify we have gone to other PCs which have not shown the pdf file before the changes and the correct live pdf is displayed. Furthermore, if we re-boot any affected PC then the correct live pdf is displayed. Users who do not have Acrobat as their default pdf provider do NOT exhibit this problem. This is occurring with both Acrobat Reader and DC Acrobat Pro DC. This is clearly extremely disruptive to users and brings disrepute to your normally excellent products. Can you please let me know how quickly you intend to fix this bug? -
Anonymous
commented
I have this same problem. MacOS Mohave 10.14.6 on MacBook Pro running Adobe Acrobat Pro DC 2019.012.20036.
We are a graphics company and create proofs as pdf so critical that when file is updated it really is - not a previous version!!!
-
Mikey
commented
Here is a Quicktime movie showing what happens with PDFs on the desktop...
When the file is moved from the folder to the desktop, it reverts to a previous version which has been moved to trash!
-
Mikey
commented
I have this problem too...
If I save a PDF from InDesign to the desktop, fine.
I do more corrections in InDesign and overwrite the PDF on the desktop, open that PDF in Acrobat Pro, it displays the old version...I think it is a desktop thing, because if the original PDF is in a folder on the desktop and that is overwritten, it is fine...
It does not happen all of the time, though...
Confused!!!
-
Allan
commented
I also have this problem an I CANNOT fix it. My client is FREAKING OUT!!!
-
Kristian
commented
Same issue here.
File is updated and is OK on one PC, but on the terminal server the old version is being shown.
Running version 2019.010.20098.
Problem was solved by closing all acrobat instances on the server -
chas
commented
acrobat reader dc 19.010.20098 still seems to be caching previously printed pdfs. revised pdf invoices that were previously printed in acrobat reader will continue to print the previous copy not the revised one. a user is printing a revised pdf from gmail in firefox, this spawns acrobat reader, which opens the pdf and presents the print dialog box. choosing print will output the previous pdf if it has been printed previously. choosing cancel and viewing the pdf (to verify that it is indeed the revised one on screen), then choosing print will output the previous pdf. temporary folder has been cleared to no avail. this is happening on a windows 7 workstation. a workaround is to avoid acrobat reader dc and use the browser's inline pdf viewer.
-
Luis
commented
Same problem.
I'm editing form fields in a PDF document usind Adobe Acrobar Reader DC, send it to my iPad, edit it further, send it back to my PC and Adobe Reader DC shows the first version, not the updated one.I sent the first version to a colleague for review and then the second one as well and he can only see the first version, too. When he opens the very same file in Firefox, he sees version 2 of the file but Acrobat Reader still insists to only show version 1.
I am running the following versions:
OS: Windows 10 Pro 1709 (Build 16299.666)
Software: Adobe Reader DC Version 2019.010.20069 -
Ron
commented
This (exactly as described in forums.adobe.com/thread/2372449) occurs with my Windows [pdf] reader. Reader (for Windows) always opens only the previous pdf file version. (refuses to open updated versions of the same filename) This happens only when updating and transfering a file from one device to another via Microsoft "OneDrive". Even when I delete the old file in "Onedrive" and subsequently save the updated file there, the destination device always reverts to opening the previous/outdated file (even though it no longer exists). The instantaneous opening of the old file proves that it is opened from cache because new file-names take a a second longer to open.
When I am transfering an updated file (with same file name) between devices, my successful workaround is to transfer via a USB flash drive instead. It solves the above problem. However this is very cumbersome given the other advantages of using synced-storage. -
Chat
commented
I'm able to reproduce it and there is a thread on the Adobe forums with others who can reproduce it as well:
https://forums.adobe.com/thread/2372449
I'm running latest versions of Adobe apps with no plugins. My project files are all in a Dropbox folder and I mention that because someone else having the problem uses Default Folder X. Both apps perform actions on saved files.
Restarting Acrobat DC solves the issue but it's still annoying and led me here.
2016 Macbook Pro
Mac OS X Mojave 10.14.2
Acrobat DC Build: 19.010.20064
-
AdminAnkit
(Admin, Adobe)
commented
Hi,
We are not able to reproduce the issue in-house. Can you please check and let us know if you are still able to reproduce this issue?
Thanks!
