I did observe the weirdness with intermediate stages. But I also can't get custom stages to work at all. public static func nsStagedMigrationManager() -> NSStagedMigrationManager { .init( [ NSCustomMigrationStage( migratingFrom: v1, to: v2 ), ... ] ) }

This is a question about Background Assets, not On-Demand Resources. But I believe they likely behave in a similar manner. I'm not accessing an NSPersistentStore currently. Just destroying and writing the 3 required .sqlite files. But reworking that into a NSPersistentStore is a great idea. I'll take a look at the tech note and see if it further solves my issue. Thank you

How did you get this to work?

Do you know when this will be available? It's still failing on simulator in 26.2

FB20750028 (Increase Background Asset Limitations)