Release the extension package
This article describes how to package and release the EasyAR Sense Unity Plugin extension developed for a specific headset after completing development and running verification, so that users can easily use the extension.
Before you begin
- Complete the development of Make the headset support EasyAR.
- Complete Running verification (bring-up) to ensure normal operation on the device.
Complete the package definition
The definition of the package itself is in package.json. You can modify this file or create a new package according to Unity's guide to creating custom packages. Make sure to modify the name and displayName of the package, and be careful not to conflict with the EasyAR-provided template itself or extensions from other vendors.
Regenerate meta files
Delete and regenerate the .meta files for all files in the package. Otherwise, they may conflict with the template itself or extensions from other vendors.
Note
Unity may cache .meta files. It is recommended to delete all .meta files in the package and the entire Library directory while Unity is closed, then reopen the Unity project to regenerate the .meta files.
Note that references in scenes and resource files will change, and you may need to recreate or modify some objects in the scene. Replacing GUIDs in .unity and other resource files through text substitution is a feasible method.
Check version compatibility
Check the compatibility of the extension with the device SDK and the EasyAR Sense Unity Plugin.
Note
Starting from version 4000, EasyAR Sense Unity Plugin follows the semantic versioning required by Unity. Before that, each minor version may contain incompatible changes.
Package and release
You may also want to modify some other files in the package. Make sure to carefully review the entire package before release.
It is recommended to use Unity package to package the files. If the device SDK is not ready to be released as a Unity package, you can also choose to release it through an asset package.
Users should be reminded that all restrictions of the EasyAR license key (especially those related to custom cameras) apply to your extension package.