@wetfeet since a while back we’ve been experiencing some issues with the Community website. Usually refreshing the page once is enough to do the trick. We will look at updating NodeBB (seems to be the cause of the errors) but it may take some time. Anyway thanks for reporting and sorry for the inconvenience.
How did you add the SDK configuration in config.xml file? Here is an example of how you should manually config the SDK settings:
<!-- Add them as preference elements -->
<preference name="android-minSdkVersion" value="10" />
<preference name="android-maxSdkVersion" value="22" />
<preference name="android-targetSdkVersion" value="21" />
<!-- Or you can use a config-file element for them -->
<config-file target="AndroidManifest.xml" parent="/*">
<uses-sdk android:maxSdkVersion="22" android:minSdkVersion="10" android:targetSdkVersion="21" />
Monaca CLI uses it’s own version of Cordova. At the moment, it uses cordova ^5.0.0 which fetches email@example.com. The latest cordova 7.0.1 fetches cordova-android@~6.2.2.
In general, monaca platform add and cordova platform add are actually the same command, so feel free to use the cordova one to fetch the desired version of the platform. Just keep in mind that some cloud features, like remote build, may not work due to a not compatible platform version.
In this case, on my machine, firstname.lastname@example.org seems to have problem finding and executing the appropriate Android SDK tools. cordova-android@~6.2.2 is fine though.
I have been digging into this, found the actual issue, the plugin that we are using requires play services 10.0.1 and that does not seem to be on the cloud server, 10.0.0 is. How do I go about getting the patch release on the cloud builder?
You must call any APIs of a Cordova plugin within “deviceready” event which signals that Cordova’s device APIs have loaded and are ready to access…
They will appear “undefined” if you call them before they are completely loaded. Also, please make sure you call each API properly.