We just released an app that uses XCAssets for app slicing, are are getting a lot of crash reports via XCode (1700+ in 3 days). Here is an example offending thread:
0 libsystem_platform.dylib 0x243fe1c4 _platform_memmove$VARIANT$CortexA9 + 136 (memmove_CortexA9.s:166)
1 MyAppNameHere 0x0084054a AssetCatalogFile::Read(unsigned long long, void*, unsigned long long*) + 146 (AssetCatalogFileSystem.mm:47)
2 MyAppNameHere 0x0084005c AssetCatalogFileSystemHandler::Read(FileEntryData&, unsigned long long, void*, unsigned long long*) + 42 (AssetCatalogFileSystem.mm:187)
3 MyAppNameHere 0x006c0d26 FileAccessor::Read(unsigned long long, void*, unsigned long long*) + 40 (VirtualFileSystem.cpp:863)
4 MyAppNameHere 0x00525804 AssetBundleLoadFromFileAsyncOperation::ConvertArchive() + 236 (AssetBundleLoadFromFileAsyncOperation.cpp:74)
5 MyAppNameHere 0x005258d2 AssetBundleLoadFromFileAsyncOperation::ConvertArchiveJob(void*) + 18 (AssetBundleLoadFromFileAsyncOperation.cpp:48)
6 MyAppNameHere 0x005a47ce JobQueue::Exec(JobInfo*, int, int) + 68 (JobQueue.cpp:325)
7 MyAppNameHere 0x005a4780 JobQueue::Steal(JobGroup*, JobInfo*, int, int) + 180 (JobQueue.cpp:444)
8 MyAppNameHere 0x005a4958 JobQueue::ExecuteJobFromQueue() + 74 (JobQueue.cpp:641)
9 MyAppNameHere 0x005a4a26 JobQueue::ProcessJobs(void*, bool*) + 36 (JobQueue.cpp:720)
10 MyAppNameHere 0x005a43bc JobQueue::WorkLoop(void*) + 8 (JobQueue.cpp:754)
11 MyAppNameHere 0x006beca8 Thread::RunThreadWrapper(void*) + 46 (Thread.cpp:40)
12 libsystem_pthread.dylib 0x2440385a _pthread_body + 138 (pthread.c:656)
13 libsystem_pthread.dylib 0x244037ce _pthread_start + 110 (pthread.c:692)
14 libsystem_pthread.dylib 0x24401724 thread_start + 8 (pthread_asm.s:162)
There is no file in my project titled "AssetCatalogFileSystem.mm", which might be in a Unity lib, or is a private iOS class. I've googled for "AssetCatalogFile" and found practically nothing at all, and for "_platform_memmove" I get more results, but nothing specifically related to Asset Catalogs. Since we have not gotten any complaints about the app crashing, nor had we seen it crash ourselves, I came to the conclusion that it might be happening when users wouldn't notice, like in the background. I was able to reproduce the crash when hooked up to Xcode by backgrounding the app while it was doing the initially loading, thus verifying my supposition.
I guess my question is, is there any way to tell from the crash reports if the app was in the background or foreground when it crashed? If it is the case that the app is crashing in the background only, then I think I'm fine with that, as the user would know no better.