Problem in embedding the Peach SDKs into app via sub-frameworks

Follow

The Peach SDK is accessing mobile.connect-resources.bundle using

[[NSBundle mainBundle] pathForResource:@"mobile.connect-resources" ofType:@"bundle" inDirectory:nil]

The problem with using mainBundle is that if the Peach SDK is ever embedded into the App via a sub-framework or cocoa pod or any other target other than the main target this check will fail.

In a particular scenario the bundle was not connected to the mainBundle but rather through another framework target.

This worked with the App until a switch was made to using Frameworks over static libraries for bundling our dependencies.

The reason for this is:

The SDK contains some resources that it looks for in a specific folder when it's not integrated directly but via another framework the resources might be somewhere else. There are ways to work around this, but we have not implemented them right now.

Have more questions? Submit a request

Comments

Powered by Zendesk