Requested Changes Are Not Necessarily a Rejection

A product may be returned when issues need to be corrected before it can meet marketplace requirements.

Common Reasons

Requested changes may involve incomplete documentation, inaccurate descriptions, missing installation instructions, broken functionality, security concerns, licensing issues, misleading screenshots, poor packaging, or inconsistent version information.

Security Issues

Products must not expose secrets, passwords, private keys, malicious code, unauthorized tracking, or unsafe behavior.

Security concerns may require additional review.

Listing Accuracy

The product page must represent the actual product.

Features should not be advertised if they are not included or do not function as described.

Licensing and Ownership

Developers may be asked to clarify ownership or licensing where third-party components, images, libraries, or other copyrighted material are included.

Responding to Requested Changes

Read every requested change carefully.

Correct the underlying issue rather than making cosmetic changes intended only to pass review.

When resubmitting, ensure that the updated files and listing are consistent with each other.

Repeated attempts to bypass review requirements may result in additional moderation action.