I'm working on collecting logs for my application. I didn't see it in ChromeOS 64 release channel. But I saw there is a "collect errors" button at the bottom of applications in chrome://extensions on ChromeOS 65 dev channel. What it stranger is that according to How to clear error list of chrome app? this seems existed 3 years before.
So I'd like to know if the collect errors feature is released or will be released in future?
Thanks,
Allisa
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
ApiRTC
we have a consultation app and below are the issues we are facing
-iPhone to android
android to android
When the call is ended during the running session, and when the caller tries to call again Application hanged and the screen turned to black when trying to call again the caller side is giving a ringing tone but the callee is not receiving the call
The caller had to close the application and reopen it again then the call will go through
On android 10
When the call is ended during the running session, and when the caller tries to call again Application hanged and Chat is erased.
There were some improvements made recently around webrtc support by different OS web-browsers you are mentioning. Theses shall fix the issues you are describing.
Also the most recent versions of Ionic, with usage of capacitor, have fixed a few issues we were facing.
We have a blog post on the subject (https://apirtc.com/building-a-webrtc-mobile-app-with-ionic/) that does not show issues you are mentioning, please give it a try !
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.
When I view the device log in Visual Studio when trying to debug my app which runs in the background (so no normal debugging is available) I get empty messages.
I am using Debug.WriteLine with the defaul System.Diagnostics, no custom stuff whatsoever. Tried restarting everything, but that didn't help. It does hit the lines because the code is executed and I see the empty message lines so it is partially working but the most important info is not visible.
It works fine on an iPhone 4S (iOS 9) but since today I'm using an iPhone SE (iOS 10) and the message is empty.
Doesn't make life easier not being able to debug and not being able to view the debug text :(
Any idea anyone?
Cheers,
Rob
screenshot
So yes, this does appear to be a bug in Xamarin.iOS. Bug filed:
https://bugzilla.xamarin.com/show_bug.cgi?id=52308
This is a regression in the latest Stable and Alpha/Beta releases (works as expected in the last stable release, Xam.iOS 10.2.1.5)
Xamarin engineers will now discuss this issue on the bug report. If you would like to receive a notification when the bug is updated, you can add yourself to the CC list for the bug. Please note that you will need to create an account on that system if you have not already done so.
I have a Chrome app that runs on a few dozen devices in auto-boot kiosk mode.
I've pushed several updates to the web store, and while I do see the update on my local Chromebox after a little bit of waiting, I've come to learn that the many devices running it in kiosk mode are on an array of older versions. Some seem to have updated at some point in time, but many have not, and none are on the latest version that's already several days old.
Is this because they are in kiosk mode? I found this question over on the product forums, but it has no answer. Seems like the behavior I'm experiencing, and if so I could see why this is the case. Still, all of the documentation from Google pertaining to apps suggests they should always be auto-updating themselves.
We had this same issue and luckily have a support agreement with Google. After some log searching, we were able to determine that the kiosk app we were deploying was specifying a kiosk required_platform_version, eg.
"kiosk": {
"required_platform_version": "11021.56.0"
},
While our Chrome devices (ASUS Chromebit in this case) were already beyond the required version specified. As Chrome won't downgrade itself, the new version in the Chrome Web Store is deemed ineligible for this device and upgrades are never applied.
To resolve this issue, we posted a new version of our Kiosk app with this value updated to match the currently highest deployed Chrome platform version in our fleet (you could also just remove it - but for long running Kiosk apps it's best practice to lock the Chrome version).
Hope that helps!
You may want to check this thread which states the following:
If these are school managed chromebooks, see this topic.
If it is not managed or if the settings have not been changed in the management console, the chromebook does have to be restarted to finish updating.
https://support.google.com/chromebook/answer/3134673?hl=en
Simply follow the given steps on how to manage kiosk settings.