Normally a production release would involve more testing, including manual tests, but this would delay delivering the Beta build. If the build passes, we run our automated test suites on it and release it.
When a beta version is released by Apple, Zendesk attempts to build the SDKs with the “Beta n” version: Zendesk doesn't release any versions of the mobile SDKs based on alpha releases from Apple. When Apple releases a new iOS or Xcode version (or Swift, until Apple releases the fully stable Swift Module Stability), the Zendesk policy for updating its iOS SDKs is as follows: What happens at Zendesk when Apple releases a new version of Swift, Xcode, or iOS? As soon as Swift 5.1 is released in a stable version, Zendesk will support module stability and forward-compatibility with future versions of Swift won't be a problem anymore. Apple is finally targeting its release as stable to Swift 5.1, and Zendesk is already working on integrating it in its iOS SDKs. Zendesk has been waiting for Swift Module Stability for a long time. What's Swift Module Stability and why is Zendesk not using it? Our customers may also not be able to use previous versions of the SDKs on top of the new versions without using a newly compiled version. The combination of Swift and closed-source means that Zendesk may need to release new versions of the SDKs every time Apple releases a new version of Swift, Xcode, or iOS. Each Zendesk mobile SDK is also distributed as a closed-source SDK (which means the SDK code is pre-compiled before being distributed to our customers). Most of the Zendesk mobile SDKs are written in Swift, with the exception of the 1.x versions of the Chat SDK. How does Zendesk distribute its SDKs, and what's the impact when a new version of Swift, Xcode, or iOS is released? This article answers common questions about the Zendesk update policy for its iOS SDKs.
0 kommentar(er)
