- My package was rejected for the reason: "Licenses required for third-party assets".
- My package was rejected for the reason: "Contains third-party content".
- My package was rejected for the reason: "Contains third-party, open-source files".
Your package might have been rejected because the vetting team has found content that is considered third-party (fonts, images, or audio created by someone else). If you include third-party content in the package, you must also include any licenses that apply to it. We don’t accept submissions that contain third-party assets if legitimate licenses are not included, or if the licenses require attribution or have other limitations.
If your product contains third-party content, please include license files (in .txt, .md, .pdf, or other readable file types). In addition, make sure the licenses are compatible with our EULA.
Here are some questions to answer when including third-party assets:
- Can the third-party content be resold commercially in its source form (as is done with packages on the Unity Asset Store)?
- Can third-party content be embedded in commercial applications without forcing restrictions like attribution, crediting the author, or other conditions on developers?
- Does the license of the third-party content allow customers to modify the content as the Unity Asset Store EULA does?
Follow these steps when including license information in your package:
- Include any license files with the content.
- Create a Third-Party Notices.txt file in your base package directory that specifies third-party files and their licenses.
- Make sure that the full text of the licenses is included, either with the content or in the Third-Party Notices.txt file.
- Add the following statement to your submission description and replace the text in brackets with file/component and license names:
- "Asset uses [name of component] under [name of license]; see Third-Party Notices.txt file in package for details".