native.showAlert, still buggy?

I know there has been issue with native.showAlert in iOS, but according to the notes in Daily Build it was fixed in December. However, I still struggle. The code runs OK for Android, both simulator and device.

This is the code that fails in iOS,

local function networkListener( event ) if ( event.isError ) then print( "Network error!") native.showAlert("GEOREG", "Nettverksfeil, er dataforbindelse aktivert?", {"OK"}) else print ( "RESPONSE: " .. event.response ) native.showAlert("GEOREG", event.response, {"OK"}) end timer.performWithDelay(10, function() network.cancel( requestID ); end) buttonEnable = true end

However, replacing event.respons in native.showAlert with the hardcoded text in event.response makes the code run,

local function networkListener( event ) if ( event.isError ) then print( "Network error!") native.showAlert("GEOREG", "Nettverksfeil, er dataforbindelse aktivert?", {"OK"}) else print ( "RESPONSE: " .. event.response ) native.showAlert("GEOREG", "Du er ikke registrert i systemet. For registrering, gå til http://www.georeg.no og trykk Registrere.", {"OK"}) end timer.performWithDelay(10, function() network.cancel( requestID ); end) buttonEnable = true end

When the code fails, I get the following message in the console window,

jan. 05 07:55:41.384 RESPONSE: Du er ikke registrert i systemet. For registrering, gå til http://www.georeg.no og trykk Registrere. jan. 05 07:55:41.390 2016-01-05 19:55:41.389 Corona Simulator[11548:164630] \*\*\* Assertion failure in -[NSTextFieldCell \_objectValue:forString:errorDescription:], /Library/Caches/com.apple.xbs/Sources/AppKit/AppKit-1404.34/AppKit.subproj/NSCell.m:1684

I think it is an internal iOS issue, but can anybody help me with a workaround? I use Corona build 2802.

Not much response here, but I found the reason myself.

It is the Nordic character “å” which creates the problem. This was coded wrongly from the server. Changing the coding to UTF-8 makes it run OK.

Not much response here, but I found the reason myself.

It is the Nordic character “å” which creates the problem. This was coded wrongly from the server. Changing the coding to UTF-8 makes it run OK.