One of the main selling points of your platform is the ease with which we can move to different versions of Xcode. Losing this ability certainly lowers the value proposition for me.
We are currently supporting an app running Xcode 9.2.x, and forced migration before end of year would be reason enough for me to seek out another platform.
I’m sure we’re not unique in this regard. Switching versions of Xcode literally means rewriting your app in a different version of Swift, so it’s not something to take lightly.
As a side note, you also deprecated our billing subscription model a couple weeks ago, forcing us to migrate to another account and re-enter all of our billing information just to scale up our build process. Again, the whole point of this platform --I thought-- was that it makes life easy for the developer. The more hoops I have to jump through, I might as well just be maintaining a Jenkins node.
@markshiz_knowink we hear you. We publish these deprecation posts as early as possible to collect feedback, and we thank you for your feedback!
We also heard Xcode 9.2.x for React Native can be important, so we’ll keep that stack longer.