Apple alerts developers that existing app updates will need to be 64-bit by June 1, 2015
Apple on Wednesday alerted members of its development community that existing applications on the App Store will need to include 64-bit support for any updates submitted after June 1 of next year.
The clarification from Apple comes after developers expressed confusion regarding the company's 64-bit app update policies. With Wednesday's announcement, developers now have more than six months to prepare for the switch.
All newly submitted apps will require 64-bit support beginning on Feb. 1, 2015. They must also be built with the iOS 8 software development kit as of that deadline.
But developers will have longer to prepare their existing applications, as app updates will be allowed to remain 32-bit-only through the end of May.
Apple has advised developers that they can enable 64-bit in their project by using the default Xcode build setting of "Standard architectures." This will build a single binary with both 32- and 64-bit code.
Apple began alerting developers to the 64-bit requirement for new applications in October, which caused confusion about existing app updates. Apple was first to bring 64-bit portable computing to the mainstream with the launch of the iPhone 5s in 2013.
The clarification from Apple comes after developers expressed confusion regarding the company's 64-bit app update policies. With Wednesday's announcement, developers now have more than six months to prepare for the switch.
All newly submitted apps will require 64-bit support beginning on Feb. 1, 2015. They must also be built with the iOS 8 software development kit as of that deadline.
But developers will have longer to prepare their existing applications, as app updates will be allowed to remain 32-bit-only through the end of May.
Apple has advised developers that they can enable 64-bit in their project by using the default Xcode build setting of "Standard architectures." This will build a single binary with both 32- and 64-bit code.
Apple began alerting developers to the 64-bit requirement for new applications in October, which caused confusion about existing app updates. Apple was first to bring 64-bit portable computing to the mainstream with the launch of the iPhone 5s in 2013.
Comments
This is the only kind of forced progress of which I’m in favor.
This is one thing I like about Apple's moving to a more modern platform. Either update your apps, or get left behind. Period. No whining, no b!tching, no having hissy-fits. Get your app updated or it's gone.
This is another reason why Android is such a mess.
Out of curiosity, what was the confusion?
Developers weren't sure if all apps needed to support 64 bits in February or not. This clears it up.
Anyone knows what happens to iphone 4s,5 which has 32-bit architecture with new App updates ? Because the same library supports 32/64 bit, would new app can run on older 32-bit iphones ?
Anyone knows what happens to iphone 4s,5 which has 32-bit architecture with new App updates ? Because the same library supports 32/64 bit, would new app can run on older 32-bit iphones ?
It's up to the individual developer. When they're compiling they can choose to make only a 64-bit binary, or a 32 and 64-bit ("fat") binary.
It's only a requirement if you update your app after the date. I assume there will be extra update submissions without 64-bit support right before the cut off date, and then a lot of lazy developers just sitting on their 32-bit apps without updating.
Those apps will be fine.
Since when is five and a half months "more than six months"??? This must be the sort of arithmetic they teach in government schools.
So now you too have ihavetomentionAndroiditis.
The count was likely done on the fingers.
January....one
February..two
March......three
April.........four
May..........five
June........six
Plus what left in December, and we get 6.5 months.
That the problem with finger counting. Are we using the front edge of the finger, or the back edge?
This is one thing I like about Apple's moving to a more modern platform. Either update your apps, or get left behind. Period. No whining, no b!tching, no having hissy-fits. Get your app updated or it's gone.
This is another reason why Android is such a mess.
It's simple enough to update your App. Maybe this will clear out some of the old crap that's just not supported anymore. This is also not the normal PC market where people can hold onto their computers for 5-6 or more years before a upgrade. Generally people go 2 years and replace. I held out for 4+ years with my iPhone 4. We're now on the second generation 64-bit CPU and the 3rd generation is right around the corner. That is if you don't count the A8 for the iPad which is 3 core. You can kind of count that as a 3rd generation if you wanted. Myself, I'll hold out and call the A9 the 3rd generation. Should be around the same time a Android phone finally comes out in 64-bit, maybe. Android and the Apps will be lagging, but what's new.
32-bit is rapidly becoming the new 16-bit.
32-bit is rapidly becoming the new 16-bit.
64bit is the new black.
The count was likely done on the fingers.
January....one
February..two
March......three
April.........four
May..........five
June........six
Plus what left in December, and we get 6.5 months.
That the problem with finger counting. Are we using the front edge of the finger, or the back edge?
Actually, mcarling is right.
You can't count June as the sixth month as the app updates need to be 64-bit by June 1st, not June 30th. That means the last 32-bit update could be submitted May 31st (assuming Apple accepts the upload).
With more than half of December gone, it really is 5.5 months: January (1), February (2), March (3), April (4), May (5), plus whatever's left of December.
Apple began alerting developers to the 64-bit requirement for new applications in October
Doesn't the article state they were alerted in October? Making it over 6 months.
Google has also advised Android developers that their apps will need to include 64 bit support by 20,015.
Unless their app uses the NDK, Android developers don't need to do anything special to make their apps support 64-bit CPUs. With ART, apps are distributed as portable bytecode and are compiled to native code at install time. The final compilation to assembler takes place on the end users' devices rather on the developer's computer.