A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
Introducing the new Universal Render Pipeline and High Definition Render Pipeline subforums!
Unity 2019.3 Beta is out now.
Discussion in 'iOS and tvOS' started by johnfrog, Sep 20, 2018.
We tried that too and it made no difference (for us).
No update for us either. We've been working directly with Unity in email and have not heard back from them since Thanksgiving. The bug is still persistent in the new versions of iOS and and Unity released over the holidays. Anything with less than a 2gb mem limit crashes the moment the assetbundle is loaded into memory.
This is for a massive national configuration and sales campaign with a major OEM for their flagship vehicle. This has now caused a 2 month delay in the release of our update and our client is very unhappy with us.
We are now looking for UE4 solutions as Unity seems to be unable and unwilling to assist.
We fixed the memory issue by using xcode 9.4.1 and building for iOS 11. When running the app, other processes release memory as the game needs more. On iOS 12, the game tries to use the same amount of memory, but other processes dont release it, and the game crashes.
This will work until the end of march 2019, when apple requires all apps to be built for iOS 12.
I think the iOS 12 requirement might kick in at the start of March, not the end
Thank you for this! Using Xcode 9.4.1 did indeed fix our issue.
Unfortunately, that isn't a solution. If you guys build with 9.4.1 and release it, you will then be dealing with a lot of angry users in March when the iOS12 requirement kicks in.
On top of it, we only have iOS 12 iPhones on our end - referring to the developers and the clients.
We did try to downgrade iOS 12 to 11 but it is not downgrade-able without a jailbreak as far as I know.
So... Xcode 9.4.1 is no go for us.
Not a permanent solution, but at least a temporary one. Builds in 9.4.1 still work on iOS 12 devices.
So will Apple just pull the plug on any games not using iOS 12?
I've managed to get my game running on all iOS / tvOS devices again, DESPITE this bug, by just crushing texture compression virtually all the way down across the entire game. Ridiculous, but it works as a temporary solution (PS: on the latest versions of everything). https://www.astrogun.com/2019/01/10/vast-update-1-0-7-live-patch-notes/
Shiny new Unity and Xcode! My game ran and looked better A YEAR AGO on OLDER HARDWARE. Awesome.
But at least this worked.
@derkoi If you build your game now in Xcode 9 it will still work in March. Games built without the iOS 12 sdk still work on iOS 12.
But any new games or updates from March on will need to use Xcode 10, and you will need MacOS 10.13 high Sierra at least to use Xcode 10. So all iOS developers will need to switch to MacOS high Sierra or Mojave in about 7 weeks If you want to keep releasing updates or new games after that date.
Cheers. I'm on High Sierra and released updates with Xcode 10.1 and suffer from this memory issue. Going to go back to Xcode 9.4.1 and see if it solves the issue until I can figure out the next step.
2018.3.1f1 out. No fix for this. Confirmed in test build.
Well I rolled back xcode and rebuilt my project and it's working fine on iPhone 5s and iPhone 6 with 220mb memory usage instead of crashing out at 650mb with xcode 10.1
Yay! Well... enjoy it till March! ::gulp::
I don't plan on updating the game again until this issue is fixed so as long as it's working until a fix is found I'm happy. At the moment I have many players unable to play the game.
Does this xCode 9 thing really work? Going to check it out myself and report back.
Yep. Did for me. You get a few compliance warnings when uploading to Apple but otherwise it's working how it should for me.
So I just fired up my old iPad mini 2 with iOS 11 installed. It ran my existing game that's released fine, however once I upgraded to iOS 12.1.1 my game crashed whilst loading. I updated the game to my new xcode 9 built test version and it works fine again.
So I'm releasing my current test version and I'll not update again until this issue is resolved.
What makes you guys think this issue will ever be resolved?
Nothing. I just hope it will otherwise I can no longer use Unity.
They won't fix it. They are completely ignoring this issue. There has been no official reply in over a month. Your project is dead. If you can't fix this on your end, you only have 2 other options. Start something else or move to another engine.
My game is released and has been for 4 years. I'm due to released on consoles later this year. If it's not fixed then I'll need to look at alternatives.
Xcode 9 works better, which leads me to believe this is more of an issue with Apple and Xcode than unity.
Yes using Xcode 9 solves the issue, for the moment.
But it’s important to remember that in 6 weeks we will all have to use Xcode 10 to submit apps and app updates. There will be no other option because you have to use the iOS 12 sdk.
And we will all need to be using at least MacOS 10.13 high Sierra, because Xcode 10 does not work on anything less.
This is definitely a big issue for all iOS developers. And I think once the Xcode 9 app rejections start in 6 weeks there will be a lot more developers looking for a solution.
Hopefully if everyone makes a bit more of a fuss, we can make something happen before that 6 weeks is up.
6 weeks? End of march you say?
I bet its a very very bad April fools joke... HAHA UNITY!
Anyway, How could we make more fuss?
Maybe a thread on the Apple developers forum? Threads with a lot of comments seem to attract mods there fairly well. If everyone watching this Unity thread posts on the Apple dev forum, we'd probably have quite a lot of comments.
Sounds like an Awesome place to start with.
Could anyone make a thread and link us?
Unity why not interested? This is a very important issue!
I am stil running MacOs 10.12 so i havent tested Xcode 10 yet.
But earlier in this thread there are links to what appears to be a way to keep using Xcode 9 with IOS 12 support.
Has anyone tested this? If the problem is with Xcode 10 itself, then can use Xcode 9 to upload our games with this 'hack' and still be accepted legitimately into the store and maybe this will solve the memory issue?
The only other solution i think is to figure out why exactly this problem is happening:
Is it a problem with Unity 5.6? 2017? 2018? all versions?
Is it a problem with MacOs high sierra? Mojave? All versions?
Is it a problem with Xcode 10 only?
Then we would know if there needs to be a fix by Unity or Apple and can focus our energy in the right place.
From what I have read in this post, its a problem with Xcode 10, because people on all versions of Unity and on multiple MacOS versions using xcode 9 do not have this problem.
xcode 9.4 ios 12.1 done build but not publish! required xcode 10.1 or later
I published my update with 9.4 on Saturday. Just ignore the warning as it says you may wish to change it,not you have to.
Maybe if we build it like this in Xcode 9.4 and then use Xcode 10 just to upload it the memory problem won’t be here?
Did you build an archive in 9.4? Or just test it on a device?
It might work. I built a project on PC from unity, copied it to my Mac mini,opened it in xcode 9.4 and built and uploaded from there.
yes build archive required xcode 10.1
Worked 4 full days on trying to optimize our assets and then found this thread!
Trying with 9.4.1 now.
Guys, if you want to force Unity to pay attention to this matter, you need to submit bug reports with repro projects.
With that said : @PauliusP and @ScottF I think another post from you on this thread would be nice, even if it is to let us know that nothing has changed since last time.
Great find. Sadly, this doesnt help me as part of the SOW was to update to iOS 12 and ARKit 2.0.
Atleast now we can point to XCode as the culprit.
I just want to makes sure I understand. Is this correct? :
You built your game in unity 2017
You opened it in Xcode 9.4
You added iOS 12 compatibility in Xcode 9.4 using the work around in the link above
You built an archive in Xcode 9.4
You then tried to upload that 9.4 archive using Xcode 10
You were given a warning that the upload required an archive built in Xcode 10?
Are these the exact steps you took or were any of them different? And has anyone else tried this?
Is it even possible to build to iOS 12 in xcode 9.4? even after spamming the Supported platforms folder with all the versions available the latest version it agreed to export is iOS 11.4 ...
Do you even read the posts?
Hey Derkoi, Thanks for the embracing reply.
I've just asked if it is even Possible to build & not submit due to udede's posts saying:
"xcode 9.4 ios 12.1 done build but not publish! required xcode 10.1 or later "
"yes build archive required xcode 10.1"
which is implying that the build does work but not submit.
It would have helped me to know because I need to build at least for our team's iphones in order to test changes.
Thanks for being such a polite and understanding community member.
Sorry. Didn't realise you'd asked that. I think based on the fact that iOS 12 SDK is included in xcode 10.1 and above it wouldn't be possible but you might be able to manually download and set it all up.
All cool now <3
I did try to manually download and set it all up but had no luck...
Did you try the method in the link above?
what appears to be a way to keep using Xcode 9 with IOS 12 support.
Sadly it doesn't work and it fails to recognise anything above iOS 11.4, therefore not even recognising our iPhones as a valid build targets.
a quick update on this. We are actively investigating this issue and apologies that it is taking so long to resolve.
At the moment it seems that there are at least two issues:
1) iOS 12 memory reporting tools has been updated, so you will see different numbers when running same app on iOS 11 or 12 devices. You will see similar pattern when using any Metal application, regardless of the engine being used.
2) iOS 12 jetsam rules can be the cause for different maximum allowed memory pressure for your apps.
These issues are slightly connected but still distinct, and the ultimate reason for unexpected termination is 2) and not 1).
We are working closely with Apple to find a solution for this issue.
Meanwhile, it would be extremely helpful to file bugreports with repro projects so we would have more projects to investigate.
Thanks for the updateI hope you can figure it out.
Sorry for your pain guys but thanks for posting this.
Just updating some legacy applications.
Have sorted the upgrades to 2018.2 (always stay a little behind the release wave) and the apps are working fine across webgl and android.
Have run into sudden crashes which look memory related with no change to code including in memory management that was otherwise stable in earlier versions of Xcode and Unity.
Instead of looking at possible coding errors will be trying building out in Xcode 9.4.1 and see if that fixes the problem.
Thanks for the heads up as if we don't have the crashing issue then its saved us a lot of time chasing down blind alleys.