Search Unity

Unity iOs project gets crashed when returning from internal method UnityUpdateDisplayList()

Discussion in 'iOS and tvOS' started by Lisan, Oct 1, 2015.

  1. Lisan

    Lisan

    Joined:
    Jun 17, 2009
    Posts:
    220
    Can't find what caused this, maybe somebody knows?

    Unity 5.2.1f1, iPad mini 2, iOs 8.4

    I have Bad Access Error in this line of DisplayManager.mm:

    (BOOL)displayAvailable:(UIScreen*)targetScreen; { return self[targetScreen] != nil; }

    because of NIL in the argument.

    It seems when calling UnityUpdateDisplayList() method in Unity, iOs gets back null result.

    Can somebody help?
     
    Last edited: Oct 2, 2015
    Lisan, Oct 1, 2015
    #1

  2. MSJAKAY

    MSJAKAY

    Joined:
    Mar 14, 2015
    Posts:
    3
    Hi,

    I have exactly the same problem.

    Did u find the solution ?

    Thx,
    Jacks,
     
    MSJAKAY, Nov 9, 2015
    #2

  3. povilas

    povilas

    Unity Technologies

    Joined:
    Jan 28, 2014
    Posts:
    427
    @MSJAKAY

    Which version of Unity are you using?

    Could you please try 5.2.2p3? If the issue is still there, please file a bug and attach small reproduction project to it so that we can look into it. Please paste the bug id here.
     
    povilas, Nov 10, 2015
    #3

  4. MSJAKAY

    MSJAKAY

    Joined:
    Mar 14, 2015
    Posts:
    3
    Yes, I'm under 5.2.2.p3. I will submit the log bug as soon as possible. Thx
     
    MSJAKAY, Nov 11, 2015
    #4

  5. MSJAKAY

    MSJAKAY

    Joined:
    Mar 14, 2015
    Posts:
    3
    Here the file called "DisplayManager.mm" with something wrong (in Xcode / Unity-iPhone / Classes / Unity / DisplayManager.mm)
     

    Attached Files:

    MSJAKAY, Nov 12, 2015
    #5

  6. povilas

    povilas

    Unity Technologies

    Joined:
    Jan 28, 2014
    Posts:
    427
    Could you please submit the bug via bug reporter tool within Unity?
     
    povilas, Nov 17, 2015
    #6

  7. jmansa

    jmansa

    Joined:
    Apr 13, 2012
    Posts:
    75
    Did you find a solution? Got the same issue after updating to 5.2.3p1
     
    jmansa, Nov 28, 2015
    #7

  8. Hoskins355

    Hoskins355

    Joined:
    Jan 3, 2013
    Posts:
    142
    Turning on Objective-C Automatic Reference Counting in Xcode Fixes the problem.
     
    Hoskins355, Feb 21, 2016
    #8