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
Related
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.
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.
We have submitted an update version of our existing applications in the App Store recently. But we have received a issue from one of the users, saying that the app is not functioning properly after the update. So in order to replicate the same, what are the steps to reproduce, so that i can analyse the issue?
Any help will be appreciated.
To simulate this before pushing yoru updated version to the AppStore you can:
Download the old version of your app from the appstore
Run the updated version of your app from XCode on the same device.
What will happen behind the scenes is that your app will be updated in a way similar to the Appstore. Your app will be partially updated while your doucments folder will stay the same. (what usually causes problems)
This solution is better because it lets you check for problems before and update was pushed to the Appstore.
Yeah, I get this a lot. The solution is a bit annoying, but you need to keep a history of IPAs you've submitted so you can put the on your phone through iTunes (so not the simulator) and then, run your code on your device putting a breakpoint on your applicationDidFinishLaunching handler in your app delegate, and start tracing from there. You should be able to find the old app store version in your organiser from the last time you submitted, or, go through your SVN/GIT history and checkout the version tagged to your release version.
Many times in the past that has happened to me where I test a new revision and everything looks fine but when I submit an update and is approved, users start complaining about a crash or lost data.
This is way I approach the problem.
(This is most important step) You need to either have your old code or old binary installed on your actual apple device. (Physical iPhone / iPad)
Now go to iTunes and install your new update.
Attach your physical iPhone / iPad to you computer, Launch Xcode and start debugging it.
NOTE: There have been many times when things work perfectly in the Simulator but break on the actual device. Its always important to test your code on the real thing as that is what the users are going to be on.
All that is required is to have the version of the app that is in the app store on your device, then install the updated version to your device. You can debug it using Xcode when you install the new version.
I am developing an iOS (5.0+) app, which works very fine on 6 different devices in our company.
When we send the build to the customer, they report they have tested it on 5 different devices and the app is always crashing right after launch.
I have integrated TestFlight and Flurry SDKs to track usage and problems.
The strange thing is that no crashes are reported from both TestFlight and Flurry.
I have adviced the customer to remove the provisioning profiles and try to install everything from scratch, which did not produce different results.
The app is in the App Store, approved from the first try.
It is even stranger that the customer reports crashing when installing a TestFlight build and installing from the App Store.
Is the app going to be approved in the App Store if it crashes right after launch?
Any ideas on how to remotely debug the app or how to proceed in this case?
Thanks and happy holidays!
One option is to ensure your logging and get the crash logs. This Apple documentation shows how to get the logs both with and without Xcode available:
http://developer.apple.com/library/ios/#qa/qa1747/_index.html
After you get the logs, here's documentation on how to read and analyze:
http://developer.apple.com/library/ios/#technotes/tn2151/_index.html
The problem has been resolved by adding both German and English localization to the project settings and having 2 storyboards for each language. Big up #RoboticCat!
Some days back i had few problems regarding the version updates from iOS 4.0 to 6.0 . The entire database was cleaned when the new version was installed .
Is there any way I can test version update before submitting to apple ?
I tested version updates via
Hockey
AdHoc build installed via iPhone configuration utility.
Is there any other way i can test the things so i can be sure that the update will not have any problems?
You can test it via TestFlight service. It's a great tool and I use it often to test my updates.
On a fresh phone (or a phone that does not have your app on it), download the current version of the app from the App Store. Setup all the necessary data, create values in your database, etc. Then update your app in the phone via adhoc release or TestFlight. The key point is to have the most up-to-date public version of your app first.
Try out Crashlytics. It provides instant and detailed crash reports, right down the line # at which a problem occurred.
It negligible in size (a few hundred KB), but even works on release distributions! That means even if you miss a few bugs, you will be notified instantly the moment a crash occurs, rather than having to wait for the useless Apple Crash Reports to be published.
Hope that helps you out a bit.