Closed PierreLouisPAUGAM closed 3 years ago
Hi,
Does the assets/plugins folder exist? If not try to create before import. Never seen this error before.
The only thing I could think of is the libraries not be able to import, but it should as they are tagged as any OS and mono compatible.
Could you try to import this package? I exported directly from Unity Editor instead of the generated by CI.
Hi and thanks for your answer.
The "ProjectRepo/Assets/Plugins" didn't exist so I created it but the end result was the same.
I downloaded "UnityStreamDeckExportedByEditor.zip" but it doesn't contain any .unitypackage file. Is it another way to import packages ?
Inside the zip file, there's a .unitypackage file that you can import.
Extract the zip anywhere, go to the Unity Editor, right-click on the Assets folder, import package and select that file.
Ok, when I tried to unzip it with the built-in macOS solution it also unzipped the .unitypackage at the same time hence the issue. I downloaded a third party software "The Unarchiver" and it worked.
I was able to import the package in my Unity project that way. Thanks a lot for your time, I'd star your repo if it was not already done :)
If you keep the version I exported manually over the version from GitHub releases you can delete the test.txt file that is inside: Assets/Plugins/StreamDeck/Editor/
For some reason, the OS was identifying the .unitypackage file as a folder.
I was able to import the package in my Unity project that way. Thanks a lot for your time, I'd star your repo if it was not already done :)
Thank you, I hope it helps.
Expected Behavior
When selecting the .unitypackage in the Finder it should add the package to my Unity Project.
Actual Behavior
Steps to Reproduce
The exact first two steps from the "Getting Started" section. I reproduces it with multiple project including a blank one.
I don't have any issue with other packages.
Specifications