I'm developing a game as a Chrome Packaged App and I want to use Google Play Games for the leaderboards, but it's turning into a little bit of a process.
I'm having trouble getting the Chrome Packaged App to authenticate with Google Play Games.
I've got most of it nailed down:
I've created a game in the Google Play Developer Console
I pretty quickly got everything working by uploading the game to my server and going to Linked Apps and creating a Web App entry. Leaderboards, achievements and everything works great.
I followed the All-The-Stars-JS example to get everything into the package so gapi.auth.authorize() can work within the packaged app... but using the call returns "OAuth2 request failed: Service responded with error: 'bad client id: NON_NATIVE'"
This makes sense-- the OAUTH2 Client ID from the Linked App manager is expecting a web app. There isn't a way to create a Linked App for the Chrome Packaged App so I created one using the Google API Console as the example suggested. This gets me authenticated!
Now, when I try to pull a list of leaderboards I get a response: "There is no linked app associated with this client ID."
Right, that makes sense because I created Client ID manually in the Google API Console and there's probably no "link" to Google Play Games... but I can't link it to the Google Play Games service manually, and there's no way to just link a Chrome Packaged App from the Google Play Developer Console. Am I missing something?? I've been chasing this issue for months!
Thanks in advance to anyone who can help!
#Brian I think you are doing everything correctly. Currently there is not a way (that I'm aware of) to link a Chrome packaged app to Play Game Services. The reason you are able to get authenticated but not see Leaderboards is that you created the Client ID through Google Developer Console, which does not create the necessary entries in the Games back-end.
I will report your experience to the Play Game Services team, maybe this is something we could support in the future.
Related
Have recently started using Flutter and so can deploy apps to Google Play as well as to Apples App Store. When I want to put an app out for internal test though I am finding some difficulties. With The App Store I can make internal tests for up to 25 users immediately (it doesn't have to be reviewed). However Google Play's Internal test channel still requires a review (which has taken 6 days recently). Is there any offering in Google Play that I can use deploy quicker to my Android users?
Thanks for any advice
Your first upload must be approved. After that they are automatic.
I accidentially moved to the new Actions on Google dashboard. Since then my project does not really work anymore.
I changed the json structure and uploaded a new version that is now running fine on the simulator.
Unfortunately, my Google Home device is not recognizing that such an action exists. This was working before when using the old actions on google api.
Ciao
Fabio
The invocation name has changed when testing apps on the Google Home device.
You should now say
Talk to my test app
I'm new to Bluemix but I've seen on several videos some folks easily using Bluemix to create their app screen just dropping whatever they find useful on it. But I logged on and I looked everywhere for this page and I can't find it. Does anyone knows how to get there?This image shows the place where I want to go.
Thank you all!
Mobile App Builder is no longer integrated into the Bluemix Developer Experience. It's been replaced with starter apps that allow users to get started quickly integrating Watson and other Bluemix services into their projects.
If you would like access to the legacy App Builder tools, they are available here.
I had implemented leaderboard in google play store console. But after implementing when I see the play store console it shows:
One or more APIs that are required for game services to work have been turned off in the API console. We recommend to turn them on again to ensure your game is working properly.
Also the leaderboard not working.
I had this same issue, and when I clicked the Turn APIs button back on, it would show the error again after a page refresh.
I got in contact with Google and they said that a few other developers were experiencing this issue and that they would email me back once they had made progress finding out what's wrong
Now then - because this all happened around the time I was re-linking a project into Google Play Games Services, I thought I had messed something up. Being restless I decided just now to create a new keystore file, and generate a fresh SHA-1 fingerprint. I was able to enter the newly generated code on the API Manager console, under the Credentials tab.
For some reason, it worked; I am now able to sign via Google and access the high-scores page.
Might be worth a try?
I have an iOS app that uses the Google Docs List API to access and download spreadsheet data. I've done a basic test with upgrading my Google Docs account to Google Drive, and everything still seems to be working okay.
Based on the answer for this question Google Document List API and Google Drive SDK it looks like things will continue to work for awhile.
Are there any steps that mobile devs should be taking now to move to the new API? My main concern is that most of the developer docs so far are related to web apps and not mobile apps so requirements like registering for the chrome web store don't seem to fit. For example:
"Warning: Apps will not have any API access to files unless the app has been installed in Chrome Web Store. To test an app during development, you must first create a listing and install it."
Any guidance or suggestions would be appreciated.
Check this answer for the rationale behind the Chrome Web Store installation: https://stackoverflow.com/a/10476737/186674
Also, we are considering removing the installation requirement for the development and testing phase, we should have some updates soon.
iOS apps using the Documents List API should now update to using the Google Drive API and the newer Google APIs Client Library for Objective-C.
The new API and library are quite a bit easier to use and more efficient than are the older GData alternatives.