We released an app on the Open/Beta test Track on Google Play and need to know if the build will expire so we can upload a new build. I've looked at a lot of Google Play Console documentation and around the web and I can't find anything that confirms whether there is an expiration timeline or not, and what it is.
*Apple has a 90 day expiration on TestFlight so we think there is a good chance Google Play has an expiration too.
To this day, there is no expiration for the artifacts published on the Play Console, on any track. You can leave your artifacts on a beta track forever if you want.
You publish a new version on that track them by uploading a version with a higher versionCode.
Hope that helps.
Related
I'm using Google Play Store to distribute an app.
For a certain issue, I would like to install an OLDER version of my app to one of the client's device.
I'm struggling to do so, is there any way to do that?
No matter how and which "testing" method I apply, Google Play automatically shows the HIGHEST version of the app which is the "release" version ignoring the old test versions.
Creating an APK would be NO way because I need Google Play's own signature in the apk to make things work (to test the things we would like to)
Is there any way at all to distribute my OLDER app version from Google Play store?
(By the way Google's testing methods are inexpressibly unusable even apart from this problem. You never see what really happens, you cannot really manage the testing channels the GUI is miserable the notification email is late the testing is slow and painful you don't see the version number in the Google Play Store, there are like 3 methods to do so and the difference between them is not self explaining, I give 1 start to the developers who made these parts of Google Play I hope they read this.)
Thanks in advance.
From Google Play Console go to App bundle explorer
Then choose the version you want to install
Go to Downloads tab
click on Copy sharable link
install it from you device using this link
Note: the device's Google Play account should be an internal tester and enable internal testing from Google Play on this device.
So I just spent all weekend debugging and building an app for my client. I don't have my 100 dollar Apple Developer License anymore, so I can't upload it. I thought my signature would just be under my client's team automatically after they added me, but I guess not.
How can I sign the app as my client's team, so they have it, and I can upload to their dashboard?
I can't seem to be able to Google the right thing to find an answer.
Oh, and secondary question; could I just get the team license under my name to sign it, so I don't have to re-achieve it again? Not a huge deal if I have to wait again, but it would save me some time.
Edit: I did also directly ask Apple's support team, but I figured I would ask this here incase a fellow dev had an answer for me. I can't be the only freelancer who's had to build and push an app for a client. Cheers!
I just published an app on the playstore, but I published it on Production track and I wanted it to be on Closed tracks for now, in alpha version so that it would only be downloaded by testers.
Is there an option that allows me to disable the Production track and later put it into production?
Thank you.
About 5 days ago my app passed 570 downloads but my badge still shows 100 downloads on google play, Isn't 5 days too long to update these stats?
They are supposed to update every 24 hours., stats which is displayed in developer console is not reliable, they often stop updating for few days.
I'd suggest you to integrate Google Analytics for Mobile, localitics or any other framework if you want good statistics.
I had the same problem recently so I contacted Google Play developers support and they clarified the issue.
As it turned out, the number shown in Developer's console statistics "New users acquired" and on the "Installs" badge in Google Play are computed using different algorithms. The first one shows raw installs while the second one shows the somehow corrected data. In particular, install metrics may be discounted or even removed entirely if Google detects fraudulent installs.
When developing online game I would really like to avoid supporting different protocol versions. The server can check the version of a client and deny login until the client gets updated. But the problem here is that I need the app update to become available simultanously at the same time on AppStore and Google Play.
Is it possible to do? How do you solve such versioning problems?
Well, I am not sure how it works for the GooglePlayStore but if you choose Developer Release instead of automatic then you could just release it in the moment it approves on the GooglePlayStore and about 30mins. later your iOS app will be online and available as well. That's what I'd do.