I have published an app in play store for alpha testing in which I have uploaded an another version where I could not get any updates message stating that a new version is available. I would like to know does the app update feature will work while the app is in alpha testing.
I think this documenation can help you, is stated here that if you want to run multiple tests on the same app, keep the following in mind:
It recommend you to set up one test as a closed alpha and another as an open beta. This works because you can run one test at a time per testing method (e.g. open & closed).
If you run an open alpha test, you can't use the open or closed beta track. This happens because you can't run two open tests simultaneously or run a closed beta given version code requirements.
For more information, you can also check the documentaion of Test and Publishing Game Changes of Google.
Related
I recently published an application to production mode on the play-store, the app status has changed from review to open testing, what does this mean? Might I have selected an option by mistake or it is a normal term as am meeting it for the first time.
Image
Internal testing: The app is not visible to the general public on Google Play. The app is only available to a list of people you manually set - you add their emails, and they get an invitation.
Closed testing: Same as Internal testing (not publicly visible, has an allow-list), but you get a Google report. Google will test your app and give you feedback.
Open testing: Visible to the general public on Google Play, but with a "Pre-release" warning. People can review the app, but the reviews are only visible to you.
Production: Visible to the general public. User reviews are public.
The workflow I use is:
I set the app as Internal testing (even if it is just my email address) . Right after doing this I
Promote the app to "Close testing" (even if it is just my email address) - so I can get Google's report right away.
After getting Google's report and fixing what they suggest (or ignoring it), I promote the app to production.
The reason why I jump from internal to closed testing is because I want Google's report right away. I do internal testings outside Google Play (I develop with React Native and Expo - and I use Expo for internal testings). So, the moment I submit the app it is already internally tested.
I also go straight from "closed testing" to "production" because my apps have a small audience, and I'm okay with public feedback. But if you are afraid you app may have bugs and it can hinder the app reputation with bad reviews, do the "open testing" first.
There's some testing type.
I hope you may know what production is. Production means when an application is completely ready for every device.
What's the difference between an internal, closed, and open test?
You can create releases on three testing tracks before you release
your app to production. Each phase of testing helps you gather the
feedback you need to make improvements to your app throughout its
development.
Internal testing: Create an internal testing release to quickly
distribute your app to up to 100 testers for initial quality assurance
checks. We recommend running an internal test before releasing your
app to the closed or open tracks. If needed, you can run internal
tests concurrently with closed and open tests for different versions
of your app.
Tip: You can also use internal testing to test apps that are not fully
configured (see below). Closed testing: Create a closed testing
release to test pre-release versions of your app with a wider set of
testers to gather more targeted feedback. Once you've tested with a
smaller group of colleagues or trusted users, you can expand your test
to an open release. On your Closed testing page, an alpha track will
be available as your initial closed test. If needed, you can also
create and name additional closed tracks.
If you're testing an existing app that you've published before, only
users in your test group will receive an update for your closed
version.
Open testing: Create an open testing release to run a test with a
large group and surface your app's test version on Google Play. If you
run an open test, anyone can join your testing program and submit
private feedback to you. Before choosing this option, make sure your
app and store listing is ready to be visible on Google Play.
Copied from google support.
Easy way : Open testing
Pre-launch reports
Spot issues before they affect your users. Test on a range of Android
devices to learn more about your app's stability, performance, accessibility, and more.
Here's another beautiful question with answer
I have an Android app that is currently on an Internal Test Track (Version 1). I am trying to upload a new version (Version 2), but I want my current users to still test Version 1.
The console will not let me retain Version 1.
Is there a way I can have user Group A test Version 1 and user Group B test Version 2?
I did try using an Internal Test and Alpha test. But the Alpha version was downloaded to both groups even when only a single group was selected for it.
All the explanations are on this help page
Summary:
you can only have one internal test
you can have multiple closed tests, but users need to opt-in
It sounds like you want to have version 1 on a (new) closed track and will need to get your existing users to opt-in to that, and rmeove them from the internal test
Then have version 2 on a new internal test track that targets group B.
The other option would not be to have an internal test track at all, and have two closed test tracks, one for Group A, and one for Group B.
Internal test tracks are normally for very quick release for developers or immediate QA within your own company. Closed test tracks are usually trusted testers, or for people within your company not necessarily within the development team who can wait a little bit for the rollout to complete.
This isn't really a whole answer to your problem, but I have figured out that you can send people links to download a certain version of the app with 'Internal App Sharing' on the Google Play Console.
So yeah, set up 'Internal App Sharing'. (Sorry, I'm too lazy to write up steps on how to do that.)
After I set that up, when I use the 'App bundle explorer' to observe an apk or app bundle, there is a Downloads tab:
And I copied that shareable link and sent it to my phone. And then I opened that shareable link on my phone. I had to enable internal app sharing in my google play store settings (look this up because it's not obvious how to do it) on my phone. And then the link sent me to a page where I could download that specific version.
Not sure if this type of thing could be used to solve your problem but it's worth a shot.
I've recently released an Alpha build of my app via Google Play Console (as I've done many times in the past). This is a closed testing build and I've opted in with my device/account via the URL console provides.
There is an existing production version of the app.
I waited a little while then went to PlayStore app to download the update.
Strange thing is, the version shown in PlayStore is updated (to the one used by my Alpha build) but there is no option to 'Update', only the option to Open the already installed (older) production version I have installed on my phone.
Has anyone seen this before? Could it just be Google are still in the process of rolling out my Alpha build?
Update
I've waited over 12 hours now since upload to console
I've tried clearing the cache on the PlayStore app to see if the update option appears but it didn't.
Update 2
I've got the update to work but in a very convoluted way. I had to:
Open the 'download' link on the testing opt-in page using Chrome (not PlayStore)
Click 'Buy' (not Update) and let it install
The result is though that it didn't seem to update the app, rather overwrite it. As a result a migration routine I had in the new app to pull over old data didn't run and my previous app data was lost (this is a separate issue though).
It does sound like something is wrong with my PlayStore app but what!?
This is weird. This sounds like you changed package name (essentially released a new app) rather than just release a new Alpha.
if I run a open beta test for payable app in google play store, what happens if I close the beta test. Will the users still be able to use the app forever ?
Situation:
1. I open my App for open beta test
2. USER A finds the app in GooglePLay for betatesting (Thats I guess, not sure how it works really )
3. After while I close the betatest phase.
4. Will USER A still be able to use the app ?
I read somewhere in documentation they go back to the available public version and cant re-enroll as an open beta tester until the next public release is shipped live.
If you close the open beta testing and move on to some other type of testing like closed beta testing or alpha testing, the user (if not mentioned as a tester in the closed beta testing or alpha testing) will be able to use your app but will not be able to make any purchases.
Hope this is what you were looking for :)
You have 1.1 version app already developed and is released in market & you are about to send update(release new version 1.2 ) in Play store/itunes with some critical functional changes.
What are the ways do you follow to simulate situation like real time App Update that happen in Play store/itunes? How do you test that?
Common things which i cross checked before :
Android
Ios
Sample Scenario :
I'm trying to trace down a database upgrade bug and need to figure out a
way of simulating market upgrades.
You can actually release into Play store as alpha and/or beta and test upgrade this way. It's best as it's a real upgrade from the store, nothing simulated.
You can read more here: https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
EDIT
You can also try something like that: have a copy of the code of the previous version. Upload it to a test device. Then upload the new code, this will force a database update which you will be able to debug.