Using react-native with MS Appcenter. Configure everything according to the docuement.
When the app crash, Appcenter didn't receive crash report.
What happen?
What is DO_NOT_ASK_JAVASCRIPT?
<string name="appCenterCrashes_whenToSendCrashes" moduleConfig="true" translatable="false">DO_NOT_ASK_JAVASCRIPT</string>
this setting means that crashes will be sent automatically, without confirmation in js code.
Do you have debugger attached to the app? Do you see crashes under Unsymbolicated tab on the portal?
Related
I have a web application in azure(App Service), recently i have restarted the app, after restaring i am getting:
500 - Internal server error.
There is a problem with the resource you
are looking for, and it cannot be displayed.
Please let me know what could be the issue. application was working fine till that time. I didnt change any other settings.
How to resolve this issue?
Go to the app service, then pick Monitoring -> App Service Logs. Then enable Application Logging (FileSystem) and save the changes. Now go into Monitoring -> Log Stream and watch the Application Logs while the site is starting up, this will most likely give the detailed error message.
There are a few things you can do step by step
Step 1: Use the KUDU console at https://sitename.scm.azurewebsites.net. Check if there are errors. More info about KUDU
Step 2: Have you turned on the detailed error message in the Diagnostics logs tab of the Azure portal. If not enable and see if you can track any error.This will give you a .zip file. Browse to LogFiles->DetailedErrors and here you should see some error pages.
Step 3: You can add Application Insights to your application and log those errors when you start the application
If nothing works, try restarting app service, or access it from a different location (because it happened to me earlier)
I have added Azure Application Insights to a number of my .Net WebAPI applications. I've noticed that I do not receive successful request telemetry from these applications. I do receive dependency telemetry and failed requests but not the actual telemetry that the request has been made. By fudging the URL or the request and forcing a failure, I can see that get sent to AI, so my issue is definitely not with the instrumentation key.
I initialize the instrumentation key as follows:
Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration.Active.InstrumentationKey =
ConfigurationManager.AppSettings["ApplicationInsightsKey"];
I have attempted to remove AI from the application entirely and added it again using the Configure Application Insights option but it still does not work. There is another of my web apps that uses AI that was configured a while back and it works perfectly, I have replaced the set up of the broken app with that of the working app and also made the package versions line up but I still only get telemetry for failed requests. The capture below from the Live Stream shows this, the red arrow points to the dependency calls made for the successful request, yet nothing shows in the Request Rate graph for it. In contrast there is a failure before it, and that is logged.
I just found the answer for this in a solved issue on the Application Insights Github. The solution is to open your ApplicationInsights.config and scroll to the telemetry module Microsoft.ApplicationInsights.Web.RequestTrackingTelemetryModule below it comment out the line System.Web.Handlers.TransferRequestHandler
This issue has been fixed and is due to go out in version 2.5 of the packages. You can read through the issue here https://github.com/Microsoft/ApplicationInsights-dotnet-server/issues/175
Try below one, it works for me:
Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration configuration = Microsoft.ApplicationInsights.Extensibility.TelemetryConfiguration.CreateDefault();
configuration.InstrumentationKey = System.Web.Configuration.WebConfigurationManager.AppSettings["InstrumentationKey"];
I'm setting my Node.js project with swaggerize-express, and are currently testing my backen using supertest to test my backend.
When I run the supertests, and it fails due to swagger rejecting (i.s. input validation fails) the data I pass to it, currently I simply get a 400 error message, without any details on what's wrong with my query.
I'd like the backend to provide some hints as to what input data it rejects. I haven't found any debug options to set in swaggerize-express, so how can I go about getting the backend to ouput some details on the validation errors? Wether the validation errors are provided in the server log or in the data returned to the client is not important at this point, although I'd prefer the latter.
if you deploy your API in a Microsoft Azure App Service you will take benefit of the Output Logs.
Check my post on how to deploy a node.js API quickly in Azure:
http://mosshowto.blogspot.fr/2017/10/try-azure-app-service.html
When it's deployed, go to the Visual Studio Code online editor, check your deployment.Then, Hit the run button. The server will try to start your API and will log any error in the output if needed:
I've deployed a node.js chatbot (built using Microsoft Botbuilder package) as an Azure web app. As seen in the attached image, the conversation in channel emulator(same with web chat) goes on smoothly until there's a db call. The part were the intent handler tries to do db call, the bot responds with the default error text(I didn't understand. Please try again.).
Interestingly, if I type in something random( like a Hello) in response followed by the query again, the bot goes ahead with the db call. This scenario is shown in the attached screenshot.
Strangely, the issue doesn't happen when I work on the bot locally or deploy it outside Azure (say AWS).
My question is how do I figure out what exactly is going wrong here ? I have been going through the logs in the Diagnostic Console(Kudu) of my Azure web app, but no pointers in any of the logs. Any help is appreciated!
edit: Got it fixed by following the steps from this link
I am newbie in Azure development ,I am migrating an existing asp.net application to be hosted as cloud service ,everything works just fine locally (on dev. AppFabric) but when I publish it on cloud and after I try to singin on my signin.aspx page it keeps giving me "This webpage is not available" error .
after that refreshing the page gives me "HTTP Error 503. The service is unavailable." error
my signin page does a lot of stuff (calling db procedure ,setting user session) before redirecting to default page [I am using the free azure trial account]
what may cause the problem ,how can I debug ,why everything works fine on the emulator ?
Checking the event Viewer I found that the problem was in "Debugger.Break ();" inside a class it seems like that line just freaks the runtime out and causes it to lose control and recycle the Application Pool and stopping the service !!!!
You should set up a remote desktop connection to your web role instance and look at the Event Log for IIS. You will want this for development and testing independent of your current issue.
Links:
http://www.windowsazure.com/en-us/develop/net/common-tasks/remote-desktop/
http://msdn.microsoft.com/en-us/library/windowsazure/gg443832.aspx