4 ms·

Speaking of being amused, when I upgraded my devices to iOS 11 I noticed a lot of apps wouldn't work or install until the developer updated their app to iOS 11.

Speaking of being amused, when I upgraded my devices to iOS 11 I noticed a lot of apps wouldn't work or install until the developer updated their app to iOS 11. I've never had this type of problem on an Android device.

apocalyptic0n3 9y ago
This is possibly because iOS 11 completes the transition to 64-bit[1]. If they apps haven't seen updates in a while, they may still be 32-bit only, meaning they cannot run on iOS 11. We have a handful of apps in this position right now, but clients are reluctant to pay to have them updated. [1] https://9to5mac.com/2017/06/06/ios-11-32-bit-mac-app-store-64-bit/ https://9to5mac.com/2017/06/06/ios-11-32-bit-mac-app-store-6...
- Uehreka 9y ago
  I've been hearing a lot about people not wanting to upgrade. My question is, putting aside the overhead of submitting to the App Store, writing release notes, etc. I thought that the only step that would actually be involved would be to recompile the app? Unless you have something like hand rolled modules of Assembly or inline functions, would it really be that difficult?
  - kuon 9y ago
    Fetching the project from archives (most of the time, just a git clone, but you have to find it), re-familiarizing with the project build process (do I need to fetch some assets that are not in git?), Xcode updating the project and breaking everything, having a gazillion of deprecated warning, code signing certificate have to be re-issued, the SDK you had is not available anymore so you have to update the APIs... It can quickly take a day, a week... depending on the App.
    - bigiain 9y ago
      Yeah, 3rd party SDKs are a problem for us. We've got a project waiting to go live, but one vendor won't give us an iOS11 "certified" SDK until 2 weeks after iOS11 ships... (And yeah, their current SDK crashes in iOS11... It's almost like they don't even know you can get access to iOS betas...)
  - apocalyptic0n3 9y ago
    For apps that are still 32-bit only, they have to be several years old. I believe the first version to support 64 bit was iOS 7 and at that point, I think Xcode would compile with universal support by default. Most of our affected apps were built for iOS 6 (or lower) and the clients have not wanted to pay to keep them up to date. As a result, an update at this point requires quite a bit of work because of deprecated and removed APIs preventing us from recompiling. Then you have the issue of third-party libraries that may not support 32 bit, so you have to go find updated version (if they exist. If they don't, you have to completely remove it and find a replacement) You are correct, though, that in the best case, it is just a recompile.
pohl 9y ago
32-bit app support has been removed. I'm guessing this will allow them to remove 32-bit support from future processors. It might already be gone in the A11 chip. High Sierra will be the last version of macOS to support 32-bit apps, so this same transition will happen next year on the desktop.
- favorited 9y ago
  More importantly, it means you don't need to ship 32-bit copies of system frameworks, and those 32-bit versions don't take up RAM just because 1 app needs to load them into the cache.

apocalyptic0n3 9y ago

This is possibly because iOS 11 completes the transition to 64-bit[1]. If they apps haven't seen updates in a while, they may still be 32-bit only, meaning they cannot run on iOS 11. We have a handful of apps in this position right now, but clients are reluctant to pay to have them updated. [1] https://9to5mac.com/2017/06/06/ios-11-32-bit-mac-app-store-64-bit/ https://9to5mac.com/2017/06/06/ios-11-32-bit-mac-app-store-6...

Uehreka 9y ago
I've been hearing a lot about people not wanting to upgrade. My question is, putting aside the overhead of submitting to the App Store, writing release notes, etc. I thought that the only step that would actually be involved would be to recompile the app? Unless you have something like hand rolled modules of Assembly or inline functions, would it really be that difficult?
- kuon 9y ago
  Fetching the project from archives (most of the time, just a git clone, but you have to find it), re-familiarizing with the project build process (do I need to fetch some assets that are not in git?), Xcode updating the project and breaking everything, having a gazillion of deprecated warning, code signing certificate have to be re-issued, the SDK you had is not available anymore so you have to update the APIs... It can quickly take a day, a week... depending on the App.
  - bigiain 9y ago
    Yeah, 3rd party SDKs are a problem for us. We've got a project waiting to go live, but one vendor won't give us an iOS11 "certified" SDK until 2 weeks after iOS11 ships... (And yeah, their current SDK crashes in iOS11... It's almost like they don't even know you can get access to iOS betas...)
- apocalyptic0n3 9y ago
  For apps that are still 32-bit only, they have to be several years old. I believe the first version to support 64 bit was iOS 7 and at that point, I think Xcode would compile with universal support by default. Most of our affected apps were built for iOS 6 (or lower) and the clients have not wanted to pay to keep them up to date. As a result, an update at this point requires quite a bit of work because of deprecated and removed APIs preventing us from recompiling. Then you have the issue of third-party libraries that may not support 32 bit, so you have to go find updated version (if they exist. If they don't, you have to completely remove it and find a replacement) You are correct, though, that in the best case, it is just a recompile.

pohl 9y ago

32-bit app support has been removed. I'm guessing this will allow them to remove 32-bit support from future processors. It might already be gone in the A11 chip. High Sierra will be the last version of macOS to support 32-bit apps, so this same transition will happen next year on the desktop.

favorited 9y ago
More importantly, it means you don't need to ship 32-bit copies of system frameworks, and those 32-bit versions don't take up RAM just because 1 app needs to load them into the cache.