Post

Replies

Boosts

Views

Activity

Reply to Background Assets Directory Collision
The system effectively merges all of your asset packs into a single directory hierarchy. You can think of it as your app’s single, shared asset-pack namespace. The system expects that every individual file have a relative path from the root of that shared namespace that’s unique across all of your app’s asset packs (though not necessarily across multiple apps). An asset pack’s ID is not part of the unique path, but every other path component is. In your case, Foo/10/239/414.png and Bar/10/239/414.png are distinct paths that shouldn’t collide. This is also what I suspected from observation. That also actually works out great for something like map tiles, unless there are duplicate files. I would much prefer to just list the images as z/x/y.png, but duplicates appear to resolve in an error. I suspect that you’re testing your app on OS 26, not OS 26.1. There’s a known issue with AssetPackManager.url(for:) in OS 26 that we fixed in OS 26.1 beta I was testing with 26.0.1. I'll upgrade and give it a go! Thank you for the quick reply!
Oct ’25
Reply to Background Assets testing in Xcode
To test with Xcode you have to run a local server. https://developer.apple.com/documentation/backgroundassets/testing-asset-packs-locally
Replies
Boosts
Views
Activity
Dec ’25
Reply to How are Assets removed?
This is also still an issue with 26.1 Beta 4
Replies
Boosts
Views
Activity
Oct ’25
Reply to How are Assets removed?
This is still an issue with 26.1 Beta 3
Replies
Boosts
Views
Activity
Oct ’25
Reply to Increase Background Asset Limitations
Hi Albert, To be fair the Developer Support Team completely missed the mark on what I was asking and referred me to a code signing guide. If you could kindly help guide the query to the appropriate team, that would be very helpful. Thank you, Tanner
Replies
Boosts
Views
Activity
Oct ’25
Reply to Background Assets Directory Collision
The system effectively merges all of your asset packs into a single directory hierarchy. You can think of it as your app’s single, shared asset-pack namespace. The system expects that every individual file have a relative path from the root of that shared namespace that’s unique across all of your app’s asset packs (though not necessarily across multiple apps). An asset pack’s ID is not part of the unique path, but every other path component is. In your case, Foo/10/239/414.png and Bar/10/239/414.png are distinct paths that shouldn’t collide. This is also what I suspected from observation. That also actually works out great for something like map tiles, unless there are duplicate files. I would much prefer to just list the images as z/x/y.png, but duplicates appear to resolve in an error. I suspect that you’re testing your app on OS 26, not OS 26.1. There’s a known issue with AssetPackManager.url(for:) in OS 26 that we fixed in OS 26.1 beta I was testing with 26.0.1. I'll upgrade and give it a go! Thank you for the quick reply!
Replies
Boosts
Views
Activity
Oct ’25
Reply to Background Assets - Apple Hosted - iOS26
Doesn't appear to work on simulator. Use a device
Replies
Boosts
Views
Activity
Oct ’25
Reply to CKShare Fails with quotaExceeded Error on Family iCloud Plan
Thank you Ziqiao. I had filed a feedback but thought there could be a quicker response here to get it to the correct team. Please feel free to reach out for any further questions. Feedback: FB16214848 (CKShare Fails with quotaExceeded Error on Family iCloud Plan)
Replies
Boosts
Views
Activity
Jan ’25
Reply to Assert in line 204: PhotoGrammetrySession crashes while running with more than 10 images
Hello, I just redownloaded the sample project this morning. It's now updated to use the new Observation and builds without failure. But I'm still having issues with Assert line 204 during reconstruction. Xcode: Version 15.0 beta 8 (15A5229m) iPhone 12 Pro Max - iOS 17.0 (21A5291h)
Topic: Spatial Computing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Sep ’23