Attention iOS 10, 11, and 12 Users:
At iZotope, we are constantly improving our products to ensure the best experience for our users. Since the Spire team is a small group dedicated to developing our app to work with Apple’s newest updates and devices, we’ve had to make the tough decision to discontinue development for mobile devices running iOS 10, 11, and 12. By doing this, we can focus on ensuring Spire evolves with the latest technology from Apple.
Q: What does discontinued support mean?
A: The Spire app for iOS will now be officially developed for and supported on iPhones and iPads running iOS 13 or higher.
Q: What happens if you don’t update beyond iOS 12?
A: If you have a device with iOS 10, 11, or 12, the last compatible version of the Spire app will be the only eligible update available in the App Store. After you’ve updated to that version, you will not be able to update the app further without updating your iOS.
The features of the iOS 10, 11, and 12 compatible version will remain unchanged and continue to function as they do on your device today. Some older Apple devices including but not limited to the iPhone 4 and 5 are not compatible with newer iOS versions and cannot be upgraded beyond iOS 10.
Q: What if I have Spire Studio hardware?
A: The information above is true for Spire Studio hardware users with iOS devices on iOS 10, 11, and 12. Once you’ve updated to the last compatible app version, you will not be able to update the app or hardware further without updating your iOS. You will still be able to use your Spire Studio with its current functionality if you do not update.
Q: What if I have Spire Studio hardware and use multiple devices to pair to it?
A: If one of your devices is on iOS 13 or newer and it updates your Spire Studio, other devices on iOS 10, 11, or 12 may no longer be able to pair with your hardware until you update their iOS.
Q: Why are you discontinuing support for iOS 10, 11, and 12?
A: With iOS 14 now available and a growing number of devices that we’d like to support from Apple, we needed to prioritize what areas of development our team could focus on.