You certainly have humor. Google is the 2nd-place champion of client torturing after Apple. And when you will try to contact them you will discover a maze of links that leed you to loops and no phones at all. It is logical though if Android covers almost 80% of mobile phones' operating systems who would they serve first? You 'd better start with support.google.com and... good luck!!!
Some debugging such as billing flow, need app to be published firstly then test, if not success as your workflow, you'll change & republish again, so the interval between each debug takes > 2 hours, this is catastrophic!
@Hamied Abou Hulaikah ..hmmm according those data... you must create an app with "Timer" every 01:59:59 ending session but before this... loop every "ms" with calling their -800- toll free numbers using unknown number... so... sometime they will change the way managing their incoming calls !
but for serious... I think sending/replying with an email (at a ticket) after "reporting" a problem at any Google Page you will have an answer in 2 weeks
@Hamied Abou Hulaikah ..hmmm according those data... you must create an app with "Timer" every 01:59:59 ending session but before this... loop every "ms" with calling their -800- toll free numbers using unknown number... so... sometime they will change the way managing their incoming calls !
Some debugging such as billing flow, need app to be published firstly then test, if not success as your workflow, you'll change & republish again, so the interval between each debug takes > 2 hours, this is catastrophic!
This is not correct. I am suspecting you have missunderstood something. When you upload an app with closed testing and gets published there, then you can compile and try endless times as long as you don't change the version of the app in B4A. You are not obliged to post each time the new compilation.
This is not correct. I am suspecting you have missunderstood something. When you upload an app with closed testing and gets published there, then you can compile and try endless times as long as you don't change the version of the app in B4A. You are not obliged to post each time the new compilation.
No, in my case if I recompiled app, even version not changed, sign key changed, because it is changed by play store, and billing lib can't initiate new billing flow.
No, in my case if I recompiled app, even version not changed, private key changed, because it is changed by play store, and billing lib can't initiate new billing flow.
I do not understand. I have done it several times and it works this way. All you have to do as described in @Erel 's tutorial, you can upload the app even not completed and recompile endless times with the same version. I am talking about In app purchases here. I hope I am not the one that has missunderstood you. Are you talking about a different thing? Does your app have any special capabilities?
I am using GooglePlayBilling lib latest update, I think my problem because when I created the app on store I checked using play store signing key, I think it replaced my own key, so when published, it signed by google play key not mine, so if I recompile app again (in this case it use my own key) & test it direct with billing service, it will failed!
Good morning everyone, I am developing a new app and I noticed there is a problem to use it. Trying the in app purchases I keep getting in the "Test card, always approved" the "Item unavailable in your country". All subscriptions are set as available in my country as well as the app. I searched...