(Case 1086863) Component script cannot configure anymore after converting into embedded package

After converting to embedded package, the script attached to game object becomes cannot be configured anymore and shows associated script cannot be loaded warning. I really hope this issue can be fixed then I can plug in/out package like a boss.

Before
3741832--310795--upload_2018-10-2_18-52-30.png

After
3741832--310792--upload_2018-10-2_18-51-22.png

1 Like

Are you using an assembly definition file in your package?
What does the package contents look like?
Did you keep the script meta file when you moved it over?

I didn’t use assembly definition file.
3749920--311740--upload_2018-10-4_15-45-37.png
Yes. I do keeping the script meta file.

Could you share your Editor log files? Unity - Manual: Log files

No need for that, we have them already.

2 Likes

Hey. We looked at your example project and the following warning is emitted

If you are using scripts inside of a package they must be within an assembly definition file(asmdef).

Please note that embedded packages are not yet a publicly documented feature and are still considered ā€œinternalā€, notably to minimize this kind of situations.

2 Likes

Does it means the requirement of package is either use assembly definition file for scripts or make it as dll?

A package must have all its scripts within one or more assembly definition files. Just stick an asmdef at the root for all your player scripts and another one if you have any editor scripts. Your project does not need to use asmdefs, just the package. The asmdef will create a dll for you.

4 Likes