I am using Extjs in my application with J2ee framework. it happens that after working for sometime on my application I get a communication failure. There is no server side error.I have to delete cookies from my browser (i use IE most of the times) and then restart my browser and everything works fine. CAN I GET RID OF THIS PROBLEM?
Do you know the specific error. For a while, I was getting a 502 error. This turned out to be a concurrency problem - I was firing off a datastore load then immediately doing a refresh of my control. This error mostly showed up under IE6, less so on other IEs and never on FF.
Related
I've a weird problem with react.
We use this react video component ([https://www.npmjs.com/package/react-video-recorder) to record or upload a vide file. And It's working fine on mac (both chrome and firefox).
On windows, it's also working fine for the recording part. However for the upload part, when the upload file is more than 20mb, It's not working neither for chrome nor for firefox (on windows).
The weird thing is that we doesn't have any log error on our web server. The only error is a "cors error" showing up in the browser developer console. So it seams that the upload fails even before reaching our api. (That say I'm sure that its not a cors issue because it's working fine when the video size is less than 20Mb, and both front and back share the same domain anyway)
I'm also sure that is not a timeout issue because our axios timeout is set to 1 hour and fails after only a few second (and it is working fine on mac anyways so It couldn't be a time out issue).
Could someone help please?
I have a really strange problem with an AngularJS application using Internet Explorer (ver 11.0.9600.18697) as browser.
I am developing an application using AngularJS. The application runs perfectly on Firefox and Chrome, but on IE I'm experiencing the following problem.
What happens is that, when I start the application, the startup stops because IE at a certain point randomly stops loading the necessary resources, simply terminating some calls of js, i18n, css files.. (calls do not arrive at the server, simply IE blocks them, despite being the path all correct).
I have not understood the reasons of this behavior. What I know is that I use RequireJs for loading files (ver. 2.1.22), and that on Firefox and Chrome everything is loaded properly. Moreover, if I start the application on IE keeping Fiddler open, then the application works very well on IE too.
Has anyone ever had a similar problem?
Here the network console:
For some reason the iPhone devices are never able to load the url requested by Protractor, they always show a blank page. It tries to load the url several times and then gives up.
The other BrowerStack devices all seem to work, including Windows, Android, and Safari/Macbook.
Has anyone encountered a similar problem?
For reference, we're using Protractor v2.2.0 (have not been able to updated because we're stuck in an old version of NodeJS, but we could try if that is the cause of the issue).
I have an application in AngularJS. We are about to launch it and QA just discovered that no data gets saved with IE versions 9,10 and 11. I see in network tab in console that the get request and post are sending the right data, but as soon as the user navigates away from the page and then goes back that data is no longer there. If the user logs out then logs back in the data displays correctly. In all other browsers there isn't any problem, only in IE 9,10 and 11.
Is there a plugin I need to be using to solve this? Anyone else ever have this problem and if so how to solve.
I solved this problem with Internet Explorer cacheing all the get requests by installing this module:
angular-cache-buster
If anyone else has this issue its an easy fix!!!
I have an Angular App that we recently upgraded to AngularJS v1.3.8 and now we get intermittent "Aw, Snap" crashes in chrome. But the app runs fine in other browsers and on certain computers.
Any time we encounter this error a refresh fixes it immediately.
We have explored many options trying to figure out the root cause of this issue:
- Verify memory profile
- Verify CPU profile
- Verify Hardware Acceleration on/off
- Verify minified/unminified AngularJSv1.3.8
When we reverted back to Angular v1.2.7 we no longer see this crash. We have isolated this change and is the ONLY change between revisions.
Has anyone experienced this as well? Or does anyone know of any reasons for this? Or any compatibility issues that could lead to this error?
Error encountered using Chrome Version 39.0.2171.95 (64-bit)
For us, this occurred when we did an $injector.invoke inside a responseError interceptor. It seems that it is sensitive to that.