Created Date Overwritten on Save - Adobe Acrobat DC Pro - Mac

[defaultcztz7sy4d0ko]

When I save some PDF files (typically dynamic XML PDF files) using Acrobat Pro DC (2020.013.20074) on Mac OS 11.1, the created date is overwitten with the date/time that the save occurs. This has severe determinental effects with out cloud document management system (which only uploads when it notes a change between the modified date and created date).

I have spent hours on the phone with Adobe support, and eventually, talked to somebody that understood the problem and opened a bug report (Bug ID : ADC-4317807) two months ago.

(1) Does anybody know how to solve this problem?

(2) Does anybody know how to look up this bug report to see if Adobe is working on it?

[Amal.]

Hi there

Hope you are doing well and sorry for the trouble. As described, the created date is overwritten with the date/time that the save occurs. 

I have checked the status on the bug reported with the ID ADC-4317807, our engineering team is working on it to find the fix. We will share the update as soon as we will hear anything from the engineering team.

Thanks for your time and patience

Regards

Amal

[default2wuks57vh9ft]

I have this exact same probelm when using Adobe Acrobat Reader, however, it does not seem to occur when useing Adobe Acrobat.  I would love to have this corrected so that I can use Reader.

Thanks.

[defaultcztz7sy4d0ko]

Amal,

Is this ever getting fixed? I don't see it listed on https://helpx.adobe.com/acrobat/kb/known-issues-acrobat-dc-reader.html. 

Thanks,

Matt

[Amal.]

Hi there

We are sorry for the trouble. The issue is already reported to our engineering team and they are working on it to find the fix. We dont have a fixed time line for it as of now. We will share the update once we get any news from the engineering team.

Regards

Amal

[defaultcztz7sy4d0ko]

Please provide an estimate date of completion of the bug fix. We need to move on to another product unless this is resolved soon.

[defaultcztz7sy4d0ko]

Do you have any plan of ever fixing this bug? This is computer programming 101. Give me the source code and I'll work on it. Sheesh.

[defaultcztz7sy4d0ko]

Over 3 years later, Adobe has still not resolved this issue. I have spoken with inept Adobe customer support folks for hours on multiple different occasions over the years but no real progress has been made.

[Amal.]

Hi @defaultcztz7sy4d0ko

Please update the application to the new version 23.08.20470 installed. Go to Help > Check for updates and reboot the computer once.
 
Also try to repair the installation from the help menu (Win Only) and see if that works.
 
Please try to reset the Acrobat preferences as described here https://adobe.ly/47Sa6Jk and see if that helps.

~Amal

[defaultcztz7sy4d0ko]

I installed on a fresh machine yesterday. It is the latest version with no changes to preferences.

[Amal.]

Hi there,

Would you mind collecting the Adobe CC logs https://helpx.adobe.com/creative-cloud/kb/cc-log-collector.html  , Procmon logs (Win Only) https://www.adobe.com/devnet-docs/acrobatetk/tools/Labs/acromonitor.html and  share them via any cloud storage. Just upload the log file to the cloud and generate the link and share that link with us for further investigation.

Regards
Amal

[defaultcztz7sy4d0ko]

See secured link below. The password is your name.
Links expire 2024-03-06

AdobeLogs_20240205_104424_599-mac-GS.zxp<>
DOWNLOAD<>
VIEW<>

[Amal.]

Hi there

I am unable to access the logs, would you mind sharing them again?  Please upload the logs to any cloud storage of your choice, create a shareable link and share that link with us in private message.

~Amal

[Matthew241588331htp]

Are there any plans to address this bug?  It is still causing trouble with my changes to .pdfs.  

Thanks M

[defaultcztz7sy4d0ko]

They claim the bug has been passed onto the developers who are working on it. But, I doubt that is true. I don't think Adobe cares at all about bugs. There support staff are pretty clueless and appear to only care about clearing support tickets. I've spent no less than 20 hours on the phone with their suppport staff over the past 4 years with this bug. At this point, they just keep repeating that the developers are working on it and they delete my support ticket but they have no idea when they will get it fixed.

[defaultcztz7sy4d0ko]

It is overwhelming clear that Adobe does not care at all about this bug. It has been over 3 years. As I understand it, they simply don't care since it likley only affects a small amount of users (i.e., those that actually use dynamic XML based PDF files and actually care about created and modified dates in metadata being accurate).

What kills me is that this bug seems like a fundamental programming error? Why doesn't Adobe care about fixing a fundamental programming error like this?