Closed spr closed 4 years ago
Hi @spr,
Thanks for the issue report! We appreciate you giving the new major release a try, and letting us know about this app store submission rejection. We'll start looking into this right away to get a 5.1 release out to correct this issue.
Thanks, @gwhelanLD
Hi @spr,
We've just released 5.1.0 which should resolve this issue. Please give it a try and let us know if you run into any issues.
Thanks! @gwhelanLD
The otool -L
output looks good to me. I'm not actively using SwiftPM (it was a fallback because of the carthage issue), so not in a great place to validate the app store submission side.
Closing this for now, thanks for taking a look even though you didn't plan to use SwiftPM.
Thanks, @gwhelanLD
Is this a support request?
No
Describe the bug
If you use SwiftPM to add LaunchDarkly 5.0.1 to an application, and submit to the app store, it is rejected with
According to https://developer.apple.com/library/archive/technotes/tn2435/_index.html#//apple_ref/doc/uid/DTS40017543-CH1-TROUBLESHOOTING You can obtain the dynamic libraries the app is expecting via
otool -L <AppName>.app/<AppBinary>
. When run on a sample project the output includes:However, SwiftPM dependencies use static linking. Consequently, the framework is not included in the resulting application.
To reproduce Steps to reproduce the behavior.
otool -L
and drag the binary onto the terminal, hit enter, observe the@rpath
present.Expected behavior No
@rpath
present inotool -L
output.Logs Full
otool -L
output for test project:SDK version The version of this SDK that you are using. 5.0.1
Language version, developer tools Xcode 11.6
OS/platform macOS 10.15.5
Additional context Add any other context about the problem here.