Is your feature request related to a problem? Please describe.
Please providing pre-compiled .unitypackage files like most other companies that interface with Unity and move away from requiring every developer to compile their own and import via tarball.
Right now, users need to pull down the source code and run some python scripts in order to generate tarballs for each module, which requires you to have your toolchain set up as expected by the plugins and leaves room for developer error in building these packages. Every time I have built these plugins I have run into some sort of nebulous issue that isn't obvious how to solve (usually something with my toolchain). Everyone else working in the Unity ecosystem just provides you with a .unitypackage to download and import into your project, so getting stuck on a step like this is extra annoying, especially seeing as messing with my toolchain could also break other tools I use.
Additionally, once you have the .tgz files, it's still awkward because if you import it incorrectly then the tarball is just referenced by the project and not imported into it. We've had at least two cases of this plugin working correctly on one person's computer but links not being set up correctly once it's in version control. I know there is a line about this in the quick start guide, but it's easy to overlook.
Describe the solution you'd like
Provide pre-compiled .unitypackage files for developers to import into their projects.
Describe alternatives you've considered
Any alternative would just add work for developers - the hope is to have one person at Apple do the work and then all developers using these plugins can benefit.
Additional context
Thank you for your consideration.
Is your feature request related to a problem? Please describe.
Please providing pre-compiled .unitypackage files like most other companies that interface with Unity and move away from requiring every developer to compile their own and import via tarball.
Right now, users need to pull down the source code and run some python scripts in order to generate tarballs for each module, which requires you to have your toolchain set up as expected by the plugins and leaves room for developer error in building these packages. Every time I have built these plugins I have run into some sort of nebulous issue that isn't obvious how to solve (usually something with my toolchain). Everyone else working in the Unity ecosystem just provides you with a .unitypackage to download and import into your project, so getting stuck on a step like this is extra annoying, especially seeing as messing with my toolchain could also break other tools I use.
Additionally, once you have the .tgz files, it's still awkward because if you import it incorrectly then the tarball is just referenced by the project and not imported into it. We've had at least two cases of this plugin working correctly on one person's computer but links not being set up correctly once it's in version control. I know there is a line about this in the quick start guide, but it's easy to overlook.
Describe the solution you'd like
Provide pre-compiled .unitypackage files for developers to import into their projects.
Describe alternatives you've considered
Any alternative would just add work for developers - the hope is to have one person at Apple do the work and then all developers using these plugins can benefit.
Additional context
Thank you for your consideration.