I think the issue is probably that your using your package identifier for your game id. Game id is badly named, most of the time it will be the same as your application id. It should look like 12345678987. This will be preventing you from logging in, and the other methods will fail if your are not logged in.

I've changed the name of it for the next release to "Application ID (android)" which will hopefully make it a little more obvious for people.

Hey everyone, just as a reminder the new runtime is considered "early alpha". Some things are missing, or broken. We're releasing it so that you get a look at what we're working on, and that we can find some of the more illusive bugs. If you want to read more, check out Ashley's blog post.

I've had a look at Demonoire and it looks like the Spritefont plugin is broken at the moment, which is stopping it from loading.

C3 will allow you to use mp4 video, but we rely on the runtime environment ( chrome, firefox, NWJS, etc. ) to be able to play it. Some environments do not support it because it is a patent encumbered format, notably NWJS. Most major browsers support it though.

If your using the desktop build of C3; it's based on NWJS. So you won't be able to preview your video in it, but it can still make games with mp4 videos in using it.

KENYONB if the app is crashing there's a good chance there's a bug in whatever action your using, could you open a bug report for me with your project?

I just need the logic pertaining to Google Play, you can remove the rest. Also you can remove the APP_ID's etc. as well. That way I can test for any bugs and let you know if there's a better way round to do it

Silviu Not a bad suggestion, but it normally takes me a little while to getting around to writing tutorials and it sounds like quite a time consuming one to write. I'll put it down on the to do list anyway.

No worries Tackla I'm glad I could help! I've updated the documentation to mention this. If you find any bugs please don't hesitate to open an issue on our bugtracker and I'll take a look for you.

Hi RetroDaddy can you please double check that the system webview is up to date in the Play Store app.

Hi Tackla,

sorry if you've been waiting a little while for a response, I don't spend much time on the forums.

I had a look through the source and there isn't a specific method for opening the top level leaderboard list. But by the looks of it, if you give a zero length string ( "" ) then it might display it. I haven't been able to confirm this, as I don't have a test project set up for this. I hope this helps. If that doesn't do it then we'll have to add the feature in.

If your curious, you can find the native code the method maps to here

fredriksthlm

So C3 will be able to use any keystore file. When you do a build via the build service it will ask you for a keystore file along with it's alias/key password/store password. We're avoiding storing the keystore itself within the editor. The hope being it will encourage users to put the file somewhere safe/secure and not just leave it in C3, trusting it will always be there. So no "import" is required.

If you want to the editor will also be able to generate new keystores for you. One limitation is that you will not be able to sign an existing APK, it will only work with builds.

Bootfit

The fee unlocks the ability to publish applications to the play store and allows you to use services like In App Billing and Play Games.

Google does not issue you with a certificate, and you don't need to give it to them. You create the certificate on your computer, use it to sign the APK and then give the signed APK to Google. The first time you upload an APK for a new application they read the signature in the APK and that signature is permanently associated with that application. To publish new versions of that application the signature must match the original one, so you need to use the same certificate every time. Once a APK has been signed it cannot be modified, or it will appear as tampered with and it will not be run.

To generate a keystore you need to use keytool which is part of the Java Development Kit ( JDK ). If you don't like using the command line you can use Android Studio to create a keystore for you.

There is a little bit of information on https://developer.android.com/studio/publish/app-signing.html#signing-manually about creating a keystore using keytool and signing an APK using the apksigner tool.

Bootfit you can sign APK files without android studio using either the apksigner or jarsigner command line tools. Android studio basically just wraps those tools to streamline the process. I believe there's more than one way to generate a signing certificate but the main one is using the command line tool keytool. I'm actually in the process of adding APK signing and keystore generation to C3, although it will only work with the build service not Phonegap Build. Although I believe Phonegap build might offer a service to sign your APK for you? It could be on one of the paid tiers though.

Incidentally you don't need a signing certificate to register as an Android developer, and unsigned debug APKs can be installed onto a phone without being a registered developer.

I understand people are finding some of the new requirements a pain, I would like to say that I also find them pretty tedious. Just so everyone is clear:

• APK files must be signed
• You must supply your SHA-1 certificate signature in the Google Play Developer Console
• The Google account you are testing with must be listed as a tester in the Google Play Developer Console

If any of these are not done, when login is called it will briefly show the Play Games dialog, then it will vanish. These 3 things are required by Google (not by us), and any application that wants to use the Play Games service on Android must fulfil them.

The reason why they were not previously required was because we used the Web API on all platforms, and the requirements are a lot slacker for the Web API. Unfortunately Google no longer allow you to use the web API within a WebView for security reasons.

There are currently no known issues with the plugin. If you are experiencing a bug that isn't a sign in related configuration error then please open an issue on our bug tracker and I will look into it ASAP.

That's fine, Apple and Google seem to go out of their way to make their services hard to integrate with!

Are you using C2 or C3?

If you attempt to close the tab or the browser during a save then a dialog will pop up and tell you that it's still saving. Are you not seeing this?

The browser doesn't allow web applications to save files in user space for security reasons. We could save a copy in the browser cache before sending it, but there's situations where that could fail and it also slows down saving. As users can choose to save to the browser I'm not convinced it would help that much.