# Common app rejections

> The reasons Shoplazza Apps are most often rejected in review, from OAuth not firing on Add App to unnecessary scopes — check yours against them first.

There are several common reasons why apps are rejected during the review process:

* When a merchant clicks **Add App** from the [app’s listing](/docs/app/getting-started/create-public-app/create-app#manage-listings), the app does not immediately authenticate using [OAuth](/docs/app/developer-tools/api-libraries#shoplazza-oauth-sdks) before any other steps occur.
* When a merchant clicks **Add App** from the [app's listing](/docs/app/getting-started/create-public-app/create-app#manage-listings), the app returns a fatal error.
* The app listing is incomplete or too short, or it includes missing screenshots, grammar and punctuation issues, or promotional videos disguised as screencasts.
* The app requests more API permissions than are actually required for its functionality.
* Uncaught errors and bugs.
* Installation instructions were not provided when code changes are required to integrate the app into a merchant’s store.
* Sign-up or sign-in forms fail to auto-populate fields like store address and email address. Using information from the `shop` object can retrieve this data from a merchant’s store and help with auto-populating forms.
* After installation, the widget that the app is supposed to display does not appear on the merchant’s store.