Android showWebPopUp crashes app under some unknown situation...

Solar2D Android
#1

I’ve read through all the other forum posts regarding webpopup issues and this seems to be slightly different…
I created a basic android app with the following 4 lines of code in main.lua:

display.setStatusBar (display.HiddenStatusBar)  
local authURL = "http://m.facebook.com/login.php"  
myFBWeb = native.showWebPopup(1, 30, 478, 290, authURL)  
temp\_textfield = display.newText("TEMP",0,0, "Arial", 20)

1/ If you enter a valid account email into the first box and press return/go/enter on the keyboard it crashes the whole app.

2/ If you put an invalid (non facebook registered) email in and press the same in behaves as expected.

3/ If you use the login button on the page, then it seems to behave as expected.

So it seems to be a very specific case…
This works correctly through the devices built in browser, so I can only imagine that the corona implimentation of the webpopup is crashing on some returned error code in a header response?

Tested on:
HTC Desire
HTC Desire HD
HTC Wildfire

If anyone can see a workaround that would be great!

Thanks!

Mal [import]uid: 13758 topic_id: 11883 reply_id: 311883[/import]

#2

Update: it appears that the “log in” button also causes crashes on a frequent basis.
Sometimes even with a valid email and password…

Thanks [import]uid: 13758 topic_id: 11883 reply_id: 43349[/import]

#3

OK I’ve nailed the error scenario down completely now so it is fully reproducible.

If you submit the login form on facebook with a correct username/email, and no password or an incorrect password, then something that is returned causes the app to crash / fail.

Many users press the return key to try moving fields - this acts as submit on the form (I know in this case it is outside of our/Ansca control how the web form reacts.)

I know there are existing facebook APIs but these currently cause issues with various facebook apps installed on the device.

We have tested with the last stable build of corona and a couple of recent nightly builds. [import]uid: 13758 topic_id: 11883 reply_id: 43380[/import]

#4

Daily Build 561 should fix your problem.

There is one small bug with the build that deals with device orientation. The screen will auto-rotate when the device is rotated if you don’t have a build.settings file with an orientation table specifying the allowed orientation modes.

orientation= { default="portrait", supported={"portrait"}, }, [import]uid: 7559 topic_id: 11883 reply_id: 43507[/import]

#5

Confirmed as fixed in the 561 update - many thanks!

[import]uid: 13758 topic_id: 11883 reply_id: 43529[/import]