Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice
New Forum User Notice Update to the Unity Editor Software Terms Unite 2023 - Ask the Experts Online

App Crash on 32 bit devices IL2CPP, Unity 5.1.1p1

Discussion in 'iOS and tvOS' started by Rokitt_Dynamix, Jul 3, 2015.

  1. Rokitt_Dynamix

    Rokitt_Dynamix

    Joined:
    Mar 4, 2015
    Posts:
    12
    Hi guys, i build app, IL2CPP Universal, if I build directly on my devices it crashes on any of my 32 bits devices. I tested on an iPad and iPhone 4 and it crashes.

    If I download the build on my iPhone 6 and iPhone5s it works.

    If i build empty project app work.

    Is it possible that I call some unsupported method while using IL2CPP Universal?

    Thanks!
     
    Rokitt_Dynamix, Jul 3, 2015
    #1

  2. JoshPeterson

    JoshPeterson

    Unity Technologies

    Joined:
    Jul 21, 2014
    Posts:
    6,775
    @Rokitt_Dynamix

    If something is unsupported by IL2CPP, you should see an error indicated what is unsupported in the Xcode console output. However, I'm unaware of anything which is supported on 64-bit devices but not on 32-bit devices. Can you provide any more details about the crash on 32-bit devices? Can you get a call stack for the crash in Xcode? That will help us track down the cause of the problem.
     
    JoshPeterson, Jul 6, 2015
    #2

  3. Rokitt_Dynamix

    Rokitt_Dynamix

    Joined:
    Mar 4, 2015
    Posts:
    12
    crash happened across a function call OnCollisionEnter() heard that this bug fixed in patch 3
     
    Rokitt_Dynamix, Jul 6, 2015
    #3

  4. JoshPeterson

    JoshPeterson

    Unity Technologies

    Joined:
    Jul 21, 2014
    Posts:
    6,775
    @Rokitt_Dynamix

    I'm not familiar with that specific bug fix, but please try 5.1.1p3 to see if it is corrected then. Thanks.
     
    JoshPeterson, Jul 6, 2015
    #4