User Profile

Hi, We are seeing a crashing bug with relatively high frequency in our app related to EAAccessory and the OS appearing to trigger an assertion when a run loop source is signalled. The crashes occur in a variety of device types, but all crashes are on iOS 14, not earlier OS versions. If anyone has some tips for how I might go about debugging this, I'd appreciate it. Our app interfaces with MFI peripherals from several vendors, so much of the EAAccessory related code we have is from closed-source third party SDKs.

We have some code in our app to perform heavyweight Core Data migrations that will use temporary intermediate stores as part of the migration. I'd like to cleanly handle situations where there is not enough disk space free to perform the migration (as opposed to other errors that could take place during the migration). It's not obvious to me what NSError values would be used by Core Data to signal out of disk space during a migration.Specifically, I'd like to know about error values returned during NSMigrationManager- (BOOL)migrateStoreFromURL:(NSURL *)sourceURL type:(NSString *)sStoreType options:(NSDictionary *)sOptions withMappingModel:(NSMappingModel *)mappings toDestinationURL:(NSURL *)dURL destinationType:(NSString *)dStoreType destinationOptions:(NSDictionary *)dOptions error:(NSError * _Nullable *)errorand also NSPersistentStoreCoordinator- (BOOL)replacePersistentStoreAtURL:(NSURL *)destinationURL destinationOptions:(nullable NSDictionary *)destinationOptions withPersistentStoreFromURL:(NSURL *)sourceURL sourceOptions:(nullable NSDictionary *)sourceOptions storeType:(NSString *)storeType error:(NSError**)error NS_AVAILABLE(10_11, 9_0);any additonal information would be much appreciated…