I'm trying to deploy the app on the google play store, and I was wondering if I did that correctly. I have deployed the app as beta testing last week, and today I just uploaded to google play as production mode. I created new app bundle by running "flutter build appbundle" in my project, and put that generated file into the production track.
So far my google play console is something looks like this
On the picture #3, I can see the rollout history as full rollout, but in side of the production I can also see something says you have a release in produciton that hasn't been rolled out.
Does that mean I just need to wait the app reviewed? or deactivate previous app bundle and do something else?
That looks correct. I just recently deployed an app to Android and it took over a week, maybe 2. I also noticed that that view isn't the most clear and descriptive. If you go to the Dashboard view you'll see all your apps and see the Status column. It'll say Published when it's live.
Related
After a tiring 3.5 months I learned how to build and launch an app using Flutter and Android Studio. I tested in debug mode on various emulators and all worked well.
I then built the app bundle and uploaded on to Google Play Store as an internal release - again everything ran well.
I pushed this in to Production. After a week of waiting for a review, the app launched. I uninstalled the test version and installed the live production version - and that's when the problems started. The app began to crash in places it hadn't before. Namely on certain pages (and often after the render of certain pages the app closes after c.3 seconds) or upon button presses on certain pages.
I have now added Crashlytics to the app (which I didn't have before), and have pushed this as a second version on to the Google Play Store - and again it's pending review. The questions I have are:
Can I deactivate an app once it's live on the app store to prevent any more downloads? - Is there any code that can be added to the app to do this internally? I can not see any options or instructions within the Play Store. It seems a little crazy that I now know my app has 'bugs' which never materalised in test, but i can't 'switch it off'?
I have only been able to add Crashlytics this time for a new production release, and once installed and I can try and work out what the problem is with error logs. Once I have I will have to create a third version and again add as a new release and wait for Google to approve - is this really the most efficient way?
Why would or could a Production release of an app crash when the Debug version, or Production release version in Internal Test mode, did not? - I find it so strange that I have so many tools available and yet none detected a problem until launch
Thanks in advance!
you can unpublish your app from playstore
goto console>select your app>setup>advanced setting>unpublish app
this will stop your app from appearing to new users and getting new download from
playstore
2.fixing bugs always need a new release to update your app there is no way to get around
uploading a new release and waiting for the review to end (this is for production app)
3.your testing might not have encountered any bugs because you might be testing on one
device or emulator with a specific api for example api 30 ,and the bugs are being
detected on other apis or device properties you haven't covered in your testing
I have deployed a flutter app on the google play as a production mode, which is this link, https://play.google.com/store/apps/details?id=yurikanamba.lovealapp
(sorry the social login doesn't work now)
I can see the latest update from the link, like screenshots, but I can still see the word (beta) right next to the app name like this.
I sent this link to some of my friends, but they cannot see the (beta) like I do.
Do you know why I can see that and how to get rid of the (beta) right next to the app name?
I guess I should disable the Beta project in our App releases on google console, but there is nothing I can deactivate my beta release...
I have got the same problem:
First I published my app as a public beta version then I released it to production track. However, when using my developer profile I'm still seeing this Beta title.
I have a tried to unregister from testers list, then cleared my browser cache (desktop and mobile), my Google cache but I'm still seeing it.
Try this anyway, it might work for you.
The only solution I found is to use another account that was not listed as beta tester, but it seems that for profiles who have been (or still are) beta testers, "Beta" won't go away from your app title.
I have been using google actions with actions sdk and most of the functionality seems to work. However, I am facing consistent issues across a few alpha test users on the updates to the application.
I notice that the latest deployed to the cloud function is what seems to run on the Simulator but an old version appears when viewing on a phone. For example, the icon that I set in the images directory is just not showing (even after 2 days) on my phone while the latest appears in the Simulator. The same with some images from Cloud storage. I tried clearing the cache and storage from the Assistant app on my android phone. Yet the problem persists.
Is there some setting or disabling of cache that needs to be specified in the NodeJS based client code or in the actions console? Thanks.
Go to the Test tab and click on the Reset Test option, such as in the screenshot. It should work.
I have followed the steps given in http://developer.samsung.com/tv/develop/legacy-platform-library/art00121/index, and the application appears on the Smart Hub on the TV. However, when I make some changes in the application, and package it again selecting "Update the packaged files on the server", do a "Apps Sync" and run the application, the updates are not reflected.
I have tried changing the application name and version in config.xml. Only the application name changes in smart hub, but the application when opened is what was installed the first time on the TV.
If a new project is made and the same steps are followed, the new application appears on the smart hub, but an update to it has the same problem.
Am I missing something while packaging the same application for a second time?
Not sure if this is useful but I believe the device seems to cache the files. I had the same issue today and was quite frustrating.
I managed to find two solutions:
1) shut down the device and re-launch again (connect to server and the Apps Sync)
2) when you export the app in the IDE, make sure you name the package name differently + title & description need to be different too.
By doing this, Apps Sync will add another app (so you'll have two of the same app, but just click on the last one that appears in the apps list - hope that makes sense). If you want to remove the apps, simply access the widgetlist.xml which will be in the root of your server and then remove the apps references from there.
I hope that helps.
I used to test my Chrome Apps by following these instructions:
https://developers.google.com/chrome/web-store/docs/publish
Now, when I upload a new app for testing, the Publish to Test Accounts button is gone, and it seems to be replaced by a set of radio buttons, one of which is "Trusted Testers", and a single Publish button. When I publish that way, the app gets into a Pending Review state, and stays there (for over a day). It seems as though I've requested it be published for real, which I guess requires a review, but I only want to test it.
A month or so ago when I did this is became available for testing in minutes.
Has anyone successfully this week published an app for testing only?
UPDATE: To get along with my development, I took an app Published to Testers a few weeks ago, and updated it with a completely unrelated app that I'm working on now. It appeared as Published to Testers within a few minutes. So, I am able to reuse this "container" for testing various apps. But, I am unable to publish anything new to testers.
This turned out to be temporary. A day later, publishing became responsibe again, with a quick response.