iOS 12, Xcode 10 & iPhone XS/XR Support Status

Cloud build does not work since it only supports xcode 9. And I think you meant Xcode 10, not 12.

There is something wrong with the safe area calculation in Unity on Xs and Xs+. Header+notch is working fine, footer does not work anymore. Builds that are showing the footer area on the X based on the Unity SafeArea is cutting off the footer on the Xs and Xs+.

 

Thanks

I am on 2018.2.10f1. UnityEngine.iOS.Device.generation still returns iPhoneUnknown. Any idea when will this be updated?

 

He does say "in the following weeks" in the first post.

I have to say though, it does seem weird that additions to the enums take so long. The beta for 12 was around for quite a while, I don't really know why these things are not done before the new iOS versions actually release.

 

FYI, to help on the above issue. It plagued me for a week (iOS11 was fine, iOS 12 was not). Not Unity's problem, but an issue with the trust level of certain certs in your Keychain on OS X. https://stackoverflow.com/a/52506186

Most people won't run into this. I recall re-installing the Apple Worldwide certs a year or so back and for some reason iOS12/Xcode didn't like the trust settings. Very obscure fix.

 

It's disappointing... Apple releases Beta versions of iOS & XCode weeks/months before the launch date. I can't understand why a big company providing tools is not fully ready on time, especially since CloudBuild is now a paid service.

 

Just installed 2018.2.11f1 and UnityEngine.iOS.Device.generation still returns iPhoneUnknown. Guys we have users to support. When will this be available?

 

(I believe you mean 12f1, 11 is already out )

 

Got it, thank you very much!

 

@_Paulius We've had issues getting our deployment targets set correctly when we build, in a few different versions of 2018. We're currently on 2018.2.1f1. If we set the Target minimum iOS Version to 12, the Deployment Target actually set to 11.3 in the generated Xcode project.

I don't see a patch where this has been addressed, although I may have missed it. Any tips/ideas on how to fix this?

 

Hi I have Unity 2018.2.9f1 and xcode 10. The xcode project is made without any issues but when I build it I have this error: Command PhaseScriptExecution failed with a nonzero exit code

 

This error is related to the Appodeal SDK. If anyone else has this please report it.

 

Is there any temporary workaround to the memory issue?

 

@_Paulius We've tested using Unity 2018.2.1f1 and 2018.2.11f1, all of the XCode 10 betas, and the current Xcode release 10.0 (10A255). We've tried it in a new project, as well as an upgraded project, and each time we do a clean build, we have to manually change the Deployment Target to 12.0 in XCode. I've gone ahead and submitted a report, thanks!

 

For future Googlers... our particular issue was being caused by line 355 in the UnityARBuildPostprocessor, part of the ARKit plugin. Mystery solved!

 

Hello,we need DPI detection... when 2017.4.13f1 will be released?
We use the 2017.2 version there will be an update for that?
Thank you

 

@_Paulius is there any temporary workaround to the memory issue? It's a crucial and game breaking issue.

 

You can check this in a different way - check what
SystemInfo.deviceModel returns. If it's "iPhone11,2" ,"iPhone11,4" , "iPhone11,6" or "iPhone11,8" then It's one
of the new iPhone Xs / Xs Max / XR models.

 

_Paulius Please can respond to my question too?
Thank you

 

Hi, any plan to add "Support for iPhone XS, XS Max & XR device (iOS.Device.generation) and DPI detection" to 5.6?

 

Should probably also list this one or is it not related to Xcode 10? At least we got this issue only after updating Xcode on our build machine.
https://forum.unity.com/threads/ios-large-cpu-spike-hang-intermittently-around-autoreadlockt.541038/

 

It looks like it's not in 2018.2.12?
[Edit] My bad, the new XS/XR values were further down the enum, not right after iPhoneX.

 

Hi! Some of the objects become invisible on iOS 12 but not on iOS 10. We tried a lot of things, but not any of them solved the problem.

iOS 10


iOS 12


For water we use Standard Shader with normal map and transparency. Its not visible even when Fade mode is selected, only opaque works. Graphics API - Metal, Color mode - linear.

 

Ok, so we finally found the core of the issue. Deffered Fog in PostProcessingStackV2 makes transparent objects to disappear on iOS 12. Right now we digging depthly and if this theory gonna be right I am gonna submit bug report. Thanks!

 

Hello, has anyone else experienced an issue where creating a C++ thread leads to a crash on iPhone XS?

Steps to reproduce:
- Export a unity project to iPhone
- Create a C++ thread as such and wait for it to finish executing
- Crash on iPhone XS

Crash sample projects:
https://ufile.io/e8m26

void *reproduce_crash()

{

pthread_setname_np("CrashingThread");

}

call

std::thread(reproduce_crash).detach()

from anywhere. After thread executes it crashes upon cleanup.

We have tried reaching unity support but they keep grouping this issue with the memory issues they are having. We don't believe they are at all related. This issue only happens on iPhone XS.

If you are using Realm or any other library that spawns C++ threads in the background then this issue will likely affect you as well. The issue only happens on iPhone XS and only when using C++ constructs to spawn a thread, if you use the C pthread functions directly then the crash does not occur.

Its not an iOS 12 or iPhone XS issue since if you create an empty app on Xcode and do these same steps the crash does not occur. It only happens when unity is somehow linked.

If you open the attached samples you will see that the crash only happens with unity.

0 libsystem_c.dylib 0x000000022d4c7094 __abort + 188
1 libsystem_c.dylib 0x000000022d4c6fd8 __abort + 0
2 libsystem_malloc.dylib 0x000000022d5c3c7c _malloc_put + 0
3 libsystem_malloc.dylib 0x000000022d5c3e48 malloc_report + 68
4 libsystem_malloc.dylib 0x000000022d5b5574 free + 412
5 libsystem_pthread.dylib 0x000000022d5ed40c _pthread_tsd_cleanup + 512
6 libsystem_pthread.dylib 0x000000022d5e6cc8 _pthread_exit + 84
7 libsystem_pthread.dylib 0x000000022d5e5a10 _pthread_body + 144
8 libsystem_pthread.dylib 0x000000022d5e5960 _pthread_start + 52
9 libsystem_pthread.dylib 0x000000022d5eddf4 thread_start + 4

The crash always happens on pthread_tsd_cleanup and only on iPhone XS and iPhone XS Max.

 

@PauliusP I'm using u2018.2.12f,1 same code export works on Droid and with XCode 10 on ipad, ipad2 ios 9.xxx. When run on IPhoneX or IPhone 6+ after unity logo animation, persistant BLACK SCREEN. Iphones are ios v12.

 

Same exact issue as @abelduarte, our apps cannot run on any of the new iPhones.

 

We also have the exact same issue as @abelduarte and @unity_5M9jXnTkXWzlcg , in several projects.

We have created a support ticket here: https://fogbugz.unity3d.com/default.asp?1099198_ok7jh5psl6ubveu8.

Thank you @abelduarte for creating this minimal project for reproducing the issue, we've linked to it in our bug report.

 

In iOS12, there is a new capability called com.apple.AccessWiFi that adds the "Access WiFi Information" entitlement to an app in order to allow the access to some wireless info such as the WiFi SSID.
https://developer.apple.com/documentation/systemconfiguration/1614126-cncopycurrentnetworkinfo

It seems like AccessWifiInformation should be added to PBXCapabilityType: https://docs.unity3d.com/ScriptReference/iOS.Xcode.PBXCapabilityType.html
Is there a workaround for it?

 

Could someone please give an update on the iOS12 memory issue which is apparently not fixed? Is there an ETA? Also for the 2017.4 LTS releases?

 

Currently updated Xcode to Version 10.1 (10B61).I am using Unity 2018.2.1f1. I have given camera usage description and location usage descrption. Ipad pro 2017( ios version - 12.1.3) .Deployment target 12.0. The app builds and loads in Ipad.After unity splash screen the screen is blank with black colour.The debug in xcode is given below

Code (CSharp):

1. 2019-01-03 13:46:49.018336+0530 DragonAR[500:86415] [DYMTLInitPlatform] platform initialization successful
2. 2019-01-03 13:46:49.065880+0530 DragonAR[500:86355] Built from '2018.2/release' branch, Version '2018.2.1f1 (1a9968d9f99c)', Build type 'Release', Scripting Backend 'il2cpp'
3. 2019-01-03 13:46:49.068875+0530 DragonAR[500:86355] -> registered mono modules 0x103393950
4. -> applicationDidFinishLaunching()
5. 2019-01-03 13:46:49.432944+0530 DragonAR[500:86355] Metal GPU Frame Capture Enabled
6. 2019-01-03 13:46:49.434819+0530 DragonAR[500:86355] Metal API Validation Disabled
7. 2019-01-03 13:46:49.521548+0530 DragonAR[500:86355] [Warning] Trying to set delaysTouchesBegan to NO on a system gate gesture recognizer - this is unsupported and will have undesired side effects
8. -> applicationDidBecomeActive()
9. GfxDevice: creating device client; threaded=1
10. Initializing Metal device caps: Apple A10X GPU
11. Initialize engine version: 2018.2.1f1 (1a9968d9f99c)
12. UnloadTime: 0.779750 ms
13. 2019-01-03 13:46:52.928276+0530 DragonAR[500:86355] [MC] System group container for systemgroup.com.apple.configurationprofiles path is /private/var/containers/Shared/SystemGroup/systemgroup.com.apple.configurationprofiles
14. 2019-01-03 13:46:52.928468+0530 DragonAR[500:86355] [MC] Reading from public effective user settings.
15. 2019-01-03 13:47:39.955456+0530 DragonAR[500:86355] <_UISystemGestureGateGestureRecognizer: 0x2812a13b0>: Touch: Failed to receive system gesture state notification before next touch
16. 2019-01-03 13:47:39.955547+0530 DragonAR[500:86355] <_UISystemGestureGateGestureRecognizer: 0x2812a12c0>: Gesture: Failed to receive system gesture state notification before next touch

 

And what about this thread: https://forum.unity.com/threads/ios-12-large-memory-usage.558550/ ?
Unity2018 + iOS12 = Crash.

There are a lot of particular cases in this thread and no clarity what is going on. Please, change the status of iOS12 support. There are HUGE ISSUES with textures and memory usage.

 

@PauliusP why is there complete silence on this issue? https://forum.unity.com/threads/ios-12-large-memory-usage.558550/

Is unity now dead?

 

I faced such type issues and help of online ios app development team I resolved.

 

Any solution to iOS 12 ? iphone 5s or iphone 6 keeps crashes when hit around 600 mb ram usage..

 

We may be forced onto Xcode 11 soon.
Any word on Unity compatibility with this?

Submitting my app recently gave this warning:
WARNING ITMS-90725: "SDK Version Issue. This app was built with the iOS 12.2 SDK. Starting April 2020, all iOS apps submitted to the App Store must be built with the iOS 13 SDK or later, included in Xcode 11 or later."

 

I've been using 11 for a while now without issue, not to say others won't encounter issues, but for me at least all good.