Closed AshleyDeng closed 4 years ago
Workaround: use Legacy Build System. it works for me.
Great! We'll continue investigation for better solutions.
@AshleyDeng @mattiacantalu With 3.1.4 we were addressing a separate bucketing behavior issue in the obj-c SDK, we are still looking into whether a fix for these XCode parallel code build issues will be feasible for the Objective-C SDK.
Our recommendation in general is to move to our Swift SDK at your next upgrade opportunity, which will be our primary SDK for new iOS feature development moving forward. https://docs.developers.optimizely.com/full-stack/docs/migrate-to-swift-sdk
For the time being as @mattiacantalu cited the Legacy Build System should another workaround option until a migration is possible
@Danny-Driscoll Thanks for the response. And @mattiacantalu Thanks for the workaround!
We've investigated the proposed options but we think we will wait for the real fix. Reasons are:
Legacy Build System
due to some business reasons.@AshleyDeng We just released a patch (3.1.5) with a fix for this Xcode-12 build issue. Please give it a try and let us know if it works for you. Tx!
Hi, thanks for getting 3.1.4 up to address the build errors on XCode 12.
Comparing the 3.1.3 (https://github.com/optimizely/objective-c-sdk/issues/448), the number of build errors goes down but there are some errors still remaining.
Thanks again for the hard work!