Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
PSA: Your Older 32-Bit Apps Won't Launch After Installing iOS 11
- Thread starter MacRumors
- Start date
- Sort by reaction score
I can probably count with one hand how many people actually use iTunes to sync with their iDevices, and I'm sure Apple has their own data and telemetry. Besides, people has been whining and moaning for Apple to de-bloat iTunes. They did it now and people got upset?
As for being customer friendly, time will tell. Again, Apple has a much larger target audience than us geeks. Majority of the users won't notice a thing other than their apps need to be updated.
Besides, the app issues should be blamed on lazy devs. I prefer Apple weeding out old apps than making iOS a bloat by supporting older libraries. Devs of abandonware should be avoided. I mean complaining this to Apple is like complaining to wal-mart when a certain bread company is no longer making the flavor you like.
Tell me why I had the need to go through my app history and download Super Monkey Ball and a dozen other 32-bit apps...
I'm sure Apple will have this warning in clear plain English, in BOLD type, right at the very top of the "Do you agree to this upgrade" tickbox, so that all users can see, instantly what they are agreeing to, before they accept the upgrade.
Apple would never hide this information deep within the 40+ pages of the agreement I'm sure.
It will be make clear, and easy for everyone to see, before they agree to the upgrade.
Especially as Apple won't allow them to revert back afterwards.
Apple would never hide this information deep within the 40+ pages of the agreement I'm sure.
It will be make clear, and easy for everyone to see, before they agree to the upgrade.
Especially as Apple won't allow them to revert back afterwards.
I guess my Flappy Bird app has finally come to an end. It's been great.
Like users can also make the choice to never upgrade to a newer iOS device? Because the apps they've paid good money for in the past no longer run on the new gadgets that don't have a downgrade option?
Let's just say it as it is: There are absolutely no technical reasons why Apple cuts 32-Bit backwards compatibility. They just cannot bother their army of developers with maintaining the old code. Instead, they force all third party developers to spend THEIR time and THEIR resources and THEIR money on trying to make something work in a 64-Bit environment that might not even be doable for them for whatever real technical reason (for example, their software might depend on libraries that are not 64-Bit compatible).
What nonsense. There's no reason why a 32-bit application can't run on a 64-bit operating system. How is forgetting about the past moving forward? Surely embracing what came before, the doing more is true progress.
And this is why I'll stay on iOS 10 until the apps I want to work, work.
[doublepost=1505804502][/doublepost]
This is why I only buy physical games and spend zero dollars on apps.
[doublepost=1505804502][/doublepost]
This is why I only buy physical games and spend zero dollars on apps.
Yeah, running a mission critical app on an unsupported OS sounds like a winning idea.
Why? If I wrote a perfect app when the system I was working on was 32-bit why should I come back latter and have to change it. I done my job, provided a program that delivered everything I promised it would. Yet after years of working fine Apple wants me to re-write it?
You don’t have to re-write it in the same way an author doesn’t have to rewrite a book for it to be published in hardback.
Every time Apple releases a new version. The user has almost no choice. Apple wants users to follow their interests.
But an author doesn't have to do anything for it to be published in any format.
But once it's written, say whatever time you like, it doesn't have to be REWRITTEN for Christs sake
I know, and apps don’t have to be rewritten in 64 bit. Just a couple of tweaks here and there, hence the analogy which was obviously totally lost on you.
I posted a couple pages back... I used/invested in an study app called Mantis Study Bible for my “work”. Invested around $1,000 dollars adding to the library through in app purchases. I updated to iOS 11 bata and now the app is gone. It wouldn’t load in iOS 11 on my iPad Pro 12.9. It no longer appears in the iOS 11 App Store. Although, I haven’t checked my purchased list to see if it appears there. I kind of expected the worst for awhile now. The developer stopped responding some time back even though their app remained in the iOS 10 App Store with all in app purchases still available.
Update... I just found the app listed in my purchases but when I went to download it I got the pop up message saying the developer needs to update the app because it’s not compatible. Wow
If the developer is that lazy and doesn’t care about their app not to update then how is that Apples fault? May the App Store cleanse begin 
if the developer cares they will update otherwise it belongs in the boneyard
if the developer cares they will update otherwise it belongs in the boneyard
You do if you used 3rd party libraries that either haven't been updated, or require an upgrade fee higher than the current worth of the app. You also do if the app would fall foul of new App Store rules, e.g. if the app was not 'retina'.
This is very anti-consumerism. I have some academic apps that cost about 200 and they are not being updated. They needed a better way to transition that 32 bit apps to 64 rather than killing it off. I'm sorry that you are experiencing this.
I'm thinking you have different attitude toward apple now, huh?
What's your future plan with ios products? Are you planning to stick with it still? like future ipad pros?
A thousand dollars? A thousand? On an app?
No wonder the dev didn’t get back to you, he’s too busy laughing all the way to the bank!
Plenty of reasons. You can't run 68000 code on a 64-bit OS. arm64 code is completely different from 32-bit ARM code, just like it's completely different from 68000 and 6502 code. Only the 3 letters of the name are the same.