I'm putting this integration within a dynamic .framework that's separate from the main app and need to bundle in Smartling.plist into that bundle. The problem is that you're using +[NSBundle mainBundle] which assumes Smartling.plist is in that bundle. I managed to bypass it with swizzling all calls to -[NSBundle URLForResource:withExtension:] but it's a giant hack that shouldn't be needed.
Alternatively, would it be possible to instead use +[NSBundle bundleForClass:[SMCredentials class]] to get the bundle that linked in your static library instead? That would work for our use case while still returning the main bundle in the default integration.
I'm putting this integration within a dynamic .framework that's separate from the main app and need to bundle in Smartling.plist into that bundle. The problem is that you're using
+[NSBundle mainBundle]
which assumes Smartling.plist is in that bundle. I managed to bypass it with swizzling all calls to-[NSBundle URLForResource:withExtension:]
but it's a giant hack that shouldn't be needed.Alternatively, would it be possible to instead use
+[NSBundle bundleForClass:[SMCredentials class]]
to get the bundle that linked in your static library instead? That would work for our use case while still returning the main bundle in the default integration.Thanks!