Problems editing photos ios8

Question

I am developing a photo editing application and I want to have an extension for the Photo application. Enxtension works great on the simulator and no problem.

But when I try to run it on my iPhone 6, I have 2 problems:

• Problems with Provisioning profiles. I know that for the extension I need a new AppID (named app.myapp.com.extension and the main AppID is app.myapp.com) and new training profiles. I created 2 new channels to create (one for development and one for distribution) with a new AppID, but when I try to run it on the device, the following message appears:

Error: The embedded binary is not signed with the same certificate as the parent application. Checking the built-in binary settings of the character of the code mark corresponds to the parent application. Embedded Binary Signature Certificate: - (Ad Hoc Signature Code) Parent App Signing Certificate: iPhone Developer: Mauro Vime (------------------)

I updated the Provisioning Profiles to verify that for development, not for Ad Hoc, but I still have the same problems.

2. So I tried to export ipa from the application and run it. The application works perfectly, but the extension just shows a black look, and not my view containing the photo. Then I checked the phone crash logs and saw the following:

Incident ID: 9E578D78-FAB7-419E-AB35-7BA7B0821AFA CrashReporter Key: ae6bdea47a4e64b09a8fb7fa8599b5e23ceb5311 Equipment Model: iPhone7.2 Process: extension [2598] Way:
/private/var/mobile/Containers/Bundle/Application/----------/------------/PlugIns/extension.appex/extension Identifier: app.myapp. com.extension Version: 1 (1.0) Code Type: ARM-64 (native) Parent process:
launchd [1] Date / Time: 2014-10-14 01: 29: 21.482 +0200 Launch Time: 2014-10-14 01: 29: 16.170 +0200 OS Version: iOS 8.1 (12B407) Report Version: 105 Exception Type: EXC_CRASH (SIGABRT) Subtype of exception: LAUNCH_HANG Exception message: Advanced time took too long to initialize the highlighted topic: 0 Backtrace unavailable Unknown thread associated with ARM Thread state (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x000000000000 x2: 0x00000000 x3: 0x00000000000000000000 x4: 0x00000000000000000000 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000000 x8: 0x0000000000000000 x9: 0x0000000000000000 x10: 0x0000000000000000 x11: 0x0000000000000000 x12: 0x0000000000000000 x13: 0x0000000000000000 000000000 x15: 0x0000000000000000 x16: 0x0000000000000000 x17: 0x0000000000000000 x18: 0x0000000000000000 x19: 0x0000000000000000 x20: 0x0000000000000000 x21: 0x0000000000000000 x22: 0x0000000000000000 x23: 0x0000000000000000 x24: 0x000000000000 x0000: 000000000000000000000
x28: 0x0000000000000000 fp: 0x0000000000000000 lr: 0x0000000000000000 sp: 0x000000016fdb3b68 pc: 0x00000001200f9000 cpsr: 0x00000000 Binary images: 0x1200f8000 - 0x12011ffff dyld arm64 / USR / Lib / dyld

It says that the application was running on device 8.1, but I also tried it on iOS 8.0.2 and the same problem occurred. After viewing the message: “The extension took too long to initialize,” I just cleared the viewDidLoad and viewWillAppear functions so that they would not execute any code, but the problem persists.

Does anyone have experienced these problems and had a solution?

Answer 1

Maybe you are not using 64-bit architecture (required for extensions)? See the “Note on 64-bit Architecture” in the Apple Application Extension Programming Guide .

Answer 2

Make sure that the Architectures and Virtual Architectures contain arm64 , and that for the active configuration (debug / release) only the active architecture is built No.

We have built an active architecture. Only for Yes, so Jenkins built only the armv7 binary (although xcode built the correct binary depending on the connected device). It seems that armv7 applications work fine on arm64 devices, but extensions for armv7 applications cannot load with the strange error "The extension took too long to initialize." After fixing Build Active Architecture, only the live binary file setting (armv7 + arm64) is installed, and the extension works fine.

Answer 3

I ran into both problems:

For the problem with code signatures, I believe that there is an error in Xcode related to adding application targets. This initially confused me, and I ended up with this error. - You need to remove and update the provisioning profiles for the application and the application extension in the Developer Center. - If you are using an application group to exchange information, remove it from the features and the Development Center and enable them again in the "Features" section.

For LAUNCH_HANG problem, it seems that there is a finite and small (undocumented) window for expanding to full load before iOS abandons it. - view all your code that is related to your extension. Do not include anything you do not need.

My particular problem was that I added podspec for my extension purpose. I copied the target for my main application and did not understand that I included Flurry in the extension. Nothing wrong with Flurry, but it is a large static library that needed to be mapped into memory when the host application launched my extension. Deleted and the error disappeared.