The following error occurred in the launch of our game iOS version after accessing the easy Access SDK
Dyld:library not loaded: @rpath/onlineahelper.framework/Onlineahelper referenced from: /var/mobile/containers/bundle/application/35ed2a71-7f60-4a16-ba4c-ecd6493a1ee1/yzg.app/YZG reason:no suitable image found. Did find:/Private/var/mobile/containers/bundle/application/35ed2a71-7f60-4a16-ba4c-ecd6493a1ee1/yzg.app/frameworks/ Onlineahelper.framework/onlineahelper:mmap () Error AAt address=0x0349e000, size=0x00014e70Segment=__linkeditinchSegment::map () Mapping/Private/var/mobile/containers/bundle/application/35ed2a71-7f60-4a16-ba4c-ecd6493a1ee1/yzg.app/frameworks/ onlineahelper.framework/Onlineahelper/Private/var/mobile/containers/bundle/application/35ed2a71-7f60-4a16-ba4c-ecd6493a1ee1/yzg.app/frameworks/ Onlineahelper.framework/onlineahelper:mmap () Error AAt address=0x034c6000, size=0x00014e70Segment=__linkeditinchSegment::map () Mapping/Private/var/mobile/containers/bundle/application/35ed2a71-7f60-4a16-ba4c-ecd6493a1ee1/yzg.app/frameworks/ Onlineahelper.framework/onlineahelper
find this post after Google Https://stackoverflow.com/questions/32730312/reason-no-suitable-image-foundSome workarounds are given, including cleaning up the cached data, reinstalling the certificate, and so on. At first I tried the methods almost all over again, but I still didn't solve the problem. when you re-analyze a problem, you suspect that it is a CPU architecture issue for the compilation target. My test machine is iphone5s + IOS 9.2, the compilation target architecture chose ARMv7use the file command to view the easy-to-connect library content, which contains two versions of ARMV7 and arm64. IPhone5S is the CPU of the arm64 architecture, so the recompile chooses the arm64, the problem solves successfully. cause of error:32-bit libraries after the IOS9 system loaded into the 64-bit machine, 32-bit pagesize changed from 4096 bytes to 16384 bytes, causing the 32-bit app to load a dynamic library that could not run on a 64-bit subnet. There are two ways to resolve this:1. Added in the other linker flags in the project of the dynamic library
-wl,-segalign,4000
2. Upgrade the app to support arm64 architecture (which is what we do now) RELATED Links: https://stackoverflow.com/questions/34707643/32-bit-app-with-dynamic-library-crash-on-64-bit-device
iOS run Error "Dyld:library not loaded" cause analysis