Silviu are you using Construct 2 or 3? I'm not sure if the version of Google Play in C2 works in Android applications at the moment.

I'm assuming your using C3, based on the "Google Play Services stopped" message. When developing the plugin I noted that Play Services can be very fragile, and will sometimes crash when given invalid data instead of producing error messages. Also setting up your application online can be quite hard. Here's a checklist I have for using it:

• Create your game and leaderboards etc. through the Google Play console NOT the Google API console
• APKs must be signed
• Upload the SHA1 signature for your signing key
• Sign the APK with the same signing key that you upload the signature for
• Specify the app ID in the project
• Make sure your email address is under the list of testers on the Google Play Console
• Leaderboard/achievement caching is very aggressive, your device will always use it's local list instead of the remote if it can

If you haven't done any of the first 6 you won't be able to log in, it can be pretty frustrating.

kingpirux I would definitely recommend saving often, but even so if a save fails you should be able to try again? You can see the progress of file saves in a status message on the bottom left of the editor, and a dialog will appear if a save fails.

When saving to the cloud a dummy file is initially created with no content, then updated with the project contents. So if you see a 0kb file only the first half of the save worked.

Saves are created in memory then uploaded to the cloud, so there is kind of a local copy but it never exists on the filesystem. If you want there is an option to set up project autosaves in settings, you can set these to be saved to the browsers local storage so that your not completely reliant on your network connection. While these are stored on your hard disk you can't get to them via windows explorer and clearing your browser cache will delete them, so treat them as temporary storage!

Hey MassimoF, I'm the developer for the ArrayEditor. I'm glad you like it!

Could you show me an example of what you mean? I don't think it's a bug but it's best to check. We "pretty print" JSON files when we save them, it's supposed to make it more readable, but with the 3D arrays we use it can spread the file out quite thinly ( one value per line ). We used to export in the more compact format, but we had a request from a user to change it to a pretty printed format. They were using version control and when all the content is on one line it's very hard to use file diffing, as it basically shows the entire file as changed if a single character is changed.

The extra whitespace is ignored by the parser so it's purely for human eyes only. Incidentally I tried creating an empty 200 x 5 x 1 array and downloading it, and while it came to 152kB loose it compresses very well. Using DEFLATE which is what c3p and apk files uses it was only 985 bytes. Minified the file was 20kB loose and 167 bytes compressed. Perhaps we should offer some option for minifying JSON files during export.

I'd be careful using that regex for removing whitespace, as it would remove any spaces in your values as well! There's quite a few JSON minifiers/beautifiers around which will safely change your content for you. Here's one https://www.cleancss.com/json-minify/

Hi Silviu,

The documentation needs some updating, sorry about that. We recently updated it to use the native API methods when packaged up for Android. Before it used the web API, which had stopped working due to some changes on Google's part.

If you set up your App on the Google Play Console according to Google's documentation, then in C3 you only need to include the "Game ID" value for Android to work. This value is a number and can be in the Game services list underneath the game name. Make sure you do your setup on the Google Play Console NOT the Google API Console.

sizcoz Whoops, looks like you found some secret UI

I'm working on it yes, but it's not quite ready yet. The UI parts are included in the current releases but shouldn't appear at the moment. Should make life considerably easier when producing release builds!

Hi hackinc2000

We operate on a whitelist policy for using cordova plugins on the build server. Provided all goes well with your plugin drop me a bug report https://github.com/Scirra/Construct-3-bugs/issues when your finished and I'll review it and update the whitelist.

Anyone not using the build server is of course welcome to use whatever they want in their projects.

Also we've just launched the addon area of the construct.net site https://www.construct.net/gb/make-games/addons I'm sure you addon would make a great addition to the list

Hi there!

The "periodically back up projects" is basically an autosave. It will either create or update a file with a name that matches projectname._autosave_.c3p for the active project at the specified interval. You can choose which service you want it to save to using the location dropdown, but the actual location is decided by C3. It will either place it next to a file which matches the project name or at the root. If you choose the "Same location" option it will save it to the same service you opened the project from, so if your project is saved on Dropbox it will be saved to Dropbox. If you select "Google Drive" but you open your project from Dropbox it will autosave to Dropbox and so on and so forth.

Originally it was called "periodically back up projects" because it would only save to browser storage, and this was considered more of a temporary back up basically. I've since updated it to save to any service, so it's more of an autosave.

Some android devices can be a little awkward to open APK files. How are you trying to open the APK? Using some sort of filesystem app?

By the looks of the error it's actually trying to make a purchase now, but is failing with an invalid product ID. I had a quick look online and this error seems to cover a multitude of configuration issues...

Have a look through these and see how you get on http://troybrant.net/blog/2010/01/invalid-product-ids/. Some are complicated looking, so just start with the easiest ones.

One that stood out to me was that you had to use xcode to load the app onto the device, and you had to make sure to remove any old versions of the app from the device first.

There's a template on the issue tracker which will tell you what you need to include. The most important thing for this report would be a minimal .C3P file that you know produces a build that doesn't work when minified. The less in the project the easier it is for us to narrow down an issue, so ideally you would create a new project, add whatever plugins / behaviours you think are breaking it and check that it produces a broken build.

We've just published r81 which should workaround this issue. Could you give it a try?

I expect this is a particular plugin that doesn't agree with being minified, please file a bug report on GitHub and we'll take a look https://github.com/Scirra/Construct-3-bugs/issues