Packages containing .unitypackage files may be rejected if they obscure content, violating Submission Guidelines sections 2.2.a and 2.2.b. .unitypackage files should only be used for alternative render pipelines, setup preferences, settings, or supplemental files. Ensure the main content is unarchived and viewable, especially for packages supporting multiple render pipelines. To resolve rejections, avoid including .unitypackage or other archive files unless necessary for specific content types not natively compatible with Unity Editor.✨
Symptoms:
My package was rejected because it contains .unitypackage files.
My package was rejected for the reason: "Contains prepackaged file".
My package was rejected for having the entirety of its content in .unitypackage files.
Cause:
Your submission may have been rejected because the file organization of your package is against the Submission Guidelines.
According to sections 2.2.a and 2.2.b, .unitypackage files should not obscure the content of your product. This prevents customers from viewing the package setup from its Asset Store page.
.unitypackage files are appropriate for content associated with alternative render pipelines, setup preferences, settings, or supplemental files for other render pipelines. However, this doesn't mean that your entire package should be sorted into nested .unitypackage files.
This is especially true for alternative render pipeline packages. If your package supports the Built-In Render Pipeline, Universal Render Pipeline (URP), and High Definition Render Pipeline (HDRP), one of these must be considered the default render pipeline for your product, and its contents should be unarchived and viewable.
Resolution:
Ensure that your package does not contain .unitypackage or other archive files unless they are for alternative pipeline content, setup preferences or settings, supplemental files, or files not natively compatible with the Unity Editor (e.g., Blender files).