Apple Errors

Troubleshoot common App Store Connect API errors when publishing prices with BasePrice.

Authentication Errors

"Invalid credentials"

Cause: The App Store Connect API key is incorrect or expired.

Solutions:

Verify your Issuer ID and Key ID match what's shown in App Store Connect
Ensure the .p8 key content includes the full key (including -----BEGIN PRIVATE KEY----- and -----END PRIVATE KEY----- lines)
Try creating a new API key if the current one was revoked

"Insufficient permissions"

Cause: The API key doesn't have the required access level.

Solution: The API key must have Admin access. Keys with App Manager, Developer, or lower roles can't modify pricing. Create a new key with Admin access in App Store Connect → Users and Access → Integrations.

"Key not found"

Cause: Newly created API keys can take a few minutes to propagate.

Solution: Wait 5–10 minutes and retry.

Rate Limiting

"Insufficient ASC API budget" / 429 Too Many Requests

Cause: Apple enforces rate limits on the App Store Connect API.

Solution: BasePrice handles this automatically with retries and increasing wait times. If the publish still shows partial failures:

Wait 5–10 minutes for the rate limit to reset
Re-publish only the failed countries

Product Errors

"Product not found" / 404

Cause: The native product ID in your platform mapping doesn't exist in App Store Connect.

Solutions:

Verify the product ID exists in App Store Connect → My Apps → In-App Purchases
Check for typos in the platform mapping
Ensure the product hasn't been deleted from App Store Connect

"Price tier not available"

Cause: The calculated price doesn't map to any valid Apple price tier for that territory.

Solutions:

Check if the base price is extremely low or high (Apple tiers range from $0.29 to $9,999.99)
Try adjusting your charming strategy to help prices land on valid tiers

Server Errors (500)

Cause: Apple's servers are experiencing issues.

Solution: These are typically transient. BasePrice auto-retries with backoff. If the error persists, check Apple's system status and retry later.