[jitsi-dev] Jitsi Meet in Chrome on IOS 8


#1

Hi,

We were testing Jitsi Meet and it seemed to work in Chrome on Android
however a user on IOS 8 only got the the "This application is currently
only supported by Chrome..." page.

Is this a know issue?, anyone tried on IOS 8?

I notice in the user agent string that it does not include "Chrome" but
says "CriOS", could this be the issue?

···

---
Mozilla/5.0 (iPhone; CPU iPhone OS 8_1_3 like Mac OS X)
AppleWebKit/600.1.4 (KHTML, like Gecko) CriOS/40.0.2214.73 Mobile/12B466
Safari/600.1.4
---

Cheers,
Markus


#2

Probably not. We don't use the UA string, but check whether certain WebRTC objects are defined. See here:
https://github.com/jitsi/jitsi-meet/blob/master/modules/RTC/RTCUtils.js#L159

Could it be that the Chrome version you are running doesn't support WebRTC?

Regards,
Boris

···

On 19/02/15 16:34, Markus Kilås wrote:

Hi,

We were testing Jitsi Meet and it seemed to work in Chrome on Android
however a user on IOS 8 only got the the "This application is currently
only supported by Chrome..." page.

Is this a know issue?, anyone tried on IOS 8?

I notice in the user agent string that it does not include "Chrome" but
says "CriOS", could this be the issue?


#3

We were testing Jitsi Meet and it seemed to work in Chrome on Android
however a user on IOS 8 only got the the "This application is currently
only supported by Chrome..." page.

Android's Chrome actually uses the Blink engine, a fork of WebKit, which includes all the WebRTC stuff. Safari, which all "Browsers" on iOS are required to use as their engine, does not support WebRTC (yet?). So as long as Safari does not support WebRTC, neither of the alternative "Browsers" will.

Is this a know issue?, anyone tried on IOS 8?

I notice in the user agent string that it does not include "Chrome" but
says "CriOS", could this be the issue?

--- Mozilla/5.0 (iPhone; CPU iPhone OS 8_1_3 like Mac OS X)
AppleWebKit/600.1.4 (KHTML, like Gecko) CriOS/40.0.2214.73 Mobile/12B466
Safari/600.1.4 ---

Cheers,
Markus

Ingo


#4

I wonder how Bowser worked around this.

--sent from my mobile

···

On Thursday, February 19, 2015, Ingo Bauersachs <ingo@jitsi.org> wrote:

> We were testing Jitsi Meet and it seemed to work in Chrome on Android
> however a user on IOS 8 only got the the "This application is currently
> only supported by Chrome..." page.

Android's Chrome actually uses the Blink engine, a fork of WebKit, which
includes all the WebRTC stuff. Safari, which all "Browsers" on iOS are
required to use as their engine, does not support WebRTC (yet?). So as long
as Safari does not support WebRTC, neither of the alternative "Browsers"
will.

> Is this a know issue?, anyone tried on IOS 8?
>
> I notice in the user agent string that it does not include "Chrome" but
> says "CriOS", could this be the issue?
>
> --- Mozilla/5.0 (iPhone; CPU iPhone OS 8_1_3 like Mac OS X)
> AppleWebKit/600.1.4 (KHTML, like Gecko) CriOS/40.0.2214.73 Mobile/12B466
> Safari/600.1.4 ---
>
> Cheers,
> Markus

Ingo

_______________________________________________
dev mailing list
dev@jitsi.org <javascript:;>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
--sent from my mobile


#5

I wonder how Bowser worked around this.

Good question. Maybe it's possible to create hooks into the WebKit engine and implement all the necessary WebRTC functionality.
https://github.com/EricssonResearch/bowser/wiki/Developing-for-Bowser states that User-Agent string and contains AppleWebKit, so I doubt they actually provide a whole engine. But at least it seems possible, so maybe Chrome will follow at some point despite my doubts...

Ingo


#6

Bowser launches gstreamer on the background, that accesses the cam and
sends streams to the Safari. It can also be tested on macos, using
safari plugin and compiled openwebrtc (it's easier to debug in such
way).
It supports multistream [1] and will possibly support simulcast [2].
It will be pretty useful to have jitsi-meet supported there. I tried
it before, and was able to get the localstream, but didn't manage why
the jingle connection wasn't established.

[1] http://iswebrtcreadyyet.com/
[2] http://www.openwebrtc.io/blog/2015/1/15/roadmap-for-2015

Regards,
Zalmoxisus

···

On Thu, Feb 19, 2015 at 6:12 PM, Emil Ivov <emcho@jitsi.org> wrote:

I wonder how Bowser worked around this.

--sent from my mobile

On Thursday, February 19, 2015, Ingo Bauersachs <ingo@jitsi.org> wrote:

> We were testing Jitsi Meet and it seemed to work in Chrome on Android
> however a user on IOS 8 only got the the "This application is currently
> only supported by Chrome..." page.

Android's Chrome actually uses the Blink engine, a fork of WebKit, which
includes all the WebRTC stuff. Safari, which all "Browsers" on iOS are
required to use as their engine, does not support WebRTC (yet?). So as long
as Safari does not support WebRTC, neither of the alternative "Browsers"
will.

> Is this a know issue?, anyone tried on IOS 8?
>
> I notice in the user agent string that it does not include "Chrome" but
> says "CriOS", could this be the issue?
>
> --- Mozilla/5.0 (iPhone; CPU iPhone OS 8_1_3 like Mac OS X)
> AppleWebKit/600.1.4 (KHTML, like Gecko) CriOS/40.0.2214.73 Mobile/12B466
> Safari/600.1.4 ---
>
> Cheers,
> Markus

Ingo

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
--sent from my mobile

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev