As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
User-Agent : Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)
Host : baas.kinvey.com
DNT : 1
Connection : Keep-Alive
Cache-Control : no-cache
If I compare the same request in Chrome is seems to have an Authorization header which the request in IE is lacking. I dont know if IE is just masking it or something.
@kueckermann can you post the init code you are using? Also, could you add a "debug: true" option to the options being passed into init, and post the console output after running it again?
k
kueckermann
said
almost 9 years ago
So I narrowed the issue down slightly and found where the fail is happening. Still unsure why its happening. I manage to get Kinvey to init by setting refresh to false. With it set to false the initialization is successful.
However, if after the successful initialization I call Kinvey.User.me(), the request for the users details will fail.
So it seems to be some issue with getting the users details.
The debug true doesnt seem to put anything new into my console.
To be clear I am only getting this behavior in Internet Explorer (Currently using version:10.0). Everything runs correctly in Chrome and Firefox.
I N I T C O D E :
window.onload = init;
function init(){
Kinvey.init({appKey : 'kid_ePhI749lsi', appSecret : 'Not sure if to post this on the forum?', debug:true , refresh:true,
success:function(activeUser){
_log('INIT SUCCESS',activeUser);
},
error:function(e){
_log('INIT ERROR',JSON.stringify(e));
}
});
}
C O N S O L E :
SEC7118: XMLHttpRequest for https://baas.kinvey.com/user/kid_ePhI749lsi/_me/?kinveyfile_tls=true&_=6hla148wbrsi required Cross Origin Resource Sharing (CORS).
SEC7119: XMLHttpRequest for https://baas.kinvey.com/user/kid_ePhI749lsi/_me/?kinveyfile_tls=true&_=6hla148wbrsi required CORS preflight.
SCRIPT7002: XMLHttpRequest: Network Error 0x80070005, Access is denied.
https://baas.kinvey.com/user/kid_ePhI749lsi/_me/?kinveyfile_tls=true&_=0hym8dpmz7rzb ; OPTIONS ; 200 ; CORS Preflight
https://baas.kinvey.com/user/kid_ePhI749lsi/_me/?kinveyfile_tls=true&_=0hym8dpmz7rzb ; GET ; 401 ; XMLHttpRequest
k
kueckermann
said
almost 9 years ago
Hey, Shortly after posting my last message, Kinvey seemed to completely stop working for 5 to 10 minutes and then after that I was able to initialize Kinvey on IE. Did you make some changes or find where the problem was?
D
Dave
said
almost 9 years ago
@kueckermann we did have a brief server issue on the 24th, although no new code was deployed. But you say it's working now?
k
kueckermann
said
almost 9 years ago
Hey sorry I forgot that I hadnt responded here. Yes last I tried it seemed to be working fine. So, I will keep an eye out and if the problem arrises again I will inform you guys.
kueckermann
I am unable to init Kinvey from IE10, here is the logs from the javascript console.
SEC7118: XMLHttpRequest for https://baas.kinvey.com/user/kid_ePhI749lsi/_me/?kinveyfile_tls=true&_=hoh073my4lzz required Cross Origin Resource Sharing (CORS).
SEC7119: XMLHttpRequest for https://baas.kinvey.com/user/kid_ePhI749lsi/_me/?kinveyfile_tls=true&_=hoh073my4lzz required CORS preflight.
SCRIPT7002: XMLHttpRequest: Network Error 0x80070005, Access is denied.
ERROR 401 : {"name":"RequestError","description":"The request failed.","debug":"error"}
Here are the request headers if it is useful.
Accept : application/json
X-Kinvey-Device-Information : js-html5/1.1.8 (jquery/2.1.1) msie 10.0 win32 unknown
X-Kinvey-Origin : http://cms.react.community
Referer http://cms.react.community/_COMPILED/React/
Accept-Language : en-CA,en;q=0.8,it-IT;q=0.6,it;q=0.4,hu;q=0.2
Origin : http://cms.react.community
Accept-Encoding : gzip, deflate
User-Agent : Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)
Host : baas.kinvey.com
DNT : 1
Connection : Keep-Alive
Cache-Control : no-cache
If I compare the same request in Chrome is seems to have an Authorization header which the request in IE is lacking. I dont know if IE is just masking it or something.
Any help is much appreciated.