thehen In the last release we added internal support for XML parsing, but it's not yet exposed in JS. So, it's getting closer! Hopefully we'll find the time to add full XML parsing support for the next release.

Hello,

I can only answer some questions but here you go:

3.- CocoonJS supports Android 2.3 and above.

6.- The CocoonJS Launcher App provides a mock service to try in app purchases. Check out the code for our IAP demo. Anyway, I think Scirra has no support for CocoonJS IAP extension yet. Once you tested the mock implementation, the cloud compiler adds the real thing so you can try in a sandbox environment.

Regards,

Iker.

Hi triks

May be there is a problem with the provisioning profile. Could you take a look to build log, please? Thanks!

ludei.com/forum

Hi Lovelocke64

If you need more info about what CocoonJS is:

vimeo.com/45506217

Or visit our site at ludei.com

CoffeeOD

Ok, Anyway you can download the APK directly from here: wiki.ludei.com/cocoonjs:launcherapp

Hello CoffeeOD,

Let's see if we can help you here. First of all, can you tell us if you have tested the game using the CocoonJS Launcher? I cannot clearly state that from your post. If so, have you tried both iOS and Android versions of the launcher? Is the result what you expected? Before compiling with the cloud compiler, it is very important that you try your game with the CocoonJS Launcher App.

Once we know this went well, we can move forward.

Regards,

Ludei

CocoonJS does not support this functionality at the moment, sorry.

jayderyu

Please, if you have been facing problems with CocoonJS we would like to help you. If we have missed your support requests, please, get in touch with us again. If the demos provided with the launcher do not work, it is definitively something we need to look into. Have you tried CocoonJS in any other android device?

CocoonJS has support for LocalStorage. If you are using it, you should be good to go.

Arima,

At this moment, CocoonJS is HTML5 standard compliant on this matter. This means that an image is loaded to memory when it is loaded and deallocated when there are no more references to it. So, do not load images until you need them and be sure not tu reference them again if you are not using them anymore. I guess that with an authoring tool like Construct, it is difficult to have such a control and that is why Scirra has added some kind of "extensions" to handle resources more accurately. Ludei will try to provide this kind of APIs soon.

Regards,

Iker