Version 0.5 crashes on load about bowser

[superdump]

What device are you using? It seems to work fine on my iPhone 6 Plus

[stefhak]

Works on my iPhone 5S as well FWIW.

On Thu, May 21, 2015 at 2:54 PM, Robert Swain [email protected]
wrote:

What device are you using? It seems to work fine on my iPhone 6 Plus

—
Reply to this email directly or view it on GitHub
#45 (comment)
.

[mostafar]

I had the same experience on iPad with iOS 8.1.1

[superdump]

@mostafar - which iPad?

My suspicion is that older devices struggle to process the language bindings resource-wise. We had added pre-generated language bindings to the app bundle I thought, which should have sped up first start and avoided such problems.

[mostafar]

iPad (first gen), now after some tries I think it crashes less than a second after initialization is finished, I can see the url in the box for one second.

[zevarito]

I've noticed that if I type an url (which should redirect to https) without
including https:// I get "Frame error", but if I indeed include https:// in
the url input box it works.

On Thu, May 21, 2015 at 1:29 PM, Mostafa Rokooie [email protected]
wrote:

iPad (first gen), now after some tries I think it crashes less than a
second after initialization is finished, I can see the url in the box for
one second.

—
Reply to this email directly or view it on GitHub
#45 (comment)
.

Alvaro

[mostafar]

Thanks @zevarito but, I can not change the url because it crashes on start, and the url is the default url (openwebrtc.io/bowser)!

[superdump]

A first generation iPad is very likely really going to struggle with real-time audio/video even in optimal circumstances.

In order to add WebRTC support to a UIWebView from outside of the iPhone platform SDK has led us to use a suboptimal rendering method where all video frames are decided to bitmaps which are then displayed by the UIWebView as images, just that the image is updated rapidly. That is, Bowser is not optimal.

You may be able to use the WebRTC data channel though. :)

Regardless, this crash issue is a real issue.

[mostafar]

Thank you guys for creating the Bowser, Actually I am not experienced in WebRTC and iOS and even apple devices, I am a web and low-level developer. Just was trying to make sure one of my customers can use my QR-Code scanner using his iPhone.

The weird thing for me is when I was trying Bowser on this brand-new iPad (1st gen) yesterday, everything was fine, and I was able to work with my online QR-Code scanner tool (unless some errors in rendering the page). But now after installing some random apps and enabling Siri on the iPad, the Bowser crashs!

By the way I think my customer may be still able to use Bowser on his iPhone 5 to work with my website.

[pachpage]

I am using an iPhone 4S with iOS 8.3. Upon further testing, I found that if I launch Bowser from the home screen, it first says "Initializing: Please wait..." After that dialog fades, it starts to load the previously opened page (in my case, http://www.openwebrtc.io). Almost immediately, the app crashes. However, if after the dialog disappears I start repeatedly pressing the reload button, it alerts me with" Bowser has a problem: The operation couldn't be completed. (WebKitErrorDomain error 101.)" When I click close, the app works fine.

Using the "bowser://" URL scheme still doesn't work, though.

[mostafar]

Oh, I just found out the new version 0.5 is released today! So it answers my question why it was working yesterday, maybe I need to find a way to install version 0.4!

[iachimoe]

I'm also having this problem on 3rd generation iPad. Would appreciate a fix!

[mostafar]

I just received a feedback from my customer, he tested Bowser on three different iPhones (5 and 5s), and has the same problem.

[superdump]

We will investigate tomorrow.

[superdump]

We have managed to reproduce all of the above on an iPad 2. We will investigate further as soon as we can.

[superdump]

I have identified the issue as likely being a problem with armv7 libffi. armv7s and arm64 seem to work fine.

https://gist.github.com/superdump/996d8550beaf491c99e3

Tracking it in the main OpenWebRTC repository here: EricssonResearch/openwebrtc#385

[ekoome]

Getting a crash on iPhone 5. Takes a while to initialise. When done, when I click the address bar, it crashes. On iOS 8.1.3

[unanimous1]

Bowser (from App Store) crashes on iPad mini while trying to initialize. (Running latest iOS)

[pearcetm]

I'm having the the crash-after-opening problem on an iPhone 5. Downloaded today from the Apple AppStore. I just updated iOS, no fix to the problem (though the app stays open maybe 1-2 extra seconds before crashing than it did before the update).

[pearcetm]

Just tried on an iPhone 5s - same problem.

[stefhak]

I just tried 0.5 on my iPhone 5s, and it works FWIW.

On Sat, Jun 6, 2015 at 1:55 AM, pearcetm [email protected] wrote:

Just tried on an iPhone 5s - same problem.

—
Reply to this email directly or view it on GitHub
#45 (comment)
.

[superdump]

The 5S is ARM64 so that should be fine. I'm still trying to find libffi that builds with the current Xcode/iOS SDK and works on ARMv7/ARMv7S

[pearcetm]

To follow-up from a couple of comments ago, the 5s that was having problems with Bowser had very little disk space left. After freeing up space, Bowser loads without crashing. So as others have reported, only the 5 (and presumably below) is having trouble.

[unanimous1]

The iPad mini fails. Even with disk space cleared. It dies on boot of Bowser.

[varunFX]

trying out in ipad mini, same problem here. crashes on initialization.

[superdump]

I have been testing libffi versions for a few weeks that used to work on armv7 / armv7s and I have so far been unable to find anything that works anymore. I suspect something has been broken as a consequence of an Xcode upgrade.

EricssonResearch/openwebrtc#385 <--- someone reported that they got something working there but I have been unable to get the same changes to work here.

[RichardNeill]

It's failing for me on both iPad mini and iPad 3 (updated to most recent iOS 8.4).
Is there anything I can do to help?

[superdump]

I spent a few weeks trying many different libffi versions and those that supposedly worked for armv7 seemed to have stopped working or no longer built.

Libffi needs fixing so that it builds and works correctly on armv7, armv7s and arm64 for iOS

[iachimoe]

Any news on this? It's starting to feel like I won't get to use WebRTC on iOS until such time as I buy a new iDevice :-)

[superdump]

I need to re-test the various libffi versions with iOS SDK 8.4 to see if that helps anything.

[brentgreyling]

Nice work.... Same question, any progress on this? I'm failing on Bowser 0.5 with ios 8.3 on iPhone 5.

[ageekhere]

This has been one bad bug :(

[superdump]

I agree and I have spent a lot of time on it already trying to find a version of libffi that builds and works on armv7 but have not yet succeeded.

It will at least get less bad with time as more people upgrade to 64-bit CPUs.

[stefanalund]

I think there is an option in iOS 9 to only support 64-bit devices. Even if that leaves a lot of devices out, it is perhaps a more honest approach until we have resolved this issue.

[Firegarden]

Dear God please fix this bug. We can't use bowser anymore after upgrading to ios 9.

[stefanalund]

@Firegarden are you sure this is the same issue? I can start Bowser on my iPhone 5s (64-bit device) running iOS 9. Please file a separate Issue on iOS 9 compatibility otherwise.

[Firegarden]

OK absolutely iPad Air 2 16GB does not work after upgrading to ios 9.-1

so there you have it I need to open a ticket but Im 2 busy coding 4 life
feel me. Tupac is 4 real.

On Sun, Sep 20, 2015 at 7:44 PM, Stefan Ålund [email protected]
wrote:

@Firegarden https://github.com/Firegarden are you sure this is the same
issue? I can start Bowser on my iPhone 5s (64-bit device) running iOS 9.
Please file a separate Issue on iOS 9 compatibility otherwise.

—
Reply to this email directly or view it on GitHub
#45 (comment)
.

FIREGARDEN https://www.google.com/?q=firegarden
1877.222.7818

[stefanalund]

This has been fixed in a updated version of OpenWebRTC. Let us know if you still have problems after re-building latest OpenWebRTC from master. Closing.

[abhijitmehta]

I get crash in iphone 6 ios 10 - is this known issue ?