Troubleshoot ASO Signals and contact support

Resolve common Apple connection and missing-data problems, and send useful diagnostic details.

Written By Enrique Bonansea

Last updated About 2 hours ago

Use the exact message shown in ASO Signals to choose the next step. A connection failure, an inaccessible app, and a feature that is not yet available are different situations.

The dashboard cannot check my connection

If Settings shows Connection setup is temporarily unavailable, use Retry connection check before entering a key again. A failed status check is not proof that your saved connection has been deleted.

If a connection attempt times out, the key may already have been saved. Check the saved state before resubmitting. For a rate-limit message, wait a few minutes before trying again.

Apple rejects my key

  • Use the Key ID and .p8 file from the same key.

  • For a team key, verify the matching Issuer ID and remove accidental spaces.

  • For an individual key, select the individual-key option; no Issuer ID is used.

  • Check that the key has not been revoked and that its Apple team and permissions cover the intended apps.

A permission failure should be addressed for the affected capability. Broader permissions do not activate analysis or reports that are unavailable in the current release.

My app or listing is missing

  1. Confirm the connected Apple team and app access.

  2. Choose Refresh apps in Settings and check the result.

  3. Confirm the app is selected as Active for ASO.

  4. Open the app and select the intended version, app information record, and listing language.

  5. Use Refresh listing and check Data health if the listing appears outdated.

Unreleased apps may lack public artwork or release information. Unavailable listing fields are not confirmed empty fields. Missing performance reports or keyword metrics can also reflect current release limits.

Contact support

Open ASO Signals Support and choose Contact support, or email support@emonster.com. Include ASO Signals in the subject so the team can identify the product.

Provide the page and action, exact error message, approximate time and timezone, app ID, and selected version and language where relevant. Explain what you expected and what happened. A screenshot can help if unrelated personal or confidential details are removed.

Never send private-key files, private-key contents, passwords, recovery codes, one-time sign-in codes, or access tokens. Start with a general description for a confidential unreleased app, then share only the details needed through the agreed support channel.