iOS Build Environment Help Center

Delete

(Leave this as-is, it’s a trap!)

To delete this post you must be either the original author or a designated moderator.
The content of the post will be removed but the name and date will remain.

  • The post will be removed completely from the thread, rather than blanked
  • Only posts on the last page of the thread can be removed completely (so as to not break permalinks)

RE[3]: Getting crash upon app launch. Remote debugger not providing useful information

Pierre-Marie Baty

Interesting. So that's the symptom of a memory exhausted error. The iOS kernel sends a SIGKILL message to your app and it shuts down immediately without being given even the ability to run any shutdown code.

The operating system already uses RAM up to a certain level. Given the device model (especially if it's old), iOS version, and the number of installed apps (especially apps that run background tasks or services), the available memory for new apps may be too low for yours.

At the moment I don't think the toolchain would be the culprit (until I am shown that the very same Xcode project, when built on macOS, doesn't exhibit the same symptom when deployed on the very same device). But the Unity engine is likely to consume a lot of RAM indeed. Maybe you're running your app on a hardware ecosystem that's out of its specifications ?

Moderators: Pierre-Marie Baty