I've lunched an app on Google Play Store, and some of my users, have Errors on the app:
Errors that i don't see on emulator or on my device.
So I was wondering how can i get the error logcats of that users so i can debug them and improve my app, I've been reading Android Vital information but only shows the errors and ANR the stats, and can't find the logcat.
Is there any way to get my users error logcats, or should I implement a function on my app to send the logcat through internet to me?
You should use Firebase Crashlytics SDK which will automatically send errors that occur on the user's device to firebase that you can see on firebase console. You'll be able to find in which activity/fragment etc the error occurred and at what line.
From the Firebase website:
Crashlytics intelligently groups an avalanche of crashes into a
manageable list of issues. It also provides information on why a crash
occurred and what happened leading up to it. With this insight, you
can uncover the root cause of crashes more quickly.
Related
I have a Google Assistant action that has been happily storing data between conversations on the conv.user.storage bucket. It has suddenly just stopped working and I am struggling to track down why. The only major change was deploying an alpha release of the action. i have checked and the user is VERIFIED and it returns old stale data when I do a trace.
Is it common for this to just stop working?
I paused the Web Activity control on my Google account, and then started it again. Suddenly the data persistence worked again. That's not great though. That it could just stop like that?
I just want to create a windows 10 mobile app but in mobile app when i select quick start it doesn't display result and this error is shown.
Could not install MobileAppsManagement Site Extension.
SettingListPart
MICROSOFT_AZURE_MOBILESERVICES
This error is viewed after clicking on quick start
The error is generally indicative of a browser issue and rarely of a permissions issue on the azure subscription that you are logging into. Force reload the page or clear the cache and try again.
Obviously, after the crash Developer tools at port 9222 is of no use, because "Remote debugging has been terminated with reason: websocket_closed". How can I retrieve, for example, recorded timeline; or get call stack; or find anything about the reason the Chromecast decided to reboot itself? What are the best (or, for that matter, any) approach to debug Chromecast crashes?
We need to look at your log file to see what is causing the crash. It is relatively easy to do that but we need some help from your side.
First, open the Chromecast setup app on, say, your Android device and go to the settings for your device. You should see a check box that states something like: "Send Chromecast usage data and crash reports to Google". If it is not checked, make sure you check it and then wait 15 minutes or so and reboot your chromecast.
Try to recreate issue and as soon as it crashes and reboots itself, open the setup app again and select "Submit feedback report" from the overflow menu. You will see a new window on your phone and make sure you enter the following text in the text box there "crash-vmt". We will be using this text to search among the reports that we receive to identify your log.
After doing that, please let us know (add a comment here) so we can grab the log for further investigation.
It appears that the libspotify page is once again no longer able to generate application keys. When trying, either via Firefox or Internet Explorer, the page reports that "There was an error generating your application key". Is the site down again, or am I doing something wrong? I've never used that page before.
Earlier today, the SpotifyPlatform Twitter account reported that the service is having issues. However, they must either be working on it or have finished doing so as a key request I just put in worked properly.
I'm working on a Spotify App, but the Spotify application keeps crashing on me. I have been trying to debug my own Javascript code, to see where it goes wrong, but it seems a bit random. It almost always happens when my app loses focus (i.e. switch to another app). Is there a compatibility issue with jQuery perhaps?
Unfortunately I can't find any crash-logs or anything, for Spotify. Are there any?
I hope someone can help me along here, because this problem makes developing cool Spotify Apps as good as impossible.
Edit: To clarify, I'm using Spotify 0.8.8.450.gd9413514, on Windows 8 64-bit, but I've also experienced the same on Windows 7 and Mac OS X 10.6.
Using Windows 7, you can create a crash log by accessing the Task Manager, right clicking the Spotify process and selecting "Create dump file". If you're on Mac OS X, you can get a crash dump by opening the Activity Monitor, selecting the Spotify process and clicking 'Sample Process'.
I was having the same problems, It seems related to ads banner on the top. Run the ad video and pause it, that solved the problem for me.