Use standard framework file hierarchy about appcenter-sdk-apple HOT 5 CLOSED

Hey @ianbytchek,

thx for getting in touch.
Can you share a little bit more about how you are integrating the SDK (if you don't want to do so publicly, please send me an email to bereimol at my employer dot com, or get in touch through intercom – the blue button at the bottom right corner in the portal)?

You are right that we don't follow the Xcode convention as we haven't done that for HockeyApp for a while and it's not uncommon to simplify the structure within fake frameworks.
This leads me to why you are seeing the error. The App Center SDK is actually a static library and not a dynamic framework (HockeyApp is a dynamic framework). My guess is that you added the AppCenterPush.framework under "embed framework". Please make sure you this is not the case – the AppCenter*.frameworks need to be linked but not embedded (they need to appear in "Link Binary with Libraries").

Please let me know if this solves the issue for you and don't hesitate to get in touch!

Benjamin

from appcenter-sdk-apple.

Hey @TroubleMakerBen! I've created a Cocoa app in Xcode for testing purposes, I don't use CocoaPods and simply downloaded the release. Integrated AppCenter.framework, AppCenterAnalytics.framework and AppCenterCrashes.framework by linking and embedding. Yes, AppCenterPush.framework had some issues – I think it requires entitlements and additional provisioning, so I dumped it from the beginning. The app builds fine without signing, but fails with aforementioned error when signing is enabled:

My guess is that you added the AppCenterPush.framework under "embed framework". Please make sure you this is not the case – the AppCenter*.frameworks need to be linked but not embedded (they need to appear in "Link Binary with Libraries").

I think we're referring to different things. Unless I embed all linked non-system frameworks the distributed app won't run – loader won't find them and will 💥 !

I've seen similar Xcode behaviour in the past when it expects certain file structure of bundle / framework, which didn't make a lot of sense to me personally, but it is how it is. The app builds and runs since dependant frameworks resemble the conventional structure, but, apparently, certain tools, like codesign, need it to actually be conventional. Of course it can be manually signed, but I'm pretty sure we'd be better off with a proper solution?

from appcenter-sdk-apple.

Hey,

First, thx for making the gif above. This makes the conversation so much easier. I really appreciate you taking the time. That said, we are definitely talking about the same thing.
You are copying/embedding the frameworks in a phase in the "Build Phases" tab, which can't work for static libraries. Please simply link the libraries and don't embed them.

I've recorded a quick video.

Best,
Benjamin

from appcenter-sdk-apple.

Hey Ben, ok, I finally got what's going on. Apparently you're creating static frameworks – never witnessed on in the wild before! Makes perfect sense now, thanks! Working on and using @Gifox for gifs, emailed you a present. 🦊

from appcenter-sdk-apple.

Hey @ianbytchek,
Thx for the present, I was wondering what that one was about ^^

I'm sorry that I didn't explicitly say that App Center is a static framework, I've taken a note to be explicit about this and not assume people read that much between the lines.

Take care and let me know if there's anything else we can do for you. Oh, and thx for trying out App Center. =)

Benjamin

from appcenter-sdk-apple.