-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Carthage Based Build Fails App Store Validation #217
Comments
Hi @spr, Thanks for also testing this in Carthage. Like #216, we will also prioritize including a fix for this in 5.1 to resolve the app store submission rejection error. We appreciate your detailed reports! Thanks, |
Merged
gwhelanLD
added a commit
that referenced
this issue
Aug 4, 2020
## [5.1.0] - 2020-08-04 ### Added - The ability to specify additional headers to be included on HTTP requests to LaunchDarkly services using `LDConfig.additionalHeaders`. This feature is to enable certain proxy configurations, and is not needed for normal use. - Support for building docs with [jazzy](https://github.com/realm/jazzy). These docs will be available through [GitHub Pages](https://launchdarkly.github.io/ios-client-sdk/). ### Fixed - SDK causing nested bundles in archived product when including the SDK through Carthage. This caused rejections when submitted to the App Store. Thanks to @spr for reporting ([#217](#217)). - SDK causing application to expect LDSwiftEventSource dynamic framework when built with SwiftPM, which does not include the dynamic framework in the resulting application. This causes the application to be rejected when submitted to the App Store. Thanks to @spr for reporting ([#216](#216)).
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! |
Passes validation now, thank you! |
3 tasks
keelerm84
added a commit
that referenced
this issue
Sep 1, 2022
According to the CircleCI announcement on [June 2nd, 2022][1], several xcode images are going to be deprecated and removed. This commit bumps our xcode versions to a supported image version. [1]: https://discuss.circleci.com/t/xcode-image-deprecation/44294
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a support request?
No
Describe the bug
If you use LaunchDarkly 5.0.1 as a dependency to your project via Carthage, and submit your .xcarchive file to the App Store for validation, you receive the following validation failures:
To reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
App should pass validation
Logs
If applicable, add any log output related to your problem.
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.
The LaunchDarkly framework is embedding the LDSwiftEventSource framework. It shouldn't do that, LDSwiftEventSource should be added directly to the top level project.
The text was updated successfully, but these errors were encountered: