Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bowser is not recognized as a browser able to support WebRTC #251

Closed
fbartels opened this issue Jan 13, 2016 · 11 comments
Closed

Bowser is not recognized as a browser able to support WebRTC #251

fbartels opened this issue Jan 13, 2016 · 11 comments

Comments

@fbartels
Copy link

Hi,

I am not quite sure if this is a problem in spreed-webrtc or maybe even in Bowser itself, but wanted to report it here first.

Bowser is an iOS browser made specially to support WebRTC:
http://www.openwebrtc.org/bowser/ & https://github.com/EricssonResearch/bowser

But sadly when opening for example spreed.me on bowser there is an error message that the current browser does not support WebRTC. I traced the error message back to:

if (!$window.webrtcDetectedVersion || $window.webrtcDetectedBrowser === "edge") {

This seems to be a general check, so it could be that Bowser is not announcing support correctly.

What do you think?

Was also reported on the Zarafa forums: https://forums.zarafa.com/showthread.php?12167-iOS-Browsers-Not-Recognized

@leonklingele
Copy link
Contributor

This issue likely has been fixed in the latest release 0.24.9.
It seems you're still running 0.24.8?

@fbartels
Copy link
Author

I tried it on spreed.me which announces itself as 0.24.9

@longsleep
Copy link
Contributor

Currently Bowser is not on the list of supported browsers. Bowser has many issues and fails to load the web client properly. See https://github.com/strukturag/spreed-webrtc/wiki/Supported-Browsers-and-Errata

@leonklingele - Webrtc adapter does not support Bowser (neither the old nor the current version)

@fbartels
Copy link
Author

Hi Simon,

thanks for the update.

@longsleep
Copy link
Contributor

I am willing to try to get support for Bowser into Spreed WebRTC. On Spreed.ME it will not work, until Bowser has fixed the Javascript injection to work on sites which use a CSP (see EricssonResearch/bowser#74)

@longsleep
Copy link
Contributor

The UI breackage fix for Bowser has landed in https://github.com/strukturag/spreed-webrtc/releases/tag/v0.24.10 and was deployed to Spreed.ME - so at least the UI should no longer be broken. Sill Bowser will not work, because of the insecure Javascript injection.

@longsleep
Copy link
Contributor

@fbartels Seems like a fix has landed in Bowser EricssonResearch/bowser#72 and they seem to think that it should work now. Do you have a way to test?

@fbartels
Copy link
Author

Interesting. So far I don't see the upgrade to 0.6.1, I will try again against the spreed.me server once I have the update.

@fbartels
Copy link
Author

Hi Simon,

I just retried with Bowser 0.6.1 and the server at spreed.me (wich reports to be at 0.24.10). Sadly there is still the popup when accessing the server that the browser does not support calls (writing chats is possible though).

@longsleep
Copy link
Contributor

@fbartels yes - they have reopened EricssonResearch/bowser#74 - it seems that they want us to test something. Maybe you could have a look?

@longsleep
Copy link
Contributor

Closing this for now. We will take another look at Bower once it has evolved more and supports restrictive CSPs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants