I've checked for possible duplicate and found one, but having implemented his solution and not finding any luck, thought I'd ask the experts.
Crashlytics has been setup on my app properly. But it isn't reporting the errors in my dashboard. I've attached a picture from my terminal. The crash is being handled and an attempt is made to send it to the dashboard.
Perhaps there is a delay from the time I setup crashlytics for the first time? It has been up and running for at least 30 minutes. And I've also downloaded the google-services-json file again after setting it up.
Any suggestions?
Everything is fine. There was just a delay in the reporting. The crashes have started showing up now, but they aren't as instant as I thought they would be. Much more detailed than Google Developers crash report though.
Related
My app has been test running without crashes for some weeks now. However, in Logcat there are 3 persistent errors (lines marked with "E"). I do not know how to solve them, but they do not appear to harm the proper functioning of the app.
E/zygote64: Failed sending reply to debugger: Broken pipe
E/MemoryLeakMonitorManager: MemoryLeakMonitor.jar is not exist!
E/vndksupport: Could not load vendor/lib64/egl/libGLES_mali.so from sphal namespace: dlopen failed: library "vendor/lib64/egl/libGLES_mali.so" not found.
How usual is it for developers to publish apps (like on Google Play) that knowingly have errors in them that don't seem to be "mission critical"?
The google play console has a 'Bad beheivour treshold' of '1.09%'.
This is calculated by: 'Percentage of daily sessions during which your users experienced at least one crash. A daily session refers to a day during which your app was used.'
So you should aim to have a lower crash rate of 1.09%. There will always be bugs in your app that you haven't encountered yet in in your tests so an app will (almost) never be completely crash free. So a lot of developers publish their apps while there are still (mostly unknown) error's in them.
Sadly enough I can't help you with your exact errors but I hope I have helped you with the Google Play Console Guidelines.
I have a Azure App Service app that I'm trying to get deployed.
Today I ran into an issue where .NET informed me (via the yellow screen of death when I browse to the URL of my app) that I had a missing DLL (for the purposes of this question I don't think it really matters).
I used FileZilla to publish my changes in an attempt to do a manual deployment first and then work my way to automate it.
After so many attempts to fix it I later realized that the error message never changed. I did something more severe and renamed my bin folder into something completely different and the exact same error message would appear.
I've stopped the service, restarted it, and as mentioned, renamed folders, etc. and still the exact same error message persisted.
I also decided to open up the Azure Portal Console for my App Service app to browse a bit and to my amazement, nothing seemed to have reflected at all. The FTP shows one thing and the Console shows another.
Would anyone have any idea as to why this is happening?
I eventually got it to work and I will share what I tried.
I deleted the web app and created it again (I found this to be important the first time around). This was quite time consuming and did help but it wasn't long before the same problem happened again.
Then I finally found a solution that seems to give me consistent results:
I kept on editing the Web.config which seems to force a recompile and clear some sort of cache. So each time the web app stopped updating, I would make a slight change in the Web.config, upload it via FTP and the app finally updates.
If anyone has any more details on this, it would be greatly appreciated.
every time I try to publish my web app to azure it gets stuck, how can I determine what the problem is? logs etc, I cant see anything but the output but thats not enough to diagnose the issue.
So the way I got around this issue was to set the visual studio parallel build settings to 1.
this would force visual studio to build each individual project one after the other, and this way you would be able to diagnose if there is something going wrong during the build stage or not.
fortunately for me nothing was wrong with the build stage and my project got published fine.
Same thing I have faced many times, process stuck while publishing Web app.This is related to network speed. May be at that time your network speed is slow. Please make sure while your will going to publish your network speed should be high.
This is work for me.
I have just installed Wordpress in a new Azure Web Application and everything is running fine at the moment.
However, I am getting notifications that I am exceeding the storage file system quota (1GB).
I went to check the value on the Azure Portal and the strange thing is that the storage usage is varying from 12% to 100% every single minute! Somehow the measurement must be crazy, since I am not changing a bit in my website nor have huge files there.
12% must be the realistic value for Wordpress. I have tried to reset the website and check log files to see if there is anything wrong, but did not find anything.
How can I fix that?
Igor.
You might want to try de-activating the most recent plugins you installed 1 by 1 to see if this corrects the issue. There could be a bug in one of them that has some type of loop that generates a large log file.
At the end of the same day the problem disappeared. It seems everything is stable now, but if happened once, it might happen again. I will keep you posted in case I experience this problem again.
Thank you.
When I try to run a report in cognos 10.1, i always get the error:
XQE error encountered: The request was cancelled by the user.
The error goes away when we restart cognos server. Is there any other way of solving the issue since restarting so many times is a problem.
This happens to me if I run a report, cancel it, then run the same report again. This is due to 'high affinity' getting confused and trying to reuse an process that has been cancelled.
When I run the report for a third time it's fine.
Does it only happen for a single report, all reports, some reports? How exactly do you reproduce the problem?
If restarting the server is an issue you could just install two app servers and restart them one at a time, and your users will experience no down time at all.
I don't think you will be able to solve it here but we can at least get you to think about stating your issue more clearly.