“file uri scheme”

I have an application which records video along with some custom metadata and a chapter track. The resultant video is stored in the Camera Roll. When sharing the video via the Share Sheet or AirDrop, the metadata track is stripped entirely (the chapter markers are preserved) Sharing via AirDrop with the All Photos Data option does include the metadata track, as does copying from the device with Image Capture but this is a bad user experience as the user must remember to explicitly select this option, and the filename is lost when sending this way. I have also tried various other approaches (such as encoding my metadata in a subtitle track, which I didn't expect to be stripped as it's an accessibility concern) but it's also removed. Essentially I am looking for a definitive list of things that are not stripped or if there's a way to encode a track in some way to indicate it should be preserved. The metadata is added via AVTimedMetadataGroup containing one AVMutableMetadataItem which has its value as a JSON str

We have 7 Advanced App Clip Experiences that have been stuck showing Received in the App Store Connect UI for 90+ days. However, after inspecting the underlying API response, we can confirm all 7 experiences show key: PUBLISHED, doc_count: 7 on the backend. Despite this, scanning a QR code on a device without the app installed returns App Clip Unavailable on every experience. This appears to be a CDN propagation failure — the backend is PUBLISHED but the edge nodes serving iOS devices are returning stale or missing data. Evidence – – App Clip Diagnostics tool shows all green checks for our registered experience URLs (screenshots attached) – App Store Connect UI shows Received for all 7 experiences – Backend API response (/appclips/api/v1/experiences) shows: jsonstatuses: { buckets: [ { key: PUBLISHED, doc_count: 7 } ] } – iOS devices without the app installed still return App Clip Unavailable when scanning QR codes – App version 1.4(6) is live and Ready for Distribution – AASA file is correctly confi

Summary When an app is associated with a domain via applinks in the Apple App Site Association (AASA) file, the app's icon is displayed next to passkey entries in the iOS passkey selection UI (e.g., in Safari's sign-in dialog). This occurs even when: The AASA file does not contain a webcredentials section The passkey's relying party ID (rp.id) matches the domain, but the app has no webcredentials association The URL path of the passkey login page does not match any paths specified in the applinks configuration Environment iOS 18.6.2 iPhone 16 Pro Safari / Passkey UI via WebAuthn Steps to Reproduce Create an iOS app and register it in App Store Connect (or distribute via TestFlight) Configure the AASA file on the domain with only applinks — no webcredentials section: json{ applinks: { apps: [], details: [ { appIDs: [TEAMID.com.example.myapp], components: [ { /: /specific-path/* } ] } ] } } Implement WebAuthn/passkey registration on the same domain with the domain as rp.id Install the

We are developing a watchOS application that records long audio sessions and uploads them to our backend in chunks (~5 MB each) using pre-signed URLs and URLSession background upload. Current behavior: While audio recording is active, uploads continue successfully even when the app is in the background. Once the recording stops, if multiple chunks (e.g., 10+) are still pending, the remaining uploads do not proceed in the background and appear to be suspended. We attempted to use WKExtendedRuntimeSession (mindfulness type) to allow sufficient time to enqueue background upload tasks, but the session is invalidated when the app goes to the background (e.g., wrist down or app inactive), which prevents reliable scheduling of uploads. Additionally, we added the entitlement: com.apple.developer.extended-runtime-session (mindfulness) in the Watch app entitlements file, but Xcode automatic signing fails with: “Provisioning profile does not include the com.apple.developer.extended-runtime-session entitlement.”