Is there anything that can be done to get real-time error reporting from windows phone devices? I have code in my app that will catch errors to let users send them via email, but it's just not happening and yet I keep seeing errors being logged, very few but still occurs every few days, via the Dev center but without details, which is completely useless to me.
Any suggestions, tools, other would be appreciated.
Thanks.
If app crashes try get your info from UnhandledException event and write it to some kind of log file so next time app launches you can send those logs Reference
I've used it in WP8 application and worked fine. To get usefull information from exception do arg.ExceptionObject.ToString()
Use Application Insights to find out what users are doing with your app,
http://www.visualstudio.com/en-us/get-started/get-usage-data-vs.aspx
Related
So I'm trying to programmatically conduct Google Lighthouse audits on several webpages, and I'm running into an issue. After installing Chrome and node/npm/lighthouse on an Amazon Linux 2 EC2 instance, I am able to successfully run LightHouse tests when I initiate a GUI session and run a command from a terminal within the GUI (this launches chrome and conducts the test as usual) but I am unable to do the same thing from the command line. This is the error I get when launching lighthouse.
ChromeLauncher:error [42565:42565:0516/170626.787500:ERROR:brower_main_loop.cc (1386) Unable to open X display.
While there are a couple of other errors, I believe this is the one I should be paying attention to, because when I try to just launch Google Chrome, that is the exact error I get, so I am inclined to believe it is an issue with trying to launch on a display.
I've also tried the "--headless" option when launching chrome and get
[0516/171128.450564:WARNING:headless_browser_main_parts.cc(83)] Cannot create Pref Service with no user data dir. [0516/171128.521499:ERROR:vaapi_wrapper.cc(594)] Could not get a valid VA display [0516/171128.524992:ERROR:gpu_init.cc(426)] Passthrough is not supported, GL is egl
Another user with a similar question decided to use the Google Pagespeeds API, which will not a be a solution for me-- it needs to be done locally.
Because this works fine on a GUI session with the same server, I really think it's just a display rendering issue, but I don't know how to solve this. Maybe "simulating" a display? I've also tried entering export DISPLAY=1:0, which apparently worked for some users and caused me to stop seeing the error, but the functionality was still broken when running the audit.
Any help would be so useful!!
Information found in this stackoverflow question was infinitely helpful. Although I still get a slew of errors when I try to launch the browser, I can successfully run LightHouse and audit the pages I want to without any errors.
When I try to create an API in APIM by using Create from Function App, I fill out the fields and click Create. The operation provides the wait dots and comes back in five seconds and says
Could not create an API. Please try again later.
I can create a blank API...but not one from an existing Function App. I have tried multiple combinations, No products, all products, no version, version..etc. No luck.
Thoughts?
Notes
The function in question is an HTTP Trigger.
The function works locally on my development box and in Azure.
APIM Tier is Developer
On that Function app, during Publish in Visual Studio I have reported that attempting to manage application settings before a publish fails and in trying to add a new one causes Visual Studio to unexpectedly close. Manage Application Settings on Publish Related, don't know.
Just a Ctrl + F5 solved the problem for me. Try it! ;)
I just ran into the same issue because I used Linux (Preview) instead of Windows. When I blew away the Function App and recreated a new one with Windows, my API Manager was able to create an API off it.
I have reproduce the same scenario. It is working for me. May I know, below details,
01.Hope you have tested your function and it is working fine.
02.What is the type of the function ? Hope that is "Http trigger" ?
03.What is you APIM tier ? (eg : development, basic etc.)
At this time the solution for me was to use Microsoft Edge instead of Chrome.
It seems Microsoft Azure portal is not working properly in Chrome and I noticed issues in several places. Parts of pages are not rendered at all and sometimes even errors like this pop up just because of the browser.
I had this same problem.
The fix was both simple and unexpected.
When importing the function app, simply enter "/" in the API URL Suffix field.
For me this changed the BaseURL field value. Originally it was just the host, ie http://hostname/. It then appended the endpoint the hostname, http://hostname/endpoint
This is done on the "Create Function from App" modal.
I had the same problem when trying to publish my Azure Functions application with several HTTP triggered functions through API Management running on Consumption plan. The plan did not have anything to do with the problem though.
What I did not realize was that my function app was not working properly when browsing it from the Azure portal. I had some configuration errors that prevented the app to work properly. When I resolved those, I succeeded to publish the application through APIM.
So, check that your application is working properly by browsing to it if you run into the problem described in this thread.
I had temporarily suspended (or stopped) my Function App. Restarting it resolved the problem.
I hope Azure could improve the error message, at least from UX perspective.
The issue was that the function did not actually work.
The Browse button that redirects to the page with the light bulb and the text Your function app version X is up and running did show, but the function still didn't work.
The function error had to be fixed before when importing to the APIM was done.
When I try to log out(both using my own button and the one provided in the SDK) I am "able" to log out. The reason I use the quotation marks is that when I will try to log in again, it is automatically logging me in as the previous logged in user. Thus, I am not able to change user. I'm assuming that this is some cache issues in the web browser or something like that. Anyone know if this will be fixed when the sdk is out of its alpha? Any help appreciated!
The problem is that the FB authentication cookies are still in the WebBrowser data.
Here is the code that clears the WebBrowser cookies (no matter which instance of WebBrowser it's called on):
await new WebBrowser().ClearCookiesAsync();
I have submitted my windows phone 8 app,
There is a option called Reports of our apps in Dashboard of developer account page,
In that we can see the "Crash count " option.
Here i can track my app downloads, but i couldn't see any app crash.
Am i need to add anything specially to update this crash count, like capability.
Can anybody help me.
Thank you.
In the Dashboard Reports section you have one option called App Downloads, there you can see the number of times your app has been downloaded over a period of tiem.
In the Crash count report you actually can see the times your app has failed, (a crash). If you don't see anything there... that's good men! your app never do a crash fail. Good Job!
So, if you want to see the downloads go to the "App downloads" report instead of "Crash count"
Got the answer, thanks for #KooKiz comments.
No need to add any more extra work, it's automatically enabled. But the end-user must have the "Send feedback" global setting enabled on his phone, or his crash reports won't be sent.
And there is no way to track the number of times the app is uninstalled.
Thank you.
I would like to record the logcat of my app and offer to the user the possibility to send it to me via email. I already have implemented all the flow and only the logcat tagged by me will be reported. I am aware that many personal information is output into the logcat, so I would like to know if there is any policy regarding to this?
I will answer myself saying that the LOG_READ permissions is not longer supported in android 4.1, however you can read the logs that YOU have written without need any permission.
Conclusion: No problems on reporting your own logs to yourself