Search Unity

  1. We would like to hear your feedback about Unity and our products. Click here for more information.
    Dismiss Notice

Timeline for Unity 2019.2.x availability?

Discussion in 'Unity Cloud Build' started by echeg, Apr 18, 2019.

  1. echeg

    echeg

    Joined:
    Aug 1, 2012
    Posts:
    60
    Timeline for Unity 2019.2.x availability in Cloud Build? (beta\alpha)
     
  2. victorw

    victorw

    Unity Technologies

    Joined:
    Sep 14, 2016
    Posts:
    94
    We don't typically include alpha versions in UCB since there's relatively little demand for them and there are often instabilities which are normally resolved by the time a beta release comes out. If you require 2019.2 for your builds then you can submit a support ticket and we are able to enable an alpha version for you. Otherwise, expect to see us adding 2019.2 shortly after the beta version is released, once UCB validation is complete.
     
  3. echeg

    echeg

    Joined:
    Aug 1, 2012
    Posts:
    60
    In 2019.1x Cloud Build I have problem with Packages.
    Code (CSharp):
    1.   "com.unity.2d.sprite": "1.0.0",
    2.     "com.unity.2d.tilemap": "1.0.0",
    3.     "com.unity.modules.androidjni": "1.0.0",
    And 2019.2.x have downgrade issues to 2019.1.x in scene serilization
     
  4. Arkitome

    Arkitome

    Joined:
    Jan 1, 2015
    Posts:
    3
    We're experiencing the same problem as @echeg with both porting an older project and with a brand new project. Cloud build under 2019.1x appears broken for those packages?

    Have tried:

    * Using a different version (2018.x)
    * Changing manifest
    * Building a brand new project
     
  5. victorw

    victorw

    Unity Technologies

    Joined:
    Sep 14, 2016
    Posts:
    94
    This isn't really enough information for me to go on - what issue are you experiencing? If you are creating projects in 2019.2 then being unable to downgrade to earlier versions of Unity is an unfortunate reality which is going to be a very frequent issue for the next year or two as Unity switches over to packages. If you want to build in 2019.2 then 2019.2.0b2 is currently available in production and I will try to add a few more 2019.2 versions today.
     
  6. Arkitome

    Arkitome

    Joined:
    Jan 1, 2015
    Posts:
    3
    Thanks for the reply - Here's more detail @victorw.

    We are pulling out our hair trying every combination we can think of to update the manifest.json to allow for a successful build. We've tried reducing it down to nothing, to reimporting the project, and everything (that we can think of) in between.

    Here's the reported error that are consistently popping up. It looks like whatever container is pulling down the unity build environment isn't able to resolve any of the packages. Right now we've shifted up to 2019.3.0a5, and I just now realized the cloud build is "Always use latest 2019.1" ... which is not 2019.3... would that matter?

    106: [Unity] [Package Manager] Done resolving packages in 0.74s seconds
    107: [Unity] An error occurred while resolving packages:
    108: [Unity] Project has invalid dependencies:
    109: [Unity] com.unity.2d.sprite: Package [com.unity.2d.sprite@1.0.0] cannot be found
    110: [Unity] com.unity.2d.tilemap: Package [com.unity.2d.tilemap@1.0.0] cannot be found
    111: [Unity] com.unity.package-manager-ui: Package [com.unity.package-manager-ui@2.2.0] cannot be found
    112: [Unity] com.unity.timeline: Package [com.unity.timeline@1.1.0] cannot be found
    113: [Unity] A re-import of the project may be required to fix the issue or a manual modification of /BUILD_PATH/<mybuildpath>/Packages/manifest.json file. 114: ! Unity player export failed!
     
  7. victorw

    victorw

    Unity Technologies

    Joined:
    Sep 14, 2016
    Posts:
    94
    Yes that does matter - none of those packages are available in 2019.1 so the project cannot be built in 2019.1. You would have to manually downgrade your manifest.json before builds would succeed in 2019.1 (and this would cause your builds to fail in 2019.3).

    You will experience this same issue if you open the project locally in a 2019.1 editor. One of the easier ways to resolve this is to delete your manifest.json and then open the project in 2019.1, although if you have complex dependencies this may introduce more issues than it resolves.
     
    Arkitome likes this.
  8. Arkitome

    Arkitome

    Joined:
    Jan 1, 2015
    Posts:
    3