Sign up

background_asset_version_app_store_release_state_updated

Learn about the BACKGROUND_ASSET_VERSION_APP_STORE_RELEASE_STATE_UPDATED webhook event. Fired when a background asset App Store release state changes.

App Store ConnectBackground Assets
background_asset_version_app_store_release_state_updated

The BACKGROUND_ASSET_VERSION_APP_STORE_RELEASE_STATE_UPDATED event fires when the App Store release state of a background asset version changes. This tracks whether your background assets are approved and available for production distribution.


When does it fire?


This event triggers when a background asset version's App Store release state transitions — for example, when it's approved for release or when the release state changes during the distribution process.


Payload highlights


The payload includes the app ID, asset version identifier, and the new release state. This is important for apps that rely on background assets being available when your app is downloaded.


How Yeethook helps


If your app relies on background assets (large downloads, ML models, game content), you need to know when those assets are cleared for App Store distribution. Yeethook delivers these status changes to your team's channel so your release team stays informed.


Common use cases


  • Confirm background assets are approved before triggering a phased rollout
  • Track asset release state alongside your app version release state
  • Get alerts if background asset distribution is blocked

Example payload

Same oldState and newState attributes as the other background asset events, but these values come from the App Store release track rather than upload processing. relationships.instance names the release record, not the asset version that was uploaded.

{
  "data": {
    "type": "backgroundAssetVersionAppStoreReleaseStateUpdated",
    "id": "607fea97-a6ba-445d-a9ba",
    "attributes": {
      "timestamp": "2026-09-12T14:30:45Z",
      "oldState": "IN_REVIEW",
      "newState": "REJECTED"
    },
    "relationships": {
      "instance": {
        "id": "607fea97-a6ba-445d-a9bd",
        "type": "backgroundAssetVersionAppStoreReleases",
        "links": {
          "self": "https://api.appstoreconnect.apple.com/v1/backgroundAssetVersionAppStoreReleases/607fea97-a6ba-445d-a9bd"
        }
      }
    }
  }
}

What it looks like in Slack

Info

Background asset App Store release updated

State change
In Review → Rejected

Questions about background_asset_version_app_store_release_state_updated

Is a REJECTED here the same as my app version being rejected?

No. Background assets carry their own review and release track, so a rejection on this event says the asset release was turned down while the App Store version can still be moving through review. Version outcomes arrive on APP_STORE_VERSION_APP_VERSION_STATE_UPDATED instead.

How do I tell this apart from the external beta event in my channel?

Only by the wording of the headline — "App Store release updated" against "external beta release updated". Both use the same package emoji at info level and both carry a State change row, so routing rules should key off the event type rather than the message text.

What states can appear here?

Apple documents review-flow values such as IN_REVIEW and REJECTED for this event, which is a different vocabulary from BACKGROUND_ASSET_VERSION_STATE_UPDATED and its PROCESSING and FAILED values. Treat the two state sets as unrelated when you write matching logic.

Learn More

Official Apple documentation:

Get this event in Slack or Discord

Connect Yeethook to receive background_asset_version_app_store_release_state_updated notifications in your team's Slack or Discord channels.

Get Started Free