Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
It's not just Archive.org. I just had a problem with an airline ticket. Travel ticket downloaded as PDF looks fine. 4 days later, return ticket from same company using the same process shows only the barcode and none of the (textual) information on the face of the ticket. As a backup to "just use an app" ticketing, I like to save PDF versions and the only way to roll with that ticket was to screen grab it as an image file and save the image instead of the PDF. In other words, the "pdf" version of the ticket in Safari looked fine/normal but when exported to PDF file for Preview (using the same steps as the first ticket), I end up with mostly a blank page with only bar codes showing. And yes, instead of just clicking the download PDF icon in Safari, I also tried print to PDF too but same result.

Investigating further by opening the problematic one in Pixelmator, the background is transparent and lots of areas where text can be appears as white rectangles... like white-out tape strips put over the text. I tried inverting the page to see if perhaps white text on white was the issue but white strips are then black and all text still invisible (if there). I then tried putting an alternative solid color background behind the page to replace the transparency but that made no difference: transparency just became solid color, different than the white strips where text should be visible.

Not all things are lost: brand, little icons and bar codes are "normal"- just the text itself is missing/hidden/"redacted". File size is about the same size as the prior ticket, so the data is probably there- just not displaying. Again, ticket for the "to" part of the trip generated just 4 days earlier by the exact same method looks fine.

Do we miss "just works" Apple or what?
 
Last edited:
  • Like
Reactions: IvyKing
You can do that here:


Oddly, the Preview App isn't listed. You could go through the Books app link. Let them know about things on the feedback page like the Books version list not being up to date.
I have just filed a report with Apple. They confirmed that this is a problem with Sequoia 15.2 and they are working on it. I gave them information about the problems described in this forum and this MacRumors forum thread to investigate. They seemed particularly concerned about the last message posted by HobeSoundDarryl:
It's not just Archive.org. I just had a problem with an airline ticket. Travel ticket downloaded as PDF looks fine. 4 days later, return ticket from same company using the same process shows only the barcode and none of the (textual) information on the face of the ticket. As a backup to "just use an app" ticketing, I like to save PDF versions and the only way to roll with that ticket was to screen grab it as an image file and save the image instead of the PDF. In other words, the "pdf" version of the ticket in Safari looked fine/normal but when exported to PDF file for Preview (using the same steps as the first ticket), I end up with mostly a blank page with only bar codes showing. And yes, instead of just clicking the download PDF icon in Safari, I also tried print to PDF too but same result.

Investigating further by opening the problematic one in Pixelmator, the background is transparent and lots of areas where text can be appears as white rectangles... like white-out tape strips put over the text. I tried inverting the page to see if perhaps white text on white was the issue but white strips are then black and all text still invisible (if there). I then tried putting an alternative solid color background behind the page to replace the transparency but that made no difference: transparency just became solid color, different than the white strips where text should be visible.

Not all things are lost: brand, little icons and bar codes are "normal"- just the text itself is missing/hidden/"redacted". File size is about the same size as the prior ticket, so the data is probably there- just not displaying. Again, ticket for the "to" part of the trip generated just 4 days earlier by the exact same method looks fine.

Do we miss "just works" Apple or what?

... about the travel tickets. We did a lot of tests in my MacStudio with 15.2 and in my MacAir with 15.1.1 just for comparison, uploaded some screencaptures and they scheduled a phone call with me next Wednesday 8 so I will post then with fresh news.
 
Not just 15.2. I'm running 14.7.1 on the (Silicon) Mac from which I rendered the tickets. And this is not the first encounter with that same problem. It's existed for a year or two, as I've had to do the same (screen grab as an image) thing multiple times over the last few years. For me, macOS has turned into "workaround"OS: find other ways to accomplish the same objective or close to it (thus, with this bug, screen-grabbing the airline ticket when the PDF "saves" can't save it with text showing). Hopefully, Apple will run down the bug(s) and fix it/them.
 
Not just 15.2. I'm running 14.7.1 on the (Silicon) Mac from which I rendered the tickets. And this is not the first encounter with that same problem. It's existed for a year or two, as I've had to do the same (screen grab as an image) thing multiple times over the last few years. For me, macOS has turned into "workaround"OS: find other ways to accomplish the same objective or close to it (thus, with this bug, screen-grabbing the airline ticket when the PDF "saves" can't save it with text showing). Hopefully, Apple will run down the bug(s) and fix it/them.
How strange. That's certainly not my case. When I checked the date of the PDFs I downloaded, I saw that the problems started right after I upgraded my MacStudio from Sequoia 15.1.1 to Sequoia 15.2.
Anyway, I hope that Apple's technical support team will take into account what is said in this forum, and your information is very relevant. As I explained, they were very concerned about the trip tickets, but they did not see your message directly, because for privacy reasons, I only took screenshots of my own screen and my own messages, but I captured the name of the forum and the corresponding thread so that they could create an account and investigate it themselves. So I imagine they will see your message, although I suppose it would be better if you reported it independently. The more people complain, the more they'll rush to fix it.
 
  • Like
Reactions: Ravi_MR
I like your optimism. There are MANY bugs in macOS with some lingering for years. Many can be worked around such as I did with the ticket text. However, others are only solvable by Apple. Plenty have reported the one that bugs me the most...

full

That one has been like that for FIVE generations of macOS. The objective among us know it is bug(s) in macOS. It is so prevalent, not only can a simple search for those keywords find lots of posts about it on lots of websites- including Apple's own support forums- but even when trying to buy new enclosures- if there are many reviews- a search for the keywords in reviews will tend to find reports of new (and old) enclosures not staying connected to Mac.

IMO: Apple needs a snow leopard year or two focused on bug fixes & refinements vs. rolling out new-new-new features every 12 months. I presume the parade of new features drives more revenue... but "just works" likely makes for happier customers (able to buy new stuff, but sometimes less willing due to the decay of "just works").

Stuff like wonky PDFs in some cases can be worked around (though the underlying bug(s) should still be fixed). Stuff like "unexpected ejections" can only be addressed in most cases by Apple debugging port and/or power management algorithms in macOS since Big Sur. Yes, I'd like BOTH and many other bugs fixed too.
 
Last edited:
What's kind of weird about the Preview bug is that the "works of Poe" PDF renders correctly on my iPad (iOS 18.2) while not rendering correctly under MacOS 15.2.
 
So glad it's not me. Super annoying and I had to end up downloading Adobe Acrobat to be able to read some PDF's.

Glad Apple is aware and hopefully a fix is incoming soon. No issues viewing the same PDFs on my iPad and iPhone.
 
  • Like
Reactions: Ravi_MR
I have just filed a report with Apple. They confirmed that this is a problem with Sequoia 15.2 and they are working on it. I gave them information about the problems described in this forum and this MacRumors forum thread to investigate. They seemed particularly concerned about the last message posted by HobeSoundDarryl:


... about the travel tickets. We did a lot of tests in my MacStudio with 15.2 and in my MacAir with 15.1.1 just for comparison, uploaded some screencaptures and they scheduled a phone call with me next Wednesday 8 so I will post then with fresh news.
Thanks a lot for filing a bug report! I got super busy at work and thought I'd pick this up this weekend. Glad you beat me to it!
 
So glad it's not me. Super annoying and I had to end up downloading Adobe Acrobat to be able to read some PDF's.

Glad Apple is aware and hopefully a fix is incoming soon. No issues viewing the same PDFs on my iPad and iPhone.
Firefox and Chrome don't have the same issue. You may use either one as a PDF reader. Adobe Acrobat is very cluncky.
 
  • Like
Reactions: Ravi_MR
I have just filed a report with Apple. They confirmed that this is a problem with Sequoia 15.2 and they are working on it. I gave them information about the problems described in this forum and this MacRumors forum thread to investigate. They seemed particularly concerned about...
Wow. That's amazingly chatty.

In 15 years of reporting bugs to Apple, the only replies I've had are: "Provide us with more information"; "We've made some changes in this build", "Works as designed", or ... nothing.
 
This is definitely not just confined to Archive.org. All my invoices are showing in this weird black and white/inverted colour format since updating to macOS 15.2 ("Sequoia must be stable by now", I thought...). An exceptional boost to my business productivity, thanks Apple!

Talked to Apple support and they were useless as expected, so it looks like it's a case of waiting and hoping a fix comes soon.

Regretting the "upgrade", but as a platform agnostic user who deliberately avoids most Apple-specific software and services I can work around it with Adobe Acrobat. This just reinforces that standpoint.

(Is this it just working?)
 
It's nothing to do with archive.org. I get PDFs from different organisations I work with routinely and many of them are illegible. These are informational booklets with professional design work in them.

The phantom disk ejections mentioned by another poster also affects me on a brand new M1 iMac. Apple aren't doing thorough QA and it's absolutely unacceptable from a company making those kinds of profits. I've been Apple-only since 2011 but I'm done.
 
The thing I find concerning is that reading PDFs is what I'd call an essential function, yet there's no public acknowledgement of the issue or rush to release a hotfix. Customer support had no awareness of the problem despite me linking to this article, instead just telling me to try safe mode...

Some users may not even realise there's an underlying issue with the PDF rendering and take the documents as they see them, which as it stands can obscure or distort information.

I'm used to the hell hole that is Xcode but, come on, a Raspberry Pi can read PDFs better than this as it stands. Each major OS update is seeming increasingly pointless these days.
 
Last edited:
This is definitely not just confined to Archive.org. All my invoices are showing in this weird black and white/inverted colour format since updating to macOS 15.2 ("Sequoia must be stable by now", I thought...). An exceptional boost to my business productivity, thanks Apple!

Talked to Apple support and they were useless as expected, so it looks like it's a case of waiting and hoping a fix comes soon.

Regretting the "upgrade", but as a platform agnostic user who deliberately avoids most Apple-specific software and services I can work around it with Adobe Acrobat. This just reinforces that standpoint.

(Is this it just working?)
I just finished my third conversation with Apple Support about this.
They wanted me to back up my system and spend the next hour and a half reinstalling the latest version of the OS, the one that gives problems with PDFs, to verify that it wasn't some installation problem.

I worked years ago for Microsoft on the early versions of Office and I know how this works, and that it is done as standard procedure, but I also know that 99.999% of the time it is absolutely useless, and I didn't feel like spending an hour and a half of my Saturday on that task.

The support technician tells me that they have no record of the PDF problem happening to other people. So, as I see that it didn't help to provide them with the address of this forum and let them see for themselves, I took the liberty of taking some screenshots of your latest posts (#BrianBaughn, #itjustworks! and #Séimhe) so that they can check it out for themselves.

They provided me with a link and I passed them on to tech support, and they could see that I'm not the only one with the problem.

They are going to call me on Wednesday to see if it is possible to reinstall just the macOS PDFkit framework from the previous version and not have to reinstall the whole operating system again.

I will let you know. Thanks.
The macOS update has screwed up Preview's ability to properly render PDFs created with the tools that the Internet Archive is using…maybe because of some sort of compression method their tools use. This also affects any apps that use the macOS PDFkit framework.

I was able to create a workable PDF version of the file by viewing it with Firefox and printing to a PDF. However, that file ended up being 31.1MB instead of the original 2MB. Uploading the Firefox-printed PDF to smallpdf.com got the file down to 3.8MB.

File a bug report with Apple.

It's nothing to do with archive.org. I get PDFs from different organisations I work with routinely and many of them are illegible. These are informational booklets with professional design work in them.

The phantom disk ejections mentioned by another poster also affects me on a brand new M1 iMac. Apple aren't doing thorough QA and it's absolutely unacceptable from a company making those kinds of profits. I've been Apple-only since 2011 but I'm done.

The thing I find concerning is that reading PDFs is what I'd call an essential function, yet there's no public acknowledgement of the issue or rush to release a hotfix. Customer support had no awareness of the problem despite me linking to this article, instead just telling me to try safe mode...

Some users may not even realise there's an underlying issue with the PDF rendering and take the documents as they see them, which as it stands can obscure or distort information.

I'm used to the hell hole that is Xcode but, come on, a Raspberry Pi can read PDFs better than this as it stands. Each major OS update is seeming increasingly pointless these days.
 
At the time, I filed a bug report under the Books app as I didn't see a link for the Preview app.

Maybe that's why support doesn't see any other complaints!

It's idiotic that support persons can't download the file to see for themselves while you're on the phone with them.

Reinstalling isn't going to help…
 
  • Like
Reactions: Séimhe
I just finished my third conversation with Apple Support about this.
They wanted me to back up my system and spend the next hour and a half reinstalling the latest version of the OS, the one that gives problems with PDFs, to verify that it wasn't some installation problem.

I worked years ago for Microsoft on the early versions of Office and I know how this works, and that it is done as standard procedure, but I also know that 99.999% of the time it is absolutely useless, and I didn't feel like spending an hour and a half of my Saturday on that task.

The support technician tells me that they have no record of the PDF problem happening to other people. So, as I see that it didn't help to provide them with the address of this forum and let them see for themselves, I took the liberty of taking some screenshots of your latest posts (#BrianBaughn, #itjustworks! and #Séimhe) so that they can check it out for themselves.

They provided me with a link and I passed them on to tech support, and they could see that I'm not the only one with the problem.

They are going to call me on Wednesday to see if it is possible to reinstall just the macOS PDFkit framework from the previous version and not have to reinstall the whole operating system again.

I will let you know. Thanks.
It does bug me about how much effort is needed to tell tech support that this is a wide spread problem. In an ideal world, Apple would be working hard on fixing the problem and letting tech tech support know that a solution is on the way. What really bugs me is that the iOS version of Preview does not have the problem.

Preview is also missing functionality in displaying PDF's, such as embedded comments that pop-up in Adobe's Reader and Foxit. The examples I have are covered under NDA's, so can't send them to Apple's tech support.
 
I just finished my third conversation with Apple Support about this.
They wanted me to back up my system and spend the next hour and a half reinstalling the latest version of the OS, the one that gives problems with PDFs, to verify that it wasn't some installation problem.
Surely they should be able to test an example PDF on their own Macs, running Sequoia, and Sonoma..? :rolleyes:

I don't see how you're going to restore PDFKit onto the OS's SSV....
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.