I'm currently working on an issue with a Microsoft Edge Add-In written in React in which state changes aren't working, and I can't see any of my console logs.
Some context:
I have a web Add-In for Microsoft Outlook desktop that I am trying to run on Windows 10 version 1903. I've added console logs to the event handlers of a few button clicks and several other events throughout the app, but none of these console logs actually show up in the Microsoft Edge DevTools console. I can see calls to console.log('We just clicked a button') in the compiled JavaScript file in the Debugger, so my changes are being picked up and are in fact there, but no actual console logs show up inside of the DevTools console. The only error I see in DevTools is XML5632: Only one root element is allowed on index.html (1, 1).
I should note that the web Add-In works in Microsoft Outlook desktop on later versions of Windows 10, but running it on version 1903 is the only time that it's problematic.
An answer on this forum: https://www.outsystems.com/forums/discussion/20753/xml5632-only-one-root-element-is-allowed-error-on-windows-edge/#Post88600 suggests it's a problem with Edge interpreting an Ajax call as XML, but doesn't elaborate much more beyond that.
My guess is that this a JavaScript issue with pre-Chromium Edge, but I'd like to know if anyone has any suggestions on a workaround or fix so that I can 1.) Resolve the issue with the state change in my React app and 2.) See my console logs.
Related
Not sure if anyone had this problem, since I could not look it up anywhere but I cannot see any logs for react native app because the browser console tells me that "Another debugger is already connected" its a warning that keeps looping.
Metro bundler is telling me that I have to see the javascript logs in the browser. I cannot work on my app without debugging it, can anyone help ?
This happens if you have another tab opened at http://localhost:8081/debugger-ui as you can only have one instance of the debugger running.
You could either go back to the already running tab and see the logs there or close the other tab and refresh this one.
I implemented Appsflyer OneLink with my cordova(Ionic)application and for android everything works fine.
In iOS, when i run the application directly to the device from Xcode and when i click on a link it opens the application.
But i uploaded the ipa file to Hockeyapp and then downloaded the application and installed and then again i clicked on the link but it redirects to the appstore.
i have added associated domains as well as i doubled checked the team ID as well as other configurations(Universal Links) and they all are according to the documentation.
Any idea about the issue that i am facing here?
If the application does not open as a result of clicking the deep-link in a "Universal Links" scenario, it could be one of the following issues:
When releasing to HockyApp some credentials that are used by the Universal Link are broken - it could be the Bundle ID or the Development Team Prefix.
You can check the credentials available on https://your-defined-subdomain.onelink.me/apple-app-site-associations and compare them to the entitlements set in the HockyApp build.
There is a known "development bug" with Universal Link, which sometimes forces an uninstall of any previous version of the Application, in order for the Universal Link to function properly.
If the issue still persists, you can always open a support ticket with support#appsflyer.com and share more information that could help with debugging this.
I was executing webextension on Firefox for testing with about:debugging menu.
Then tests are done, I want to stop it.
I am looking for a way to stop without shutdown browser, but I can't find a way to stop it out.
Is there way for do it without shutdown browser?
Just like a normal add-on, you can disable or remove a temporary WebExtension that was loaded from about:debuging from about:addons (Ctrl-Shift-A, or Cmd-Shift-A on OSX) . If you "Remove" it, and then refresh about:debugging you will see that it is gone from that list.
If you do not refresh about:debugging after disabling or removing it, it will remain in the list that is displayed. This can be convenient if you are testing behavior when the add-on is installed or removed.
The following gif shows loading and removing an add-on named "aaaaaaaaaaaaaaaaaa - demo add-on":
If you do not refresh about:addons after removing an add-on, the add-on will remain in the "uninstalling" state. From that state you can "Undo" the removal/uninstall. This is displayed in about:addons with the "Undo" link. The fact that an extension is in this state is not available to WebExtension add-ons, but can be seen from other Firefox add-ons using the Add-on Manager API. The Add-on Manager API is not compatible with WebExtensions. If you want to take a look at a Firefox Add-on SDK based add-on that shows these states, you can see my answer to another question.
I started exploring react-native. One thing which I want is should able to debug my app from chrome. I am having prior experience to cordova. Cordova renders app in chrome web view. I understand that with react-native it is not possible because react-native doesn't render app on web view.
There is an option react-native "debug in chrome". When I click this option, attached screenshot is getting opened. I enabled "pause on exception."
But nothing is happening. I am unable to see my app code at all.
I like to do step by step debugging. Is it possible? If so can some one tell how to do this?
You can definitely examine the source code, set breakpoints, etc in Chrome.
In the Sources menu, select debuggerWorker.js and then you should be able to see your project tree.
Any console.log in your code will print to the browser too. But I find the breakpoint inspection most helpful.
this is simple as you were doing in cordova.
try to put debugger; statement in your code while in debug mode.
It will set the breakpoint and you can then debug your application. No need to find out your files in debuggerWorker.js
Is there any circumstance that would cause IE9 to force an unrequested page reload? If so how can I tell that this is occurring? Is there a log I can look at or custom event I should be looking for in event viewer?
I am troubleshooting an issue with an AngularJS web application that only exists in IE9, it works fine in newer version of IE and works on FF, Safari, Chrome. When testing in IE9 I see no errors in the console but I am getting redirected to my applications login page. This redirection always happens on a page reload, hence why I think IE9 is forcing a page reload.
You can track navigation events, and the subsystems that invoke them, using the Network tool in Internet Explorer 9's F12 developer suite. Press F12, switch to the Network tab, and press "Start Capturing". From this point on, any further navigation events will be logged for your inspection.
Internet Explorer 9 uses an older version of the F12 developer tools, but you can still access the historical documentation for those on the Microsoft Developer Network.
The modern documentation for IE 11 is also available online, and much of what is shared about the Network tool in particular is still helpful even if you happen to be using Internet Explorer 9.