search

Sashasagan / lwuitgauthj2me

Automatically exported from code.google.com/p/lwuitgauthj2me
0 stars 0 forks source link

Problem with nokia N72 #6

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Start the installation from the .jar file

What is the expected output? What do you see instead?
Instead of any further prompts, I get the error message "Unable to install. 
Invalid version."

What version of the product are you using? On what operating system?
I'm using a Nokia N72 running Symbian S60.

Please provide any additional information below.
So, when this failed, I tried installing from the .jar file attatched to this 
comment: http://code.google.com/p/lwuitgauthj2me/issues/detail?id=3#c7.
This time, the app was installed successfully. But when I open it, I get a pop 
up saying "java.lang.NullPointerException". I can see the app's home screen in 
the background though.
Next, I downloaded the original version of the app, unzipped it and edited the 
MANIFEST.MF file myself(as explained to do in the above comment), re-zipped all 
the files, renamed the zip to jar and then tried to install it on my phone. 
This time it did ask me a couple of things like where I wanna install the file 
etc., but then, before the actual installation starts, it says, "Authorization 
failed". Any ideas as to what I should do?

Original issue reported on code.google.com by mohakvs...@gmail.com on 1 Feb 2012 at 1:22

GoogleCodeExporter commented 8 years ago 
According to 
http://www.developer.nokia.com/Community/Discussion/showthread.php?73793-quot-Au
thorization-failed-quot-message-displayed-when-installing-jar-file there might  
be a lack of support of API's lwuitgauhtj2me is using by your phone. I removed 
every unnecessary api from the manifest file. I hope this will do the trick.

Original comment by Rafael.B...@gmail.com on 6 Feb 2012 at 4:18

Attachments:

GoogleCodeExporter commented 8 years ago 
Doesn't work. I am still getting "java.lang.NullPointerException". Thanks for 
trying though.

Original comment by mohakvs...@gmail.com on 6 Feb 2012 at 5:42

GoogleCodeExporter commented 8 years ago 
It was worth a try. To fix this specific exception one would need to debug the 
app on the mobile phone itself.....

Original comment by Rafael.B...@gmail.com on 6 Feb 2012 at 10:11

GoogleCodeExporter commented 8 years ago 
Alright. Thanks again.

Original comment by mohakvs...@gmail.com on 11 Feb 2012 at 4:56