app store update page looks strange

I have a 13" Mid 2012 MacBook Pro that I recently have decided to downgrade due to Photoshop CS5/CS5.5 no longer working on Mojave & newer. According to the forums CS5/CS5.5 was only stable on Sierra but if it helps anyone I have tested it on High Sierra and it works fine. High Sierra is still downloadable in the App Store and it was fairly simple to make a USB installer so I didn't have any issues there. The only funky thing is the app store update page as you guys have mentioned. Aside from it looking corrupt it still functions properly, still can check for updates and still does any updates that are offered. Upon setting up the laptop I received the following updates. iTunes v.12.8.3, Safari v.13.1.2, iTunes Device Support Update (required a restart), Security Update 2020-005 (required a restart), Security Update-004 (required a restart) and lastly Security Update-006 (required a restart). For the Security Updates I had to install them individually before the newer one appeared in the app store. I guess my point is while the page is unsightly it still functions properly so don't let it bother you too much. Besides, I don't believe High Sierra will receive any more updates from Apple so unless apps provide any new updates you won't be on that page too often.

This remains a problem on each of my devices.

It is clearly a Server-side problem as a result of how the App Store is feeding the layout design for this page.

(As noted, other pages in the App Store do display correctly.)

How do we push this up so that Apple will prioritize a fix?? Surely they have the technical expertise to be able to build a basic Responsive web page that will display correctly in their own specialized browser environment (which is what the App Store is.)!

I have this problem as well. It just started showing up.

I now have 10 incompatible updates that usually outnumber the number of updateable application.

I wonder if this is an issue with the quantity of incompatible updates.

I am on Mac Sierra.

If I delete the imcompatible applications on my Mac, I wonder if the text version goes back to the GUI version.

Hello PJ'sPal, please read more answers here; there will be no more updates. Only the 3 latest versions will be updated. Besides, even looking strange, the update page still works (or at least it has).

The days of plenty are over PJ

I have had the same issue with a friend with a Macbook Pro 2017 and now my son has the same issue with his iMac 2013. I also had the same issue with one of my iMacs but it allowed me to upgrade past the 'weird looking page' all the way to Catalina. All have had the strange looking 'app store' page. What may be a concern is that Apple can't do an upgrade to fix the problem as the existing 'app store' won't allow us to move forward. It maybe the case to 'backup, wipe and start again??

It's worse than I thought with Macbook Pro 2017 having issues. It turns out this is a rather "new" issue: with my 2009 Macbook it started some months ago, now it appears to be quickly spreading to rather recent machines. That's a shame if not a crine. So wipe and get rid of Apple time .... As sad as it is it's a fascinating story - will Apple at least publish some facts: I read only the last 3 versions will be supported - with a new version every year or so that would mean future support will last maybe 4 years? Crazy.,.

the weird looking update page still works tho.

Awesome! As of 07/01/2021, my macOS High Sierra App Store Updates page looks good again. Woohoo! Thank you, Apple. We were all correct in stating to them via numerous phone calls and tickets that it was indeed a faulty CSS link.

Glad it's finally fixed after three months, but that in itself, it not acceptable Apple.

The runaround from support was not acceptable, using scripted replies to try remedies on the user's mac when it was clear to anyone with any technical expertise, that this was server side and clearly related to a CSS issue. (as many of us stated).

A large number of mac users will have spent time (and money) trying to resolve this, when it was the fault of Apple all along.

Add to the fact I had to take this up matter up formally with the UK's National Cyber Security Centre, UK Trading Standards and the UK's Competition and markets authority to put high profile pressure on Apple to fix this.

NB. In a word, this wasn't resolved 'easily'.

And what really p sses me off with all this Apple, was Steve Jobs was obsessed with typography, Enough Said.

Tim Cook, you really should be embarassed by this. Apple's management has clearly taken their eye of the ball to let this happen for so long.

But as said, glad it has been fixed, and rightly so.

It was too important to let this slip below the radar, to accept this garbled update page. It would have given companies like Apple 'carte blanche' (unrestricted power) to switch off server side support on devices after only three years of support to show in now uncertain terms your device is now "unsupported", i.e. buy a new one, "new and shiny".

I have this problem to..

I am on a MacBookPro 17", late 2011, OSX 10.12.6

I have sent feedback/problem report https://www.apple.com/feedback/macos.html

Hope this will get fixed soon.

I just did clean install of High Sierra on my 16" 2013 MacBook Pro. Same issues.

This is FINALLY fixed as of tonight, June 30. I didn't do a thing. The problem was all on Apple's side.

Where exactly on that page should someone give feedback about the Mac App Store?

M1 Mac mini, macOS 11.2.3; Watch, series 5 GPS/cellular, watchOS 7.3.3; iPad Pro 2nd Gen, iPadOS 14.4.2; iPad Air 2, iPadOS 14.4.2; iPhone 12 Pro, iOS 14.4.2; TV 4th Gen, tvOS 14.3  HomePods, audioOS 14.3 and Airport Express w/ Airplay 2

Thanks for reaction! Looks exactly like mine, I am still on El Capitan, first time I encounter a thing like this.

My old med 2009 machine has served me just fine all these years and still hums like a happy bee.

Greets from Holland.

I have the same problem on my mid-2011 iMac running on High Sierra 10.13.6. Does anyone knows if the updates are actually installing themselves correctly? Hard to say with the page set up the way it is...