Closed alexcroox closed 2 years ago
o-alexandrov
commented
2 years ago Using Cordova setup on AppCenter would have been pointless, as Cordova support was only for preview w/o ability to build. So while the idea to document a self-managed solution would be great, the mentioned AppCenter news has nothing to do with this particular project.
Some references how you should have configured AppCenter instead (as a native iOS / Android project):
alexcroox
commented
2 years ago Ah excellent news, apologies I'm still waiting to implement this in a sprint but I've been following closely since the last project used Cordova CodePush and assumed it was the same setup in AppCenter. Thanks for the clarification!
alexcroox
commented
2 years ago @o-alexandrov what did you choose as your platform? I chose iOS / Objective-C/Swift in their web UI and got the following when trying to later add deployments keys;
➜ xxxx git:(feature/ota-native) appcenter codepush deployment add -a xxx/xxx-ios-sandbox Production Error: [{"message":"Not Supported platform / OS combination: Objective-C-Swift / iOS"}]
Edit: ignore me, I realise now your "choose native" message previously meant "choose React Native"
o-alexandrov
commented
2 years ago @alexcroox please follow mentioned articles above.
Native means iOS / Objective-C and Java / Kotlin
alexcroox
commented
2 years ago Yeah I followed that originally and got the above error when trying to add deployment keys. Looking into it seems codepush is only for React Native / Cordova so selecting one of the other project types wont work.
o-alexandrov
commented
2 years ago Sorry, I misunderstood you. If you want the OTA (codepush), you should pick React Native. If you want the TestFlight/App Store or Google Play distribution, you should pick a native project.
You can have two AppCenter projects for the same app, one for the OTA and another one for the Builds to stores
https://devblogs.microsoft.com/appcenter/announcing-apache-cordova-retirement/