Table of Contents

Publish extension package

This article describes how to package and publish an EasyAR Sense Unity Plugin extension developed for a specific headset after development and runtime verification are complete, so users can conveniently use the extension.

Before you begin

Complete package definition

The package definition itself is in package.json. You can modify this file or create a new package according to the Unity guide for creating custom packages. Make sure to modify the package name and displayName, and avoid conflicts with the template provided by EasyAR 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 while Unity is closed, delete the entire Library directory, and then reopen the Unity project to regenerate .meta files.

Note that references in scenes and resource files will change, and you may need to recreate or modify some objects in scenes. Text replacement of GUIDs in .unity and other resource files is a feasible method.

Check version compatibility

Check version compatibility between the extension, the device SDK, and EasyAR Sense Unity Plugin.

Note

Starting from version 4000, EasyAR Sense Unity Plugin follows the semantic versioning required by Unity. Before that, every minor version may contain incompatible changes.

Package and publish

You may also want to modify some other files in the package. Carefully review the entire package before publishing.

It is recommended to use Unity package to package files. If the device SDK is not ready to be published in Unity package form, you can also choose to publish through asset package.

Remind users that all restrictions of the EasyAR license key, especially restrictions on custom cameras, apply to your extension package.