Google play closed testing waiting time for changes published for ~ 2 hours is very looooong, who can give me google ceo mobile number to complain.
leads to indefinite loooooooopsupport.google.com
In our days, is easier to call Greece Primeminister ! ..or her Majesty Queen... from the other world !Google play closed testing waiting time for changes published for ~ 2 hours is very looooong, who can give me google ceo mobile number to complain.
I think you can call at Google -800- phone and tell them you are Elon Musk and you wanna buy them, then will give you the CEO for sure !So, I think calling POTUS is easier than google ceo!
DDoS calling attack@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!
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.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, private key changed, because it is changed by play store, and billing lib can't initiate new billing flow.
that is, no reverse!it does not give you the right to opt-in
Your app is signed by another Google Play key.What is the error you get?