Apple enforces 64 bit in february

Now the question ... is unity prepared for it ?
Last information i had was that there is no full 64 bit support planned.

 

I just read that too:

Apple: Beginning February 2015, App Store submissions need to be 64-bit
http://arstechnica.com/apple/2014/1...2015-app-store-submissions-need-to-be-64-bit/

I have to use Unity 4.2 because of the IOS Terrain Tree Bug:
http://forum.unity3d.com/threads/ca...ree-bug-is-fixed-unity-4-3-and-higher.259116/

Will Unity 4.2 be able to build a 64 bit IOS app?

 

Unity 4.2 probably not but the last version of the 4.x Version (4.6 or maybe 4.7) and the last 5.x if its out in time.
Upgrading is sometimes a pain but i have upgraded a project form 3.5 to 4.5 for iOS and it worked out so upgrading to the last 4.x version should be doable.

 

Thanks for the reply fffMalzbier

I have this sinking feeling i'm in trouble because the 4.2 IOS Tree bug/regression hasn't been fixed in over a year, and everytime it's said to be fixed it isn't. Basically terrain tree framerates have been unplayable since version 4.3, and my game is already on the app store with tons of trees, so if i upgrade you suddenly won't be able to play it.

I can't upgrade until they fix the regression and i'm really stressed that I wont be able to use Unity to update my game on the app store after February because of this (my latest update was released today https://itunes.apple.com/us/app/id885657108?mt=8 ). I really hope to get more information about Unity 4.2 being able to build 64 bit apps.

If they do fix the Unity Bug that will be amazing because they have to implement 64bit IOS builds now in at least Unity 5, or they'll lose their whole IOS developer stable.

 

Apple says "Starting February 1, 2015, new iOS apps uploaded to the App Store must include 64-bit support..." (https://developer.apple.com/news/?id=10202014a).

It states 'new', not 'existing', so it sounds like it shouldn't affect current apps.

 

Thanks Greg - it's great that you caught that. It does offer some releif.

I guess what i need to find out now is if updating your 32bit app is OK too.

I have also planned releases for 2015 that are affected by the Unity bug (more terrain games) but at least this gives me some more time to try and find a workaround (or maybe the bug will be fixed in Unity 5, solving everything

it also says "To enable 64-bit in your project, we recommend using the default Xcode build setting of “Standard architectures” to build a single binary with both 32-bit and 64-bit code." - i wonder if we can build a 64bit app now for IOS? I read that Unity already builds 64bit PC apps.

If anyone has any insight about this that would be great.

 

The big question for me is, does unity need just to update the default xCode project or does the Unity mono code does need to be converted to 64 bit. If its just the xCode project i could think of just grabbing the newer xCode base project of the new unity version and replace the old one in the older version of unity.

@protopop is the tree error in 4.6 fixed? if not it could be difficult to say if its coming to 4.x because they say "Status: Fixed in future release".

 

@greg harding , regarding

"It states 'new', not 'existing', so it sounds like it shouldn't affect current apps."

According to http://9to5mac.com/2014/10/20/apple...nd-include-64-bit-support-from-february-2015/

"In addition however, Apple will also require that all apps and updates include 64-bit support from that date too."

 

@fffMalzbier Unfortunately the Unity IOS Terrain Tree bug hasn't been fixed in 4.6 (details are here: http://forum.unity3d.com/threads/ca...ree-bug-is-fixed-unity-4-3-and-higher.259116/)

I was told it's been fixed in Unity 5and will be ported back to 4.5, but in 4.5.4 release notes (http://unity3d.com/unity/whats-new/unity-4.5.4) it says Terrain: Improved tree culling performance but performance is not fixed. I don't know if that was meant to be the official Unity 5 fix they were talking about or if its just an incremental performance fix but either way the regression remains.

Jerome is right - i just read an official apple repost that Update will require 64bit and IOS8

So starting in February basically all app submissions (is there any other kind aside from new apps and updates?) will need to be 64 bit.

I'm stuck on Unity 4.2 so if Unity doesn't offer 64bot builds for earlier versions we will not be able to update our app.

This is a buisness-breaking issue so I hope we can get some kind of official Unity confirmation about the 64bit build ability of 3.x and 4.x Unity versions.

 

theres another issue. Apps and updates will also need to be built using the IOS8 SDK.

I built using Unity 4.2 and Xcode 6.1 and got this:


From what i understand there is a patch for 4.5 http://forum.unity3d.com/threads/wrong-screen-orientation-with-ios8.269175/

It looks like Unity 4.2 doesn't meet Apples February requirements to update our apps using IOS8 SDK. Is there a way to fix this for Unity 4.2 and earlier?

 

We are working on action plan for 64 bit support. We will announce it once we settle on details.

 

Please support 64 bit with 4.5 or 4.6, did not have enough money prepared for upgrade to Unity 5, but the deadline of February is so close.

 

Although I am a pro subscriber I would love to see 64bit in Unity 4 too.
I just don't want to be forced to switch to Unity 5 early.

 

We can not update our games now... Unity is usually pretty good about this stuff... odd this happened

 

Angry Water, its not even just about "you" having money, its about my whole team, i am not spending 10k to update EVERY copy of Unity, this is ridiculous, and this error should NOT have happened. Not being able to upgrade our 10 games right now is stressful. 2 more weeks and Apple will be swamped, my bet is NO GAMES will be approved till after the holiday... which will crush sales...

I see free Unity5 copies going out for us who are about to loose there butts.

 

So sad, I am so worried about this problem, too. The Apple kept my app "In Review" for days even over a week, but it was only a metadata fix issue. I don't know it was all countries' issue or the App which was taken by the review team in Beijing.

Recently the App Review process was so weird, some games even taken over 1 month "In Review", but when they call the developer from Beijing, they can only answer "I don't know" about the detail of metadata issue. That seems "In Review" is just a fake status, actually, they do nothing but change its status for days or month.

I don't know why do they act like that way?

 

Unless Unity knew about the 64bit requirement in advance I think they were taken by surprise.

Until now it was OK to be using older versions of Unity. Now anyone not using the latest version is going to need a 64bit patch.

It's a pretty big deal so it's OK to be freaked out. I am too because i am stuck using Unity 4.2 due to a technical requirement.

Hopefully they will sort it out before February

 

Please make unity 3.5.7 support this. I haven't upgraded yet

 

Could you provide an update on this? Would it make sense for Unity give an update on the topic even as a blog post or something? This is a pretty serious issue and the current silence isn't very comforting. If I understand correctly, in about 2.5 months nobody will be able to submit any Unity based applications on iOS.

 

While there is bit silent from us, I want to assure that development is in progress at full pace.
Just there are some details we are not yet 100% sure about and once we settle on them we will do both forum and blog posts.

 

Thank you, that is good to hear!

 

I just wanted to upload updates for my iOS apps but ran into problems while validating, because of the lacking 64 bit support.

Is there ANY way we can upload updates at the moment or do we have to wait for Unity / Apple to handle that issue?

 

I can't find the thread now but i read that there was a temporary issue where Apple was rejecting non 64bit apps, but that it was a bug that was fixed. Maybe try submitting the app again?

I know that i just submitted and got approved a 32bit update this week and i did get a yellow warning during the submission that my app was 32bit and that starting February 1 2015 all apps need to be 64bit, but they still accepted it for now.

 

That is good news

Just curious, is Unity also dealing with the IOS8 SDK requirement for February? (Apple requires both 64bit and IOS 8 SDK) I know i got squished screen results when exporting from Unity 4.2 to IOS 8.

 

I'm sorry but, I just joined ship with Unity3D 4.6beta... only to realise you guys haven't built arm64 support for iOS devices into it yet? You didn't see 64 bit coming? It's been out for over a year. DOH wrong turn.

 

Unity 5 beta 13 seems to have Arm64 support and all my games made with Unity 4.6 work on all new devices and apple approved...so dont know what all the fuss is

 

It would be nice with an official comment on that. I can't say that I would like to start developing a game NOW if that game can't even be released on the App Store, February 1. Is Unity 4.* already dead? I just versioned up to 4.6 beta to get the new 2D tools... and it's a beta, and it's not even released yet. And it will be dead in ~2 months? Surely someone will have to make move real soon.

 

Who said they cannot be released on Apple store?
Do you have proof? No, then stop making noise

 

See above quote - no noise involved - Feb 1st 64bit support or GTFO ;-)

 

Its only a warning. You can use the uploaded build and set it for release - this caught me off guard as well. Turns out I wasn't reading it properly.

 

Few moments ago we published blog post on this: http://blogs.unity3d.com/2014/11/20/apple-ios-64-bit-support-in-unity/

 

@MrEsquire, arm64 is not yet enabled in U5b13, but we are already making builds with it enabled for internal testing purposes.

 

64-bit iOS support will be available in Unity 4.6.
Earlier versions will not support it.

You will need to upgrade to 4.6 if you wish to submit a new game to the app store after February 1.

 

IL2CPP sounds great and I am looking forward to it, but have one concern:

I remember Unity app sizes being much bigger when they included both armv6 and armv7 compared to an armv6-only build (if I remember correctly, an app of mine jumped to around 28 MB from roughly 16 MB when the OTA limit was 20 MB). Will that issue be repeated when we have both 32-bit and 64-bit?

If there are the same issues, it could push some apps over the 100MB OTA barrier, so it would be nice to know as soon as possible so that development could take that potential into account.

 

Apple are recommending a single binary, as mentioned in the blog, and I don't believe they have ever had the option for multiple binary submissions, so I will go on the assumption that will remain the same unless I hear otherwise. Based on how app sizes have grown with Unity updates, this could add 20 MB.

 

Im sure Unity will have 64bit export before June, but this is just a note since many people have been wondering if App updates will also need to be 64bit in February

Beginning June 1, 2015 app updates will also need to include 64-bit support and be built with the iOS 8 SDK.

 

I just want to add, that everyone developing for iOS on Unity versions older than 4.6 should start upgrading to Unity 4.6 (or Unity 5 if they have access to the beta) as soon as possible. This ensures that you are best prepared for these changes. Also if you using 3rd party native plugins, you should contact plugin vendors for 64 bit support early (Prime31 has already added necessary changes).

 

Does anyone know what Apple defines as a "new" app? Does the app need to actually be for sale in the app store? Submitted for review? Beta uploaded to iTunes Connect? Or just an iTunes Connect record created?

I'm wondering if we should submit for sale an unfinished 32-bit project in Micronesia for a billion dollars buying ourselves time so we can continue working on our existing 32 bit Unity builds until June 1st, or if just having the iTunes Connect and Beta builds uploaded, but not for sale, is fine.

 

All app submissions, new or old, updates or completely fresh, must be 64-bit starting in February. There is no way around it, if you try to upload an app's binary to iTunes Connect after February 1, it will fail unless it includes a 64-bit executable and support for iOS 8.

If you submitted a complete app before then and it never needed updating, that's the only way to get around the 64-bit requirement. Once you update it, though, it needs to be 64-bit.

 

I thought it was 1 June deadline for updates?

 

Dear Unity,

I know you guys are really working hard on these IL2CPP 64 bit issue and Unity 5...
But, even in 4.6.2, we still got the same linking errors in xcode and our project is over-due because of these problem.
For plug-ins, we are using prime31, playmaker, chartboost, GameAnalytics, websocket-sharp, Poolmanager, FingerGestures.

Code (CSharp):

1. Undefined symbols for architecture arm64:
2.  
3.   "Register_UnityEngine_BitStream_Serializeb()", referenced from:
4.  
5.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
6.  
7.   "Register_UnityEngine_BitStream_Serializec()", referenced from:
8.  
9.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
10.  
11.   "Register_UnityEngine_BitStream_INTERNAL_CALL_Serializev()", referenced from:
12.  
13.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
14.  
15.   "Register_UnityEngine_BitStream_Serializef()", referenced from:
16.  
17.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
18.  
19.   "Register_UnityEngine_BitStream_Serializei()", referenced from:
20.  
21.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
22.  
23.   "Register_UnityEngine_GameObject_get_networkView()", referenced from:
24.  
25.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
26.  
27.   "Register_UnityEngine_MasterServer_get_port()", referenced from:
28.  
29.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
30.  
31.   "Register_UnityEngine_MasterServer_get_dedicatedServer()", referenced from:
32.  
33.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
34.  
35.   "Register_UnityEngine_MasterServer_get_updateRate()", referenced from:
36.  
37.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
38.  
39.   "Register_UnityEngine_MasterServer_get_ipAddress()", referenced from:
40.  
41.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
42.  
43.   "Register_UnityEngine_MasterServer_RegisterHost()", referenced from:
44.  
45.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
46.  
47.   "Register_UnityEngine_MasterServer_set_dedicatedServer()", referenced from:
48.  
49.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
50.  
51.   "Register_UnityEngine_MasterServer_PollHostList()", referenced from:
52.  
53.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
54.  
55.   "Register_UnityEngine_Network_HavePublicAddress()", referenced from:
56.  
57.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
58.  
59.   "Register_UnityEngine_Network_get_isMessageQueueRunning()", referenced from:
60.  
61.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
62.  
63.   "Register_UnityEngine_MasterServer_UnregisterHost()", referenced from:
64.  
65.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
66.  
67.   "Register_UnityEngine_Network_get_isServer()", referenced from:
68.  
69.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
70.  
71.   "Register_UnityEngine_MasterServer_set_port()", referenced from:
72.  
73.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
74.  
75.   "Register_UnityEngine_Network_CloseConnection()", referenced from:
76.  
77.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
78.  
79.   "Register_UnityEngine_Network_Internal_GetPlayer()", referenced from:
80.  
81.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
82.  
83.   "Register_UnityEngine_Network_DestroyPlayerObjects()", referenced from:
84.  
85.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
86.  
87.   "Register_UnityEngine_Network_set_sendRate()", referenced from:
88.  
89.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
90.  
91.   "Register_UnityEngine_Network_get_isClient()", referenced from:
92.  
93.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
94.  
95.   "Register_UnityEngine_Network_GetAveragePing()", referenced from:
96.  
97.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
98.  
99.   "Register_UnityEngine_MasterServer_RequestHostList()", referenced from:
100.  
101.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
102.  
103.   "Register_UnityEngine_Network_InitializeSecurity()", referenced from:
104.  
105.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
106.  
107.   "Register_UnityEngine_NetworkPlayer_Internal_GetExternalIP()", referenced from:
108.  
109.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
110.  
111.   "Register_UnityEngine_Network_get_minimumAllocatableViewIDs()", referenced from:
112.  
113.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
114.  
115.   "Register_UnityEngine_Network_SetLevelPrefix()", referenced from:
116.  
117.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
118.  
119.   "Register_UnityEngine_MasterServer_ClearHostList()", referenced from:
120.  
121.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
122.  
123.   "Register_UnityEngine_Network_set_incomingPassword()", referenced from:
124.  
125.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
126.  
127.   "Register_UnityEngine_Network_set_isMessageQueueRunning()", referenced from:
128.  
129.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
130.  
131.   "Register_UnityEngine_Network_set_minimumAllocatableViewIDs()", referenced from:
132.  
133.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
134.  
135.   "Register_UnityEngine_NetworkViewID_INTERNAL_CALL_Internal_GetString()", referenced from:
136.  
137.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
138.  
139.   "RegisterClass_NetworkView()", referenced from:
140.  
141.       RegisterAllClasses() in UnityClassRegistration.o
142.  
143.   "Register_UnityEngine_Network_Internal_GetTime()", referenced from:
144.  
145.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
146.  
147.   "Register_UnityEngine_Network_Internal_ConnectToSingleIP()", referenced from:
148.  
149.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
150.  
151.   "Register_UnityEngine_Network_get_maxConnections()", referenced from:
152.  
153.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
154.  
155.   "Register_UnityEngine_Network_get_peerType()", referenced from:
156.  
157.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
158.  
159.   "Register_UnityEngine_Network_Disconnect()", referenced from:
160.  
161.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
162.  
163.   "Register_UnityEngine_Network_get_sendRate()", referenced from:
164.  
165.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
166.  
167.   "Register_UnityEngine_Network_InitializeServer()", referenced from:
168.  
169.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
170.  
171.   "Register_UnityEngine_NetworkViewID_get_unassigned()", referenced from:
172.  
173.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
174.  
175.   "Register_UnityEngine_NetworkPlayer_Internal_GetPort()", referenced from:
176.  
177.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
178.  
179.   "Register_UnityEngine_NetworkPlayer_Internal_GetExternalPort()", referenced from:
180.  
181.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
182.  
183.   "Register_UnityEngine_MasterServer_set_ipAddress()", referenced from:
184.  
185.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
186.  
187.   "Register_UnityEngine_Network_get_connections()", referenced from:
188.  
189.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
190.  
191.   "Register_UnityEngine_Network_set_logLevel()", referenced from:
192.  
193.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
194.  
195.   "Register_UnityEngine_NetworkViewID_INTERNAL_CALL_Internal_GetOwner()", referenced from:
196.  
197.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
198.  
199.   "Register_UnityEngine_NetworkView_Internal_GetViewID()", referenced from:
200.  
201.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
202.  
203.   "Register_UnityEngine_BitStream_get_isWriting()", referenced from:
204.  
205.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
206.  
207.   "Register_UnityEngine_NetworkPlayer_Internal_GetPlayerIndex()", referenced from:
208.  
209.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
210.  
211.   "Register_UnityEngine_NetworkPlayer_Internal_GetLocalGUID()", referenced from:
212.  
213.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
214.  
215.   "Register_UnityEngine_Network_INTERNAL_CALL_Internal_RemoveRPCs()", referenced from:
216.  
217.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
218.  
219.   "Register_UnityEngine_Network_INTERNAL_CALL_Instantiate()", referenced from:
220.  
221.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
222.  
223.   "Register_UnityEngine_Network_set_maxConnections()", referenced from:
224.  
225.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
226.  
227.   "Register_UnityEngine_NetworkPlayer_Internal_GetLocalIP()", referenced from:
228.  
229.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
230.  
231.   "Register_UnityEngine_NetworkPlayer_Internal_GetLocalPort()", referenced from:
232.  
233.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
234.  
235.   "Register_UnityEngine_NetworkViewID_INTERNAL_CALL_Internal_Compare()", referenced from:
236.  
237.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
238.  
239.   "Register_UnityEngine_NetworkViewID_INTERNAL_CALL_Internal_IsMine()", referenced from:
240.  
241.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
242.  
243.   "Register_UnityEngine_NetworkPlayer_Internal_GetIPAddress()", referenced from:
244.  
245.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
246.  
247.   "Register_UnityEngine_Network_GetLastPing()", referenced from:
248.  
249.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
250.  
251.   "Register_UnityEngine_BitStream_INTERNAL_CALL_Serializeq()", referenced from:
252.  
253.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
254.  
255.   "Register_UnityEngine_NetworkPlayer_Internal_GetGUID()", referenced from:
256.  
257.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
258.  
259.   "Register_UnityEngine_MasterServer_set_updateRate()", referenced from:
260.  
261.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
262.  
263.   "Register_UnityEngine_NetworkView_Internal_RPC()", referenced from:
264.  
265.       RegisterAllStrippedInternalCalls() in UnityICallRegistration.o
266.  
267. ld: symbol(s) not found for architecture arm64
268.  
269. clang: error: linker command failed with exit code 1 (use -v to see invocation)

 

This is missing RakNet support, we are working to bring it with next updates.

 

There's never going to be an update to Unity 3 dot anything. So you'll be forced to upgrade.

 

Yup, and while you're at it please do 2.x and 1.x please!

 

Seem that lots of people believe this (as did I) but this official word from Apple states clearly that the cut-off date for updates is 1-June-2015: https://developer.apple.com/news/?id=12172014b (note this news item is dated Dec-17-2014 vs the previously provided link was a news item from Oct-20-2014. I'm trusting the later news item)

Quote from that link:

As we announced in October, beginning on February 1, 2015 new iOS apps submitted to the App Store must include 64-bit support and be built with the iOS 8 SDK. Beginning June 1, 2015 app updates will also need to follow the same requirements. To enable 64-bit in your project, we recommend using the default Xcode build setting of “Standard architectures” to build a single binary with both 32-bit and 64-bit code.

[emphasis mine]​

So we've got a few more months for our existing apps before we need to provide 64bit. I might wait for IL2CPP to mature a bit before I do a release based on it.

 

Does anyone know at what point of the submission process the deadline affects? We have uploaded an update for an app that does not have 64 bit support. If it does not go into review before the 1st of June is it going to be automatically rejected? Or are we ok because we have submitted it before the deadline?

 

Here is the latest from Apple on this: https://developer.apple.com/news/?id=04082015a

Quote:

As a reminder, beginning June 1, 2015 app updates submitted to the App Store must include 64-bit support and be built with the iOS 8 SDK. To enable 64-bit in your project, we recommend using the default Xcode build setting of “Standard architectures” to build a single binary with both 32-bit and 64-bit code. For more information, read the 64-Bit Transition Guide for Cocoa Touch.​

It does explicitly state "submitted" so I'd say you're in the clear. But being Apple there's never any guarantees.