J2ME build failed to run on Sony Ericsson (eg.W850i,K610i)

[codenameone]

Original issue 784 created by codenameone on 2013-07-16T04:32:41.000Z:

My J2ME build works on Nokia devices but failed on SE devices as it occured a message "Application error" and unable to launch the app. It used be fine on SE devices but now it doesn't work though on new created sample project.

What steps will reproduce the problem?
1.compile and send J2me build to server.
2.download the build and install to SE device
3.error message "application error" occurred after launching the app

What is the expected output? What do you see instead?
The app should be run successfully as it does on emulator/Nokia devices. Unfortunately, it fails and shows the error message when attempting to run the app.

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

Please provide any additional information below.

[codenameone]

Comment #1 originally posted by codenameone on 2013-07-16T04:57:56.000Z:

<empty>

[codenameone]

Comment #2 originally posted by codenameone on 2013-07-16T05:45:54.000Z:

What version of the product are you using? On what operating system?
netbeans 7.2, .OS X 10.8.3 , codenameone plugin 1.0.47

[codenameone]

Comment #3 originally posted by codenameone on 2013-07-16T15:05:48.000Z:

anyone with solution regarding this ? thanks.

[codenameone]

Comment #4 originally posted by codenameone on 2013-07-17T04:57:03.000Z:

Unfortunately since we don't have the physical device this will take some time to investigate.
Does this happen with a hello world application?
If not can you narrow down the cause within your application?
How big is your resulting application?

[codenameone]

Comment #5 originally posted by codenameone on 2013-07-17T06:07:52.000Z:

Hi Shai

Yes. It does happen to hello world app installed in SE devices but working fine on Nokia devices.
520kb

Thanks.

[codenameone]

Comment #6 originally posted by codenameone on 2013-07-17T11:05:14.000Z:

Chen just tested a build on an SE device we have and it worked for him, its a newer device though.
Since we don't have access to the device we will need some help debugging this. Can you install the Sony Ericsson SDK and connect the device to the SDK to get console access, do you get an error message in the console that is more detailed?

[codenameone]

Comment #7 originally posted by codenameone on 2013-07-26T04:19:39.000Z:

There is no error occurred running with SE sdk on simulator.

I didn make any changes and it used to work on devices. I found this issue actually happened on Nokia 206 as well that the message "Application error" showed up and crashed.

I had even tested with Hello world newly created project and got the same result. Wondering if the server added extra resources causing the crash?

[codenameone]

Comment #8 originally posted by codenameone on 2013-07-28T07:40:43.000Z:

My previous developed cn1 j2me applications no longer able to run on certain devices which used to be fine working. I strongly believe this issue was created by the changes in server to my j2me build.

Please help to resolve this issue asap. Thanks.

[codenameone]

Comment #9 originally posted by codenameone on 2013-07-28T08:04:30.000Z:

Sorry I missed your last comment. I don't need you to run the app in the SE simulator. The SE SDK supports connecting to the device so you can see the output from the application as it loads and crashes. You will need to connect your device with a cable to your computer then use an application from the SE SDK to see the printouts and stack traces from the device.
You should be able to see some information and you could possibly also add some printouts to help us understand what specifically is failing.

[codenameone]

Comment #10 originally posted by codenameone on 2013-08-13T09:40:30.000Z:

java.lang.NoClassDefFoundError
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at java.lang.Thread.run
at unknown
at unknown

This is the error message received in SE console when attempting to run the application,hopefully this can help to solve the issue. Thanks

[codenameone]

Comment #11 originally posted by codenameone on 2013-08-13T09:47:09.000Z:

Ugh.
Can you set the build argument j2me.obfuscation to false and check if that build will install/run (and if so it might produce a better stack) hopefully the file won't be too big to install.

[codenameone]

Comment #12 originally posted by codenameone on 2013-08-13T10:16:21.000Z:

file size gone up to 2.2mb without obfuscation and unable/failed to be installed into the mobile as become invalid application. Is that other way to trace it ?

[codenameone]

Comment #13 originally posted by codenameone on 2013-08-13T10:20:58.000Z:

Is 2.2m for a hello world or for your app?
I suggest trying to track the problem with a hello world app.

[codenameone]

Comment #14 originally posted by codenameone on 2013-08-14T02:03:07.000Z:

Yes..am using hello world and even removed the theme for debugging, it can't be installed into the handset.

[codenameone]

Comment #15 originally posted by codenameone on 2013-08-14T03:13:54.000Z:

my problem is exactly same as this issue https://groups.google.com/forum/#!topic/codenameone-discussions/EnD-ql1h80g.

what else can be done to track the issue ? Thanks.

[codenameone]

Comment #16 originally posted by codenameone on 2013-08-14T05:31:46.000Z:

Can you try this?
I just randomly removed packages so I might have broken something else though.

[codenameone]

Comment #17 originally posted by codenameone on 2013-08-14T06:43:26.000Z:

Tested and got the same result as failed to be installed. Have a check on the screenshots captured.
Thanks for your time.

[codenameone]

Comment #18 originally posted by codenameone on 2013-08-14T06:54:51.000Z:

I've tested on Nokia 206 as well and got the same result as invalid application and forced to be deleted.

[codenameone]

Comment #19 originally posted by codenameone on 2013-08-14T09:25:58.000Z:

Lets try this file

[codenameone]

Comment #20 originally posted by codenameone on 2013-08-14T09:37:31.000Z:

This jar can be installed yet the printout of application error is same as previous one.

Is this jar been obfuscated ?

[codenameone]

Comment #21 originally posted by codenameone on 2013-08-14T09:43:45.000Z:

<empty>

[codenameone]

Comment #22 originally posted by codenameone on 2013-08-14T09:43:49.000Z:

<empty>

[codenameone]

Comment #23 originally posted by codenameone on 2013-08-14T11:35:13.000Z:

Yes it has been obfuscated but with flags to keep most of the data in. I just added another flag for keeping more data in. Can you check that?
Thanks.

[codenameone]

Comment #24 originally posted by codenameone on 2013-08-15T02:24:48.000Z:

Printout :

java.lang.NoClassDefFoundError
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at java.lang.Thread.run
at unknown
at unknown

[codenameone]

Comment #25 originally posted by codenameone on 2013-08-16T02:50:01.000Z:

Tested and got the same result:
Printout :

java.lang.NoClassDefFoundError
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at unknown
at java.lang.Thread.run
at unknown
at unknown

[codenameone]

Comment #26 originally posted by codenameone on 2013-08-16T04:41:57.000Z:

I'll need to create a specifically tailored version which is something that will take some time/effort. I'm still looking into this.

[codenameone]

Comment #27 originally posted by codenameone on 2013-08-16T06:06:48.000Z:

Highly appreciate for the time and effort you put into fixing this issue.

[codenameone]

Comment #28 originally posted by codenameone on 2013-08-19T16:36:46.000Z:

I just made a server update with some fixes based on a tip from the discussion forum. Its a blind guess but I'm hoping it might be related to this and that I won't have to make a clean app. Can you please send a new test build and see if it works now?

[codenameone]

Comment #29 originally posted by codenameone on 2013-08-20T03:40:05.000Z:

Tested and unfortunately the issue remained.

I have attached a build compiled with previous version CN1 which works fine in all handsets.

Wondering if you can use it to detect the cause.

Thanks.

[codenameone]

Comment #30 originally posted by codenameone on 2013-08-20T04:15:11.000Z:

Damn.
Thanks, this won't help since the jar is obfuscated its impossible to see what's in it. Unfortunately a lot has changed so even if I could see the jar's contents properly this will be a needle in a haystack. I'll try another approach.

[codenameone]

Comment #31 originally posted by codenameone on 2013-08-23T15:54:27.000Z:

OK, here is another attempt this time with no obfuscation and some major pieces stripped out.
It would be great if you can get back to me fast on this (sorry for doing it just over the weekend) because I have a lot of local changes and if I need to change more it will be hard.

[codenameone]

Comment #32 originally posted by codenameone on 2013-08-26T02:34:38.000Z:

Sorry for late reply.
The jar cannot be installed into any handset as it turned into an invalid jar.
Can the jE size be further reduced ? Thanks.

[codenameone]

Comment #33 originally posted by codenameone on 2013-08-26T02:35:51.000Z:

Sorry for late reply.
The jar cannot be installed into any handset as it turned into an invalid jar.
Can the jar size be further reduced ? Thanks.

[codenameone]

Comment #34 originally posted by codenameone on 2013-08-30T03:33:38.000Z:

any progress regarding this issue ? Thanks.

[codenameone]

Comment #35 originally posted by codenameone on 2013-08-30T07:53:54.000Z:

This might take some time now. I'll have to recreate a J2ME environment and unfortunately September is a remarkably busy month for me (2 conferences).
I'm re-assigning this to Chen since I probably won't be able to follow up on this, he also has a better J2ME setup to test this on.

[codenameone]

Comment #36 originally posted by codenameone on 2013-08-30T09:04:48.000Z:

Thanks. Hopefully this issue can be resolved asap for my j2ME applications to run perfectly on all handsets.
Your time and efforts are greatly appreciated.

[codenameone]

Comment #37 originally posted by codenameone on 2013-09-11T09:04:56.000Z:

Any further progress regarding this issue ? Thanks.

[codenameone]

Comment #38 originally posted by codenameone on 2013-09-13T15:52:06.000Z:

This will take some time. Probably not this month. I was hoping that Chen would have the time to help on this but unfortunately there are other tasks of higher priority and I'm traveling making this pretty hard.

[codenameone]

Comment #39 originally posted by codenameone on 2013-10-02T01:49:04.000Z:

Okay. Thanks.

[codenameone]

Comment #40 originally posted by codenameone on 2013-10-11T02:33:42.000Z:

Hi.. any update for this issue ? Thanks.

[codenameone]

Comment #41 originally posted by codenameone on 2013-10-24T05:45:18.000Z:

Hi.. any update for this issue ? Thanks.

[codenameone]

Comment #42 originally posted by codenameone on 2013-11-01T01:52:00.000Z:

This issue still remained and causing application error on specific SE and Motorola handsets. Anyone still following this ?

Hope to get this work for my j2me projects. Thanks.

[codenameone]

Comment #43 originally posted by codenameone on 2013-11-04T18:46:54.000Z:

Hi Ander. Sorry for the delay with this. Can you check this file.

[codenameone]

Comment #44 originally posted by codenameone on 2013-11-05T06:02:20.000Z:

Hi Shai. This jar size is way too big as invalid jar to be installed onto my handsets.

I've just compiled my j2me builds with CN1 version 1.1 under premium features and it works prefectly now.

Wondering if i should not bothering with the latest version for my j2me builds.

[codenameone]

Comment #45 originally posted by codenameone on 2013-11-05T06:17:36.000Z:

You would probably want to keep moving forward, we will eventually drop support for 1.1. Currently for pro users we guarantee 2 versions back support and we are now coming out with a new version. Enterprise versions get more but even then you would eventually have a problem.
What is the maximum jar size for the device?
Looking at the specs http://www.mobileheart.com/cell-phone-reviews/sony-ericsson-3/sony-ericsson-W850i-438.aspx it seems to have no limitation of jar size?

[codenameone]

Comment #46 originally posted by codenameone on 2013-11-05T08:00:37.000Z:

It stated no limit but all my feature handsets rejected it as invalid jar during installation.

[codenameone]

Comment #47 originally posted by codenameone on 2013-11-05T09:05:26.000Z:

Does it install on slightly newer devices?
If you just send a working build but add some text files (or images) to make it 1.8mb in size would that install?
If not would it give the same error.

[codenameone]

Comment #48 originally posted by codenameone on 2013-11-18T11:37:21.000Z:

I just made a fix to the current server that might resolve this issue. Can you see if builds work with the current trunk version?

[codenameone]

Comment #49 originally posted by codenameone on 2013-11-19T13:05:34.000Z:

<empty>

[codenameone]

Comment #50 originally posted by codenameone on 2013-11-21T14:27:07.000Z:

Issue 775 has been merged into this issue.