native.newTextField causes crash on relaunch

Solar2D Android
#1

After exiting the app containing a native.newTextField, the app will crash on relaunch. Only tested on Android. This does not happen if the app is suspended via the home button then closed via the task manager. The attached crash log contains 2 runs of an app com.test.test (test.apk). The 1st run being successful and the 2nd being the crash. I have also tried removeSelf on the textfield on applicationExit just in case with no effect. Does not occur in simulator, but does occur on Samsung Galaxy S2 running Android 4.0

Blank project. Add a native.newTextField. Quit the app either via back button or from within the app via native.requestExit. On the next app opening, you will be presented with a blank screen and the app will eventually crash.

http://pastebin.com/B4KCr5gk (also tried with removeSelf against textfield on applicationExit)

Filed a bug report. [import]uid: 204816 topic_id: 36351 reply_id: 336351[/import]

#2

PS: This is with Corona build 2013.1036 and I attached the log file to the bug report not to this - lol.

Edit: Apologies didn’t notice the bug reports forum. [import]uid: 204816 topic_id: 36351 reply_id: 144381[/import]

#3

A further update. I have now tested on another Galaxy S2 running 4.0.2 which produces the same results. I have also tested on a Nexus 10 running 4.2.2 and it does NOT happen on this. [import]uid: 204816 topic_id: 36351 reply_id: 144416[/import]

#4

Credit where its due! Corona has just emailed me to advise they have resolved this bug and it will be fixed in the next daily build. What a brilliant response time. [import]uid: 204816 topic_id: 36351 reply_id: 144458[/import]

#5

PS: This is with Corona build 2013.1036 and I attached the log file to the bug report not to this - lol.

Edit: Apologies didn’t notice the bug reports forum. [import]uid: 204816 topic_id: 36351 reply_id: 144381[/import]

#6

A further update. I have now tested on another Galaxy S2 running 4.0.2 which produces the same results. I have also tested on a Nexus 10 running 4.2.2 and it does NOT happen on this. [import]uid: 204816 topic_id: 36351 reply_id: 144416[/import]

#7

Credit where its due! Corona has just emailed me to advise they have resolved this bug and it will be fixed in the next daily build. What a brilliant response time. [import]uid: 204816 topic_id: 36351 reply_id: 144458[/import]

#8

PS: This is with Corona build 2013.1036 and I attached the log file to the bug report not to this - lol.

Edit: Apologies didn’t notice the bug reports forum. [import]uid: 204816 topic_id: 36351 reply_id: 144381[/import]

#9

A further update. I have now tested on another Galaxy S2 running 4.0.2 which produces the same results. I have also tested on a Nexus 10 running 4.2.2 and it does NOT happen on this. [import]uid: 204816 topic_id: 36351 reply_id: 144416[/import]

#10

Credit where its due! Corona has just emailed me to advise they have resolved this bug and it will be fixed in the next daily build. What a brilliant response time. [import]uid: 204816 topic_id: 36351 reply_id: 144458[/import]

#11

PS: This is with Corona build 2013.1036 and I attached the log file to the bug report not to this - lol.

Edit: Apologies didn’t notice the bug reports forum. [import]uid: 204816 topic_id: 36351 reply_id: 144381[/import]

#12

A further update. I have now tested on another Galaxy S2 running 4.0.2 which produces the same results. I have also tested on a Nexus 10 running 4.2.2 and it does NOT happen on this. [import]uid: 204816 topic_id: 36351 reply_id: 144416[/import]

#13

Credit where its due! Corona has just emailed me to advise they have resolved this bug and it will be fixed in the next daily build. What a brilliant response time. [import]uid: 204816 topic_id: 36351 reply_id: 144458[/import]