Can't export packages in 5.3.1f1

Hey guys,

I'd like to know if someone also experienced this issue in 5.3.1f1

Everytime I try to export a package (folder with assets or single assets) the Export-Window pops up but shows me a message that there is nothing to import, which is weird, since I don't want to import anything but export my stuff:



Beyond that I also got this error-message:

NullReferenceException: Object reference not set to an instance of an object
UnityEditor.PackageExportTreeView.GetFolderChildrenEnabledState (UnityEditor.PackageExportTreeViewItem folder) (at C:/buildslave/unity/build/Editor/Mono/GUI/PackageExportTreeView.cs:113)
UnityEditor.PackageExportTreeView.RecursiveComputeEnabledStateForFolders (UnityEditor.PackageExportTreeViewItem pitem, System.Collections.Generic.HashSet`1 done) (at C:/buildslave/unity/build/Editor/Mono/GUI/PackageExportTreeView.cs:73)
UnityEditor.PackageExportTreeView.RecursiveComputeEnabledStateForFolders (UnityEditor.PackageExportTreeViewItem pitem, System.Collections.Generic.HashSet`1 done) (at C:/buildslave/unity/build/Editor/Mono/GUI/PackageExportTreeView.cs:66)
UnityEditor.PackageExportTreeView.RecursiveComputeEnabledStateForFolders (UnityEditor.PackageExportTreeViewItem pitem, System.Collections.Generic.HashSet`1 done) (at C:/buildslave/unity/build/Editor/Mono/GUI/PackageExportTreeView.cs:66)
UnityEditor.PackageExportTreeView.RecursiveComputeEnabledStateForFolders (UnityEditor.PackageExportTreeViewItem pitem, System.Collections.Generic.HashSet`1 done) (at C:/buildslave/unity/build/Editor/Mono/GUI/PackageExportTreeView.cs:66)
UnityEditor.PackageExportTreeView.RecursiveComputeEnabledStateForFolders (UnityEditor.PackageExportTreeViewItem pitem, System.Collections.Generic.HashSet`1 done) (at C:/buildslave/unity/build/Editor/Mono/GUI/PackageExportTreeView.cs:66)
UnityEditor.PackageExportTreeView.ComputeEnabledStateForFolders () (at C:/buildslave/unity/build/Editor/Mono/GUI/PackageExportTreeView.cs:49)
UnityEditor.PackageExportTreeView..ctor (UnityEditor.PackageExport packageExport, UnityEditor.TreeViewState treeViewState, Rect startRect) (at C:/buildslave/unity/build/Editor/Mono/GUI/PackageExportTreeView.cs:41)
UnityEditor.PackageExport.TreeViewArea (Boolean showLoadingScreen) (at C:/buildslave/unity/build/Editor/Mono/GUI/PackageExport.cs:213)
UnityEditor.PackageExport.OnGUI () (at C:/buildslave/unity/build/Editor/Mono/GUI/PackageExport.cs:136)
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:222)
Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Reflection/MonoMethod.cs:232)
System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) (at /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Reflection/MethodBase.cs:115)
UnityEditor.HostView.Invoke (System.String methodName, System.Object obj) (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:187)
UnityEditor.HostView.Invoke (System.String methodName) (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:180)
UnityEditor.HostView.OnGUI () (at C:/buildslave/unity/build/Editor/Mono/HostView.cs:76)



I already made a Bug-Report. Just wanted to know if someone else experienced this.

 

We experienced the same, tested and it happens on all our computers especially when exporting a large scene. Unity just hangs and we can't export the scenes anymore. Prefabs/textures/meshes or folders without scenes still export well. This didn't happen before unity 5.3 .

It always displays "Nothing to Import" on the exporting window while it could export. I believe it's a related issue.

Right now using unity 5.3.1f1. Same issue was existing in 5.3.0 .

Is there a link to bug report on issue tracker?

 

Mhm, seems related, yes.

Apparently there is non on the official issue tracker, I only have access to it via FogBugz.

 

@Matt Roper Uh, that's great. Will the fix be included in the next patch release?

 

I am also with this problem, I need to transfer some assets from one project to another and i can't, someone know any alternative way of passing assets without breaking the connections between them.

5.3.1p2 out, is fixed ?

 

Copying files together with meta files might help keeping dependencies. Tell me if this works, I remember doing this long ago.

 

Is this fix already out? We need this since we have to export scenes and such and it's easier to do it that way than copying the scenes+metafiles from the local directory and overwrite them on the projects of the team-members :/

 

No updates were released for free users since 30 days. I checked patch releases changelogs and couldn't find any information about exporting packages.

There are lot's of other major issues that didn't get solved since unity 5 release.

 

Looked at the patch notes for 5.3.1p4, seems there is no fix for this one :/
http://unity3d.com/unity/qa/patch-releases

@Matt Roper
Could you give us at least an ETA? Will it be in the 5.3.1-Cycle or will the fix come in 5.3.2?

 

As said, not able to export at all. For me it takes seconds till the "Nothing to import" appears and then it stays :/

Uh, 5.4? That's...bad, but yeah...nothing we can do about that.

 

Exporting crowded scenes (a city map) fails, we tried waiting an hour when this error occured first, "nothing to export" wouldn't disappear. Because of problem thats mentioned in this forum, finding dependencies takes significantly longer. (A crowded scene has lot's of dependencies).

@Matt Roper

I have a feature request if you can forward this to developers. (It's not completely about this bug)

"Include Dependencies" is toggled on when the window pops up. Because of this, everytime we wish to export an asset, unity hangs a long time looking for dependencies. If it was toggled off as default, export window would be usable in no time.

We've lost lot's of time waiting unity to find references where we don't need them. We usually toggle "include dependencies" off after waiting about 2 to 10 seconds. Yes, it's a usable (a great) feature, but it should be toggled off when window pops up, we should enable it optionally.

Especially for a crowded scene, without any bugs or glitches, when I click export, unity was hanging for about 15-20 seconds for the export list with dependencies to appear(on my intel i7 4790k overclocked cpu and 840evo SSD). When I toggle it off, it just takes a microsecond for the export list to appear.

 

@Matt Roper
Unity QA sent me a mail weeks ago stating that they fund the bug and the issue is closed, although there is no fix yet. But since you said it's coming and marked as necessary fix, I guess everythings fine. Anyway, here's the case-number:

756626

 

I have found that if you wait long enough for Unity to find all the dependencies the right information eventually appears, though its weird to hit "Export" and be told "Nothing to import"

 

Weird, if I wait long enough after hitting Export Unity freezes.

 

I was having this problem and force closing Unity since it appeared hung up on the nothing to import pop up. But this time I left it running while I searched this topic. Upon returning back to Unity, the export list had populated! Just try waiting for a while?

 

As mentioned already, if I wait for a while Unity freezes.

 

We still get this bug in 5.3.5p4

 

Still the same bug in 5.5.0f3? What's the deal?

We have a team of developers working on different functionality in different packages and we're now going to need to blend everything manually it seems, if this functionality isn't available?

Is there any functionality like "Blend differences" available?

We have subscribed for two Pro licenses and have just on-boarded another couple of programmers.

This is going to really hamper our development if there isn't some functionality to blend forked code and scenes/packages back together.

Doing this manually is potentially going to now take us months given our developers have been working on various versions of the same package.

Looking back on this page, it looks like the issue was first reported around two years ago?? (or am I mis-reading something here?)

 

Hey there just an Information about this bug.
Uninstalling Unity don't fix it. I clean every project too.
I tried on a VM and It works the first time and then same.
Hope that could Help I'm in 5.5.2f1

 

I still get this bug in 5.6.2
and I can't import anything from asset store

 

I found out what was the issue. If you download package multiple times in same folder, windows will name the file as "package (1).unitypackage" and this produces this error. When I removed "(1)" from the name, it worked properly

 

Thanks IcyHammer - this should be the answer.