Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

WARNING ITMS-9000 "Missing 64-bit Support"
Started by fosfor Nov 07 2014 02:16 PM

- - - - -
16 replies to this topic
warning 64-bit

Best Answer steve_capie , 19 November 2014 - 08:10 AM

I have submitted an update to my app with this warning and it got approved.  It was version 1.1 for my app.

[TOPIC CONTROLS]
This topic has been archived. This means that you cannot reply to this topic.
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

fosfor

[GLOBAL: userInfoPane.html]
fosfor
  • Enthusiast

  • 39 posts
  • Enterprise

On a recent attempt to submit an app I built with 2014.2468 using OSX 10.8.5 (XCODE 5.1.1), my client pointed out that the submittal received a warning from Apple:

 

WARNING ITMS-9000 "Missing 64-bit support. Starting February 1, 2015, new iOS apps uploaded to the App Store must include 64-bit support and be built with the iOS 8 SDK, included in Xcode 6 or later. To enable 64-bit in your project, we recommend using the default Xcode build setting of "Standard architectures" to bulid a single binary with both 32-bit and 64-bit code."

 

It seems like this would be no problem for the time being, but is there anything I can do now to build the binary with both 32 and 64 bit code?



[TOPIC: post.html]
#2

roaminggamer

[GLOBAL: userInfoPane.html]
roaminggamer
  • Corona Geek

  • 7,641 posts
  • Corona SDK

Use 2472 or later.  Unless I'm reading the release notes incorrectly, all builds are made with iOS8.1 SDK from 2472 onward: http://developer.coronalabs.com/release/2014/2472/

 

This also assumes the build produces a unified 32/64-bit binary.



[TOPIC: post.html]
#3

fosfor

[GLOBAL: userInfoPane.html]
fosfor
  • Enthusiast

  • 39 posts
  • Enterprise

Thanks roaminggamer. Can anyone else confirm this?



[TOPIC: post.html]
#4

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,622 posts
  • Enterprise

Even our iOS 8.1 will have this warning.  We have not added 64 bit support yet.  We are aware of the 2/1/15 date to have this done by.

 

Rob



[TOPIC: post.html]
#5

fosfor

[GLOBAL: userInfoPane.html]
fosfor
  • Enthusiast

  • 39 posts
  • Enterprise

Thanks Rob!



[TOPIC: post.html]
#6

d.mach

[GLOBAL: userInfoPane.html]
d.mach
  • Contributor

  • 956 posts
  • Corona SDK

So this is only a warning and current builds can be uploaded and are accepted even when this warning appears?

 

- Daniela



[TOPIC: post.html]
#7

loughrank

[GLOBAL: userInfoPane.html]
loughrank
  • Enthusiast

  • 41 posts
  • Corona SDK

I'm having the same issue.  Can someone please confirm d.mach's comment - that builds will not be rejected due to this warning?  



[TOPIC: post.html]
#8

fosfor

[GLOBAL: userInfoPane.html]
fosfor
  • Enthusiast

  • 39 posts
  • Enterprise

I'm almost positive it will not be rejected. Just a warning that clearly states it will be required on Feb 1. I'll know for sure once my app has been submitted.



[TOPIC: post.html]
#9

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,622 posts
  • Enterprise

This is just a warning.  Apple will start rejecting submissions after Feb 1, 2015 that do not support 64 bit slices.  Corona SDK and such only support 32 bit.  This will be a major engineering effort to accomplish.  It will not be in the next public build, so everyone is going to just have to ignore this message until we put it out in a Daily build for Pro/Enterprise subscribers.  We will probably have to put out a new public build because of this which will likely be closer to the deadline than sooner.  

 

Engineering knows about this and will be working on it. 

 

But for now you can ignore this message.

Rob



[TOPIC: post.html]
#10

st.tosi

[GLOBAL: userInfoPane.html]
st.tosi
  • Enthusiast

  • 67 posts
  • Corona SDK

@laughrank

I may confirm: I've submitted an app with the warning and it's now in review



[TOPIC: post.html]
#11

steve_capie

[GLOBAL: userInfoPane.html]
steve_capie
  • Observer

  • 24 posts
  • Corona SDK

  Best Answer

I have submitted an update to my app with this warning and it got approved.  It was version 1.1 for my app.



[TOPIC: post.html]
#12

fosfor

[GLOBAL: userInfoPane.html]
fosfor
  • Enthusiast

  • 39 posts
  • Enterprise

Thanks Steve. 



[TOPIC: post.html]
#13

Mars Interactive

[GLOBAL: userInfoPane.html]
Mars Interactive
  • Contributor

  • 180 posts
  • Corona SDK

so now it's actually 3 days before the date it will reject the apps

is there anything new on the matter ? 



[TOPIC: post.html]
#14

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,622 posts
  • Enterprise

Pro subscribers can download the latest daily build and it should be 64 bit compatible.  There are some plugins that have not been updated, and we've removed them from the servers until the vendors fix them.   Enterprise and CoronaCards users have been 64 bit for a while.  Still it never hurts to have the latest fixes in hand.

 

For Starter and Basic subscribers, I'm trying to get a status on a release for you.

 

Rob



[TOPIC: post.html]
#15

Satheesh

[GLOBAL: userInfoPane.html]
Satheesh
  • Contributor

  • 732 posts
  • Corona SDK

@Rob Which plugins have been removed?? 



[TOPIC: post.html]
#16

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,622 posts
  • Enterprise

And as Walter just reminded me.   This effects **NEW** apps only.  You will still be able to update your existing apps until June 1st.  Please see the blog post here:  http://coronalabs.com/blog/2015/01/21/update-on-corona-ios-64-bit-support-and-plugins/

 

As for which plugins that have been removed, the currently available plugins are listed here:
 

[LINK CORRECTED] http://docs.coronalabs.com/daily/plugin/

 

Rob



[TOPIC: post.html]
#17

MAS1

[GLOBAL: userInfoPane.html]
MAS1
  • Contributor

  • 279 posts
  • Corona SDK

AdBuddiz have confirmed in an email to me that their Plugin is 64-bit supported. 

 

Hopefully the documentation will show that soon...




[topic_controls]
[/topic_controls]