We made a purchase - a real product using a test account, we did not use one of the android test ids. The Google Popup box appeared as normal, we entered our password as normal, and got the "this is a test purchase you will not be charged etc" message. When we pressed ok, the application crashed and stopped responding with this error dialog:
"Sorry. The application Game-Name(process com.HappyBuddhaGamesCWW.PKG3) has stopped unexpectedly. Try again."
So the next time I run the same app, it crashes with the same error almost immediately upon starting the app. If I CHANGE the package name and resubmit to a new APK slot on Google Play Developer, then the app runs just fine as long as I don't press the IAP button to purchase again.
Another answered question suggested this was a licensing issue, but I do not use Eclipse, I use Game Maker Studio. I too suspect this is some kind of licensing thing, but I don't know exactly where to look.
Any help, pointers or suggestions would be GREATLY appreciated.
The problem was my Google Play License. It were munged in my GameMaker Global Game Settings/In App Purchases/Google Play Public Key window. When I replaced it properly, with no spaces, all was well.
Related
I just finished the first version of my react native app and I've uploaded it to the google play store for open testing. However, I can't get a public link that anyone can download the app from to work.
I have used internal testing, closed testing and they both work ONLY IF I have testers added by email to my list.
The two links that are available from under the testers bar in Open Testing are "Join on android"
https://play.google.com/store/apps/details?id=com.(Myapppname)
as well as "Join on the Web"
https://play.google.com/apps/testing/com.(Myappname).
The first link ONLY works if I am logged on to my main account (it shows "We're sorry, link is unavailable...etc)
and the second link says that the app doesn't exist or I am not added as a tester - but open testing should work without me manually adding new testers right?
I would very much appreciate any help on this.
Extra info:
App is "under review"
App has been uploaded today morning (been 9 hrs+ since uploading).
probably the open testing version is under review.
you can check this out from Google Play console, from "Releases overview" in left menu.
just wait (it may take couple of days) and then it will work just fine.
Today I added my first application to play google stores. Send your application went smoothly. The application was in store. But as I want to download this application pops up an alert: Authentication is required. Sign in with your Google Account. I might also add that I am logged into your Google account, and checking whether the application runs on several other phones. But unfortunately, the situation repeated itself. Very Please help.
I had the same problem and how to fix it is very simple just go to your apps description and update it with anything I just added one word clicked update and an hour later worked perfectly
I cant comment as I am a new user.
But it seems its an issue with the Google Play, as every one is facing the same issue.
I got 7 apps uploaded yesterday and none of them are working. I have retried to upload again today, and waiting to see the outcome.
Let me know if your apps are working fine now or if any updates on this.
I created a licence test app a year ago that was identical to the sample licence test, added the key and uploaded as draft. It worked exactly as it should. Now when I run the exact same app I get an application error 3 message every time. I am using the exact same device and the exact same account so nothing at all has changed whatsoever, so why is it now not working? I have a new app ready for market but I need to resolve this problem so I can test the LVL on the new app (which has the same application error response problem
The conditions of the LVL has just changed. Now, You have to give Your app a Beta Test status to get it work. On the developer console, select Your app, select APK, and then put it into the Beta Status. It needs a time to change, 24 hours is not unusual.
I have created a test build of a GDK Glass app that I want to deliver to a few test users. However the app disappears after a reboot. Logcat shows this:
08-19 18:18:18.256: I/GlasswareSyncAdapter(978): Uninstalling Glassware ID #6DBADA7634397F00 (com.example.demo).
A look at the issue tracker explains that this is caused due to the fact that the MyGlass app didn't install this app and that the app thus isn't linked to the user's account.
Are there any workarounds? With a submission process of over a month how can we get our app tested properly?
The submission process should be less than a month at this point. I suggest that once you think you have things working, you submit the app.
Once submitted, you'll be working with the Review Process Team. They are able to create a whitelist (certainly of accounts, and possibly based on a list you can control through a Google Group) of who will be able to see the app on their MyGlass page. This will also allow you to test the app, including the auth flow, using the actual installation process.
It seems like this issue only occurs when the application you are side loading has been submitted to Google for approval. Just change change the package name of the APK you want to sideload and your problem should be solved.
Recently I've been trying to get my Adobe Air AS3 Android game to work with Google Play Game Services.
I'm using the Milkman Native Extension and Flashdevelop.
I made my own sign in button, and when I press it the standard "Sign in with your account" window with all my accounts appears. The first time I sign in with an account it even gives me the standard options to share my game status to my Google+ circles. Then, when I do try to log in, the service shows the standard spinning progress wheel, then disappears, the "Signed in as PLAYER" box doesn't show up, and I'm not logged in. The ANE tells me that it's an unknown_error_code.
Things I've noticed:
It doesn't let me see a list of achievements or leaderboards either.
After the first time I log in it just tries
to log me in again indefinitely.
The "Apps using google+ data" shows it as a "3rd party app" and not the actual title of the app. EDIT: It now displays it as the correct app for some reason. Still doesn't sign me in though...
I'm pretty sure this isn't a coding problem.
Things I've tried:
Matching the SHA1 key with the SHA1 key from my p12 key.
Logging into different accounts.
Making my accounts tester accounts.
Using non tester accounts.
Making new Game Service pages
Making new application pages
Changing my app I.D. (com.blank.mygame)
Clearing the "Apps using google+ data"
Making the Version Number of the game higher than the most recent test account
Making new Google+ accounts
Syncing my app to the services page.
Desyncing my app from the services page.
Making new OAuth 2.0 client I.D.s.
Publishing the game services.
Any suggestions?
Now I can answer my question officially:
I fixed it.
Apparently if you go to the API console and change the Oauth from there the game services doesn't detect it. I originally put in the wrong SHA1 and fixed it through the API and not the google services developer console.
http://www.youtube.com/watch?v=nkJS_W-VC9I (it's problem #6 which is really n)
I was having the same problem, and I solved it by changing the App/Package ID at the Google Developer Console from:
com.developer.appname
to:
air.com.developer.appname
I had simliar issue - the app was asking for permition, but it triggered onSignInFailed event.
Tried several things, the problem was with runtime enviroment - everything works correctly when I include it to application. (I was using separate AIR runtime enviroment to decrease the time of publishing the app)