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

Resolved (Case 1336903) Exporting a package is broken

Discussion in '2021.2 Beta' started by Deleted User, May 15, 2021.

  1. Deleted User

    Deleted User

    Guest

    Using 2021.2.0a17 I wanted to export a very small package containing two scripts. Normally the operation should be instantaneous but nothing happened; Unity froze and I had to kill its process in the task manager.

    in my project directory, in the "Temp" folder I found another directory named "Export Package" containing another folder named by a series of numbers, itself containing an "asset.meta" file.

    Opened in a text editor the "asset.meta" file reads:
    Code (CSharp):
    1. fileFormatVersion: 2
    2. guid: 2719456758e79395081b451df67840e4
    3. folderAsset: yes
    4. DefaultImporter:
    5.   externalObjects: {}
    6.   userData:
    7.   assetBundleName:
    8.   assetBundleVariant:
    And there was a warning in the console but I couldn't access the console, Unity being frozen, I just got what the editor showed at the bottom of the screen:

    Capture d’écran_2021-05-15_18-07-30.jpg
     
  2. Deleted User

    Deleted User

    Guest

    Updating the thread with case number: 1336903.
     
  3. Deleted User

    Deleted User

    Guest

    @LeonhardP

    Here we go, my bug reports are rejected again because I'm not using the "right" Linux distribution:

    Not counting the *** recommendation at the end of it...

    I suppose all the others will be rejected too. What's the use then?

    Edit: apparently, the bug was tested under Ubuntu and wasn't reproduced. That's what the qa team should've said in the first place instead of slamming the "you don't use the right Linux" door at my face.
     
    Last edited by a moderator: May 27, 2021
  4. LeonhardP

    LeonhardP

    Unity Technologies

    Joined:
    Jul 4, 2016
    Posts:
    3,111
    Apologies for the confusion. The team is generally trying to reproduce reported issues for Linux on supported distros, even if the reports originate from unsupported distros. In this case, the issue wasn't reproducible and thus closed.

    What's wrong with the recommendation?
     
    Deleted User likes this.
  5. Deleted User

    Deleted User

    Guest

    Exporting a package is broken only in 2021.2.0a17 and a few previous alpha versions and all my projects are created on the external SSD mentioned.

    To make things clearer (I hope):
    1. Linux is installed on an external SSD,
    2. this external SSD has two partitions,
    3. on one of them the editors are installed,
    4. on the other the projects are installed.
    I've never had any problems with that organisation.

    Now I'm waiting for a20 (since a18 and a19 have been cancelled) to see if this happens in that version too.
     
    Last edited by a moderator: Jun 3, 2021
  6. Deleted User

    Deleted User

    Guest

    In the meantime, I tried exporting a package a last time in 2021.2.0a17. I created a new project, added a script, for good measure, and launched the process. 40 minutes later, still no package. The last line of the log is that one:
    Code (CSharp):
    1. Start ondemand import (priority Urgent): Assets/Scenes (Guid(8aae9321f5eb4f80db485559185a154b) Importer(815301076,1909f56bfc062723c751e8b465ee728b))
     
  7. Deleted User

    Deleted User

    Guest

    Ha ha! Fixed in 0a19! :D
     
    LeonhardP likes this.