On j2me phone entering * key for symbol table causes null pointer exception

codenameone / CodenameOne

Cross-platform framework for building truly native mobile apps with Java or Kotlin. Write Once Run Anywhere support for iOS, Android, Desktop & Web.

https://www.codenameone.com/

Other

1.71k stars 408 forks source link

On j2me phone entering * key for symbol table causes null pointer exception #410

Closed codenameone closed 9 years ago

codenameone commented 9 years ago

Original issue 410 created by codenameone on 2012-11-29T14:44:57.000Z:

Please clearly state whether the issue relates to a device/the simulator or the tools.

Real device

If related to a device be sure to specify exactly which device with as much details as possible.

Nokia C2-01 phone.

What steps will reproduce the problem?

Have a textField with ANY or EMAIL constraint.
Then when you try to enter a symbol using the * key in j2me phone, it causes null pointer exception. 3.

What is the expected output? What do you see instead?

The symbol table should be shown. Instead we see a null pointer exception.

What version of the product are you using? On what operating system?

codename one plugin 1.0.24

Please provide any additional information below.

Video showing the problem is attached.

codenameone commented 9 years ago

Comment #1 originally posted by codenameone on 2012-11-29T15:11:43.000Z:

Weird, I looked at the code and don't see anything that changed there for ages.

codenameone commented 9 years ago

Comment #2 originally posted by codenameone on 2012-12-01T10:32:00.000Z:

I tried to run the jar file on J2ME simulator and there also it is causing null pointer exception on * key. I have pasted the console output from the WTK toolkit.

/Applications/Java_ME_SDK_3.0.app/Contents/Resources/bin/emulator -Xdevice:DefaultCldcPhone1 -Xdescriptor:/Users/nirmal/tmp/cn1-gen-src/j2me/result/S2PayApp.jar

Installing suite from: http://127.0.0.1:50457/S2PayApp.jar java.lang.NullPointerException: 0

bz.a(), bci=69
bz.a(), bci=4
bz.M(), bci=73
bz.aA(), bci=2
bz.a(), bci=198
bz.a(), bci=11
bz.a(), bci=9
bz.a(), bci=7
bz.a(), bci=7
cz.bv(), bci=32
cz.a(), bci=548
cz.keyReleased(), bci=51
ce.keyReleased(), bci=61
ca.c(), bci=110
ca.aG(), bci=131
ca.aF(), bci=243
cr.run(), bci=242
n.run(), bci=4

It seems the problem in happening in a method of Dialog class. I have attached the built app's jar/jad file and obfuscation_mapping file for your reference.

codenameone commented 9 years ago

Comment #3 originally posted by codenameone on 2012-12-02T13:36:38.000Z:

thanks it is now fixed in the repository, will be available in the next server update