Google play error: authentication required

Ok Rob, i zipped the project’s files. You can find them here:

http://www.filedropper.com/myapp

thank you for your help.

Yes i saw many native developers ran into some sort of the same problem, but their error was temporary for some reason, due to google play publishing time, or they forgot to publish an alpha version of their app or something like that.

Say is there a chance that the problem lies whithin the build itself? i mean , does building in corona has any dependency on the java/android sdk/adk that is intalled on my computer?

Another thought would be, can there be a problem with my keystore file?

It’s always possible that it could be your keystore or an issue with the build like licensing, keys and such.

EDIT:  I can’t deal with a .RAR file.  Please use .zip.

Rob

Ok, here is the zip version:

http://www.filedropper.com/showdownload.php/myapp_1

I didn’t see anything obviously wrong with your code.  You do things a bit differently that I would, as I tend to put all my IAP initialization in main.lua and then have my purchase button do its work.  I can’t really test your code.  But what I did is take a game of mine that’s in development that has Google IAP v3 in it to see if there is an issue with the plugin.  My code worked as expected, so the plugin is functioning as expected.

This leaves either a setup circumstance with what’s on your Google Play account, or perhaps a keystore issue, or you’re running an older version code on your device than what Google Play expects.   I would suggest that just for fun you also try a test account and not your developer account.  Add some more print statements in and watch your “adb logcat”.  I know it will be noisy, but your looking for Corona messages and Finsky messages.

I’m curious at what point your getting that message.

Thanks, I will try doing so, do you also use google ‘licensing’? or do you just use their key to verify purchases?

I will be posting once I have somthing

Say Rob, can this error occur if for some reason java updated its version and corona is not using the 6th version anymore?

I suppose there is an outside chance this could happen, but I don’t think this is the issue.  If anything, your app wouldn’t install since the main impact is signing.  I’ll ask engineering about it.

Rob

Thanks, I appreciate it.

Ok, at last i manage to overcome this THING.

Rob, thanks for the help and sorry for the troubles, it was quite one of those things that are just easily overlooked, and it was

really a stupid thing of me to do so too. 

When adding items as an in-app purchases, I inserted only the id itself as the name of it, not including the package’s name.

Meaning I wrote “fullversion” instead of “com.mydomain.myapp.fullversion”.

I only realized it a moment ago after checking up on my former app i uploaded a year ago.

I do need to add one or two things:

-when trying to buy your own products the error given should be “the publisher can not make purchases~” and not “Authentication is required…” (I think it’s important to notice that different)

-for other people who are having same error it is important to notice, most of the time it can be fixed by making sure:

       * to PUBLISH your app in an alpha mode.

       * to put the license given by the google developer console inside the config.lua, and insert the right permissions in build.settings.

       * to be patient. It takes several hours from when you publish your alpha version until everything is updated on googles servers.

       * to set all in-app purchases to “active” in the developer console, and write the exact FULL name of each of them.

-when checking errors on the ‘adb logcat’ we tend to think that many of the errors we see on the log are connected to the problem. well… they are not. almost 99% of them has nothing to do with the error. so it is very confusing, so try looking at your own code and upload to the console.

Again Rob, thank you for your time, very much appreciated.