Swift 5.1.1

11 Comments

  • Igor Makarov
    Comment actions Permalink

    This is because Zendesk didn't add .swiftinterface files. Until those are added, it will continue happening on each release!

     

    This is a new format introduced in Swift 5.1 and is intended for use by library vendors to ensure forward-compatibility of the libraries.

    To emit these new interface files, you need to pass `BUILD_LIBRARY_FOR_DISTRIBUTION=YES` to your xcodebuild commands.

    Here's an example project that shows how it's done: https://github.com/bielikb/xcframeworks

    Enabling Swift Library Interfaces will be very helpful going forward as a new Xcode version would not require waiting for a new Zendesk SDK.

    3
  • Joey
    Comment actions Permalink

    Thanks for that input, Igor.

    Swift module stability is still a roadmap item, but there is no timeframe as to when it will complete.

    -4
  • Brilliant
    Comment actions Permalink

    Xcode 11.2 was released today, is there an ETA on a Swift 5.1.1 compatible release of the SDK? 

    0
  • Tdrummond
    Comment actions Permalink

    Would it be possible to update the policy to clarify Zendesk's position?

    3
  • Kyle Rokita
    Comment actions Permalink

    I would also like to ask that you make Module Stability a priority. We are also waiting on a Swift 5.1.1 compatible release of the SDK for Xcode 11.2. This wait occurs for each Swift update so supporting module stability would provide a much more flexible developer experience.

    5
  • Viktor Rutberg
    Comment actions Permalink

    We're also waiting for a Swift 5.1.1 compatible build -- FYI this is currently holding us back from upgrading to Xcode 11.2.

    Thanks
    Viktor

    0
  • Steve Tibbett
    Comment actions Permalink

    Also affected here.  I'm surprised this isn't addressed yet.

    0
  • Max Brunner
    Comment actions Permalink

    Hi everyone,

    Some updates around XCode 11.2 and Swift 5.1.2:

    Our iOS teams are fully committed and working right now on a new release of Support SDK to unblock you with XCode 11.2. This release will contain the Swift interface file inside our fat framework to enable module stability for our SDK. Given the high number of bugs in iOS 13.2, we expect that a new version of iOS might come around sooner than later, so the Swift interface file will get you unblocked nonetheless.

    In parallel, we're also working around the support of proper xcframeworks for our SDKs, to give you the definitive support of module stability. One of the problems we're facing here is that most of our integrators depend upon CocoaPods, which still doesn't support xcframeworks.

    We'll keep you all updated as we progress through these solutions and new releases.

    Thanks,
    Max.

    1
  • Simon Mitchell
    Comment actions Permalink

    Hi Max,

    Unfortunately it seems like the pre-compiled version hosted for carthage users was built with Xcode 11.2 which means it suffers from the same crash that caused Apple do disable distribution of apps from that version of Xcode. I'm sure you can appreciate that this means that the vast majority of devs will have already moved to Xcode 11.2.1 (GM) which resolves this crash.

    Unfortunately it seems the binaries also exhibit this crash (Caused whenever a UITextView is within an interface builder file). Is there any way you could quickly re-compile the frameworks from Xcode 11.2.1? This shouldn't be more than a 10 minute job for your devs!  

    Thanks,
    Simon

    0
  • Max Brunner
    Comment actions Permalink

    Hi Simon,

    We released another version of our iOS SDK yesterday, the 4.0.0, which was compiled with XCode 11.1 and contains module stability inside our fat frameworks. This version should not present the problem you described. Can you double-check to see if are you using the correct, last, version?

    Thanks,
    Max.

    0
  • Simon Mitchell
    Comment actions Permalink

    Hi Max,

    Thanks for getting back to me!

    Unfortunately carthage doesn't yet support module stability in their latest stable release so due to them not being up to date this doesn't help us at the moment. We'd drop back to manually installing the SDKs but unfortunately I'm a 1 man team doing 3 people's jobs at the moment and we have a very tight deadline with both the app this is affecting and other apps so I don't have the time to do that work really!

    Thanks again,
    Simon

    0

Please sign in to leave a comment.

Powered by Zendesk