We're evaluating Apple-hosted Background Assets for an app distributed on App Store and would like to understand the security model behind it before adopting it. So far the public documentation only mentions the HTTPS requirement for asset transport. We'd appreciate any additional documentation or guidance covering: How asset downloads are authenticated (e.g., is access tied to the app's entitlement/provisioning, or is there a separate token/credential mechanism?) How access to specific assets is controlled/scoped Where Apple-hosted assets are physically/logically hosted (e.g., is this CDN-backed, and is there any control or visibility over hosting region?) Any other security considerations typically associated with cloud-hosted content (encryption in transit and at rest, integrity verification, etc.) Is there a more detailed security/architecture document beyond the public developer documentation, or can someone from the team point us in the right direction?

Hello, We're evaluating Apple-hosted Background Assets for an app distributed on the public App Store. Is there any documentation or guidance on update latency, specifically: How quickly are asset updates propagated to devices once a new version is published? More specifically, is propagation near-immediate, or should we expect a delay (minutes/hours/days) before devices know they have to pick up the new version in the ideal condition of being connected to Wi-Fi, locked, charging and the app has been recently used? Are there any other factors other than the aforementioned ones that affect how fast an update reaches a device? Any official documentation, WWDC session, or guidance from the team would be appreciated, thanks in advance.