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

UNITY 5.0.0f4 >>> UNITY 5.0.1f1 trouble!

Discussion in 'Editor & General Support' started by Anjimo, Apr 29, 2015.

  1. Anjimo

    Anjimo

    Joined:
    Apr 22, 2014
    Posts:
    14
    Hello everyone! I'm making a game for IOS devices and faced with many problems when transferring the project from version 5.0.0 to 5.0.1. It all started with that old project stopped working in the editor, referring to an error

    Leaderboard not found
    UnityEngine.Social:LoadScores(String, Action`1)


    The fact that the code has not been platform verification, after the addition of verification problem disappeared:

    if (Application.platform! = RuntimePlatform.WindowsEditor & Application.platform! = RuntimePlatform.WindowsPlayer) {
    Social.localUser.Authenticate (ProcessAuthentication);
    }


    However annoying the fact that in version 5.0.0 this error does not occur.
    After this correction, I started to do an update to their already released games in the version 5.0.1 in the editor, everything went well until I tried to build for the Ipad. Game compiles, run on iPad ... and hung on the home screen. xCode issued line:

    exc_bad_access (code = 1 address = 0xffffff07)

    I tried to make in Unity 5.0.1 build his old project that was successfully met in the version 5.0.0 and have placed in Appstore - the same mistake!
    Please tell me, what could be wrong? Or at least how to move revised draft back to the version 5.0.0?

    The game uses a unity Ads.
     
  2. Anjimo

    Anjimo

    Joined:
    Apr 22, 2014
    Posts:
    14
    SOLVED
    The problem was resolved by switch off dynamic batching.