I'm using 2.12.2 version of Quickblox, and Edge 42+ version. The call is made from iPhone8+ to the browser, and video chat isn't successfully established every time.
The console is displaying an error:
ORTC18614: ORTC RTCIceGatherer: Transport endpoint allocation failed. hr=c004e00e.
And next:
SCRIPT5022: InvalidStateError quickblox.min.js (1,363529).
Quickblox documents state that Edge 14+ is supported, but there seems to be an issue.
Is anyone having a similar problem with Quickblox and Edge? It seems that Edge is not fully supported. Is there any solution to this problem?
EDIT: The same behavior is reproducible with the QuickBlox sample code. Also, after 30 seconds, the call is disconnected.
Related
I'm developping a website which is meant to be used on mobile devices using Google Chrome, the purpose is to list information such as time (hh:mm) and battery level.
I saw the Battery Web API but I'm experiencing a strange error:
click to see the chrome error
Here is the code I used in order to get the battery level:
navigator.getBattery().then(function (battery) {
console.log(Math.round(battery.level * 100))
});
I had the error yesterday, without changing any line of code, it is working today on my tablet (chrome version: 103), but I tested on another tablet (Samsung Galaxy TAB A7 LITE, Chrome version: 103) and I encounter the error, I restarted several times the devices, inspected pages using the devtools connected by cable to my laptop, but I can't solve this error.
I saw a topic having the same error but he was developing a web worker it is not the same context as I.
No matter when I'm calling the navigator.getBattery() if the error appeared in the beginning it will stay undefined later, so it is not a problem of timing to call it (I even bound it to the body.onload but it didn't work).
I thought it could be authorization issues on system information but there's nothing refering to the battery which is not authorized in the application settings of Chrome.
Any help is welcome :D
I found out where my error was coming from.
It is a problem of HTTPS, my testing environment is configured behind a NGINX HTTP Server, which serves HTTP and HTTPS version of my application in order to use a single certificate for every of my projects, Chrome on my laptop prefix URLs I'm accessing with https:// and it is hidden in the navbar, but it is not the case on Chrome tablet or mobile, I thought I was consulting the HTTPS version but it was HTTP, and Battery Web API isn't accessible on HTTP websites, it is required to have a secure connection using HTTPS and certificates. It has nothing to do with version number since Battery Web API is fully supported since Chrome version 38 according to MDN Documentation.
Recently, I am getting the following message on chrome console;
WebSocket connection to 'ws://evo15:4008/?stream' failed: Unknown reason
It's getting more and more and it's somehow annoying and I have to open a new tab or restart chrome every time to get back to normal websocket connection. How can I debug it? Unfortunately, I cannot reproduce it yet. My chrome version is Version 77.0.3865.75 (Official Build) (64-bit)
Update 1: I think you could reproduce it by closing the connection for a long time (I don't know the exact time) from server side and then open it and try to connect to it (client trys to connect every 1 sec). Then it will happen. So I guess there is an expire time or a limited number of tries to connect somewhere.
Update 2: It happens after 256 tries of reconnection.
WebSocket connection to 'ws://evo15:4008/?stream' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
After seeing 255 of this error on console, you will see the first error and cannot reconnect. So I think there is a 8 bit limit somewhere that I am missing
Looks like someone just filed this as a Chromium (v77) bug. See issue tracking it here.
Update 1: As noted in the issue tracker and comments below, this should now be fixed in the latest stable release, which is being rolled out now (2019/10/11).
Update 2: Despite the bug being marked as fixed/closed in monorail, canary (80.0.3977.4) still appears to have this behavior. As others have noted there is a global limit of 255. However, the fact that connections opened by JS don't get closed/reset when the page is refreshed still seems like a bug to me.
For some very very very odd reason in my computer the websocket connection was considered as an ad by AdBlock.
Try to disable AdBlock and see if it works.
I'm working on establishing a RTC connection between a Chrome/ff client and Edge client. I'm using the most up to date adapter.js shim. I have everything working without a hiccup except for the following two:
1) The call can only be initiated by the Edge user, otherwise the transfer of sdp information doesn't complete.
2) When initiated by Edge user, the full exchange happens, but remote videos can't be seen, which I think I've narrowed down to a discrepancy in stream ids between the two clients.
Chrome local streamid: "aPshOXkbsPHswpajCqzaJcLowZzSHZr6QrPD"
Edge local streamid: "89077962-9A1B-47B9-8754-7B80FAAC82DF"
Chrome remote streamid (Edge local): "89077962-9A1B-47B9-8754-7B80FAAC82DF"
Edge remote streamid (should be chrome local): "3750A59D-7E90-450A-96BB-63EED7D564C3"
So it seems that Chrome has an issue with the id of the Edge stream, and then for whatever reason Edge is interpreting the Chrome stream and/or its id.
One ancilliary issue that I've noticed with Edge is that when the success function fires from the navigator.mediaDevices.getUserMedia function, the video camera starts up, but then immediately shuts down. I have to enable it afterwards through javascript and then obtain stream ids, otherwise chrome/other client won't even get correct stream information of edge's running stream.
I haven't submitted an issue on the webrtc-adapter github repo yet, I'm firstly curious if anyone has any tips on how to tackle this issue. All the browsers are fully up to date. The clients are communicating from debian wheezy and Windows 10 (pro, creator's update edition). Works fine between the two machines if any combination of chrome and firefox are used.
According to this page https://msdn.microsoft.com/en-us/library/dn255005(v=vs.85).aspx it is possible to profile Web Worker code in Internet Explorer 11 (11.576.14393 in my case) Developer Tools (F12). But when I finish profiling, I can see only report from code running on main thread and threre is no Worker ID colum in the results as described on the mentioned page. Also, when I try to programatically start profiling from the Web Worker using Console.profile() method https://msdn.microsoft.com/en-us/library/jj152133(v=vs.85).aspx, I get error:
Object doesn't support property or method 'profile'
Do you have any clue what may be wrong? Do you please know how to profile Web Worker code in Internet Explorer?
PS: Same applies to Edge 38.14393.0.0. Rewriting the Web Worker code to run and profile it on main thread is not an option because it would take several months. The same code runs reasonably fast on Chrome and Firefox.
I tried to profile a simple web worker from the following demo
Web Worker Demo
It seems a bit weird but I was able to profile the worker only in the following scenario
I had started profiling the page and then started the worker and then stopped the worker and then stopped profiling.Exported the Data with Worker Id.
I had used IE11 in windows 7 environment.
Hope this helps :)
I have a Chrome Extension, Requestly which allows you manipulate HTTP Requests. 3-4 Users have faced an issue where Searching in Omnibox is Crashing the Google Search Results Page while rest of the pages work fine.
Please have a look at this Gif for more understanding.
Issue seems to be resolved by couple of ways:
Export Rules, Delete Rules, Restart Browser, Import Rules
Simply Restart Browser
Clearing Cache
This issue is reproducible on Ubuntu 14, Windows 8.1 Chrome 42. I have Ubuntu 12.10 Chrome 42 and I never saw this issue.
Here is the background.js code on Github. I am just wondering the cause of issue. I have used the following in my code
chrome.storage.sync
chrome.webRequest.onBeforeRequest (Blocking Option)
chrome.webRequest.onBeforeSendHeaders (Blocking Option)
I have observed another Chrome Extension, Scritsafe is facing the same issue. Details mentioned in this thread but the users are still not able to completely get rid of this bug.
One of the kind and helpful user gave me this information by enable logging while launching Chrome but I am not sure if these logs are helpful. These are the logs:
[13753:13788:0515/203052:WARNING:spdy_session.cc(2373)] Received HEADERS for invalid stream 7
[13753:13788:0515/203052:WARNING:spdy_session.cc(2373)] Received HEADERS for invalid stream 11
[133,3746404608:17:30:52.858104] Native Client module will be loaded at base address 0x0000702d00000000
[13753:13788:0515/203058:WARNING:spdy_session.cc(2373)] Received HEADERS for invalid stream 17
[13753:13788:0515/203210:WARNING:spdy_session.cc(2373)] Received HEADERS for invalid stream 55
[13791:13791:0515/173212:WARNING:ipc_message_attachment_set.cc(37)] MessageAttachmentSet destroyed with unconsumed descriptors: 0/1
Main problem is I am not able to manifest this on my machine. If I am able to manifest this, I would certainly try some random things and figure this out.
I have done enough Google Research. Now How should I approach to fix this issue ?
Edit:
Clone of this question is also available in Google Chrome Extension Forum. Simon Knott has also faced the same problem/bug.
He mentioned to avoid blocking all requests (Avoid especially XHR).