some .crash files for which there is not much information other than the "Dyld Error Message:

Originator:kbeitz
Number:rdar://25072879 Date Originated:2016-March-09
Status:Closed (Duplicate of 24278648) Resolved:Duplicate of 24278648
Product:iOS Product Version:various
Classification: Reproducible:
 
we have some .crash files for which there is not much information other than the "Dyld Error Message:" quoted below.

in some cases, the crash recurs repeatedly on a device until the device is reset.

we are also experiencing some crashes in applicationDidFinishLaunching:withOptions: where either (a) an exception is thrown for a selector for a particular class when that selector is a known good selector in a class in an embedded .framework; or (b) an EXC_BAD_ACCESS occurs in a c-style function called from obj-c, where the function is a known good function, and normally exists, but belongs to an embedded .framework.  in both of these cases, it's as though the .framework does not load.  this is not reproducible on demand, merely the results of crash logs reported from the field.

Dyld Error Message:
Dyld Message: Library not loaded: @rpath/Decodable.framework/Decodable
  Referenced from: /var/mobile/Containers/Bundle/Application/A9F0345B-9FFE-43DE-880F-20AF7BE616CF/Fabric.app/Fabric
  Reason: no suitable image found.  Did find:
	/private/var/mobile/Containers/Bundle/Application/A9F0345B-9FFE-43DE-880F-20AF7BE616CF/Fabric.app/Frameworks/Decodable.framework/Decodable: mremap_encrypted() => -1, errno=12 for /private/var/mobile/Containers/Bundle/Application/A9F0345B-9FFE-43DE-880F-20AF7BE616CF/Fabric.app/Frameworks/Decodable.framework/Decodable

	/private/var/mobile/Containers/Bundle/Application/A9F0345B-9FFE-43DE-880F-20AF7BE616CF/Fabric.app/Frameworks/Decodable.framework/Decodable: mremap_encrypted() => -1, errno=12 for /private/var/mobile/Containers/Bundle/Application/A9F0345B-9FFE-43DE-880F-20AF7BE616CF/Fabric.app/Frameworks/Decodable.framework/Decodable
  Dyld Version: 370.6

Steps to Reproduce:
we don't really have steps to reproduce.  the only way we know about it is that many, many end users run the app, and we get some number of crash reports, while the rest of our end users are able to run the code just fine.

Expected Results:
using a dyld or a .framework loads the framework in time for use, and doesn't crash.

Actual Results:
some crash reports are occurring.

Comments

probably a dupe of rdar://25126016


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!