search

lukeme / gobible

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

Error opening the GoBible 2.4.3 for Nokia E50 #163

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
When you open the Bible created by GoBibleCreator V2.4.3 for Windows XP and 
Windows 7, gives an error
java.lang.Error:
ClassFormatError: 40

When created by GoBibleCreator V2.4.1 had no problems.

Phone: Nokia E50, RM-171 firmware V07.36.0.0, Symbian OS 9.1

Sorry, I do not know English. Google translate
I know Russian and Ukrainian.

Original issue reported on code.google.com by lastavtc...@gmail.com on 25 Jan 2012 at 9:42

GoogleCodeExporter commented 8 years ago 
You're the first to report this issue.

The software changes in v2.4.3 are detailed in the file called 
GBC_2.4_Readme.txt

Briefly:

GoBibleCreator 2.4.3 Notes 
December 8, 2011

GoBibleCreator updated as follows.
 BUG FIX: (Issue 161 follow-up - see below)
  - Fix applied also to \ndx_...\ndx*, \wg_...\wg*, \wh_...\wh*

GoBibleCreator 2.4.2 Notes 
November 28, 2011

GoBibleCreator updated as follows.
 BUG FIX: (Issue 161)
 - To ensure the correct processing of the USFM tag pair \w_...\w* 
   such that tagged glossary words are not deleted in error.

 ENHANCEMENTS: (User Interface properties)
 - Supports the UI-Digits property in collections files (issue 24)
 - Allows remark lines beginning with # in ui.properties
   Facilitates grouping of properties as an aid for UI translation

GoBibleCore updated with some minor improvements:
------------------------------------------------
 - Java classes no longer have obfuscated file names
   Previous obfuscation deemed pointless for open source software
 - Updated ui.properties - this now includes:
    (a) Remark lines with properties grouped according to context
    (b) New properties in anticipation of the SymScroll branch
 - Updated MANIFEST.MF with more sensible defaults
 - Viewer Version updated to 2.4.2

=================================================== 
A possible (but unlikely) scenario is that the Nokia phone does not like the 
comment lines within the internal ui.properties file. 

It's possible to test this by replacing the ui.properties file within the 
created JAR file. You can open the file with 7-Zip - a free archive utility.

If you extract the ui.properties file from the Go Bible you made using v2.4.1 
and drop that into the Go Bible you made using v2.4.3, the results would be of 
considerable interest to the developer.

If this gives no solution, then I've no idea what may be happening.

Maybe our programmer can shed some light on the issue?

Original comment by DFH...@gmail.com on 26 Jan 2012 at 8:30

GoogleCodeExporter commented 8 years ago 
http://www.developer.nokia.com/Community/Discussion/showthread.php?73443-ClassFo
rmatError

Will obfuscate the code for release.

Original comment by daniel.s...@gmail.com on 26 Jan 2012 at 5:16

GoogleCodeExporter commented 8 years ago 
lastavtchouk,

http://translate.google.com/

Please see the attached file. (GoBibleCore2-obfuscated.jar)

Replace "GoBibleCore/GoBibleCore2.jar" with the above, and try again.

Original comment by daniel.s...@gmail.com on 26 Jan 2012 at 5:57

Attachments:

GoogleCodeExporter commented 8 years ago 
It works!
Thanks for your help.

Original comment by lastavtc...@gmail.com on 27 Jan 2012 at 9:36

GoogleCodeExporter commented 8 years ago 
should obfuscation therefore be a standard practice? This is really a
Nokia bug, not a feature.

Original comment by daniel.s...@gmail.com on 27 Jan 2012 at 12:25

GoogleCodeExporter commented 8 years ago 
Daniel,

Although this is a Nokia bug, if the workaround is to implement obfuscated 
class names, then we should do that, merely in order to forestall further 
reports of the same problem from other users of GoBibleCreator.

A new release of the trunk is therefore called for, and it should also become 
standard practice for the SymScroll branch as well as the trunk.

Once the new release has been made, I will update the file GBC_2.4_Readme.txt 
and package the download for the trunk.

I will also remake all the GoBible apps that have been built using GBC_v2.4.3 
during the last few weeks.

David

Original comment by DFH...@gmail.com on 28 Jan 2012 at 12:10

GoogleCodeExporter commented 8 years ago 
I've still not got round to doing what I said in the previous comment.

Original comment by DFH...@gmail.com on 27 Jun 2012 at 5:00

GoogleCodeExporter commented 8 years ago 
Just discovered that for any Go Bible app made with version 2.4.3 with 
non-obfuscated names in gobiblecore2.jar - the Send SMS feature does not work.

This is the case for my Sony Ericsson K750i phone.

Original comment by DFH...@gmail.com on 25 Aug 2012 at 2:24

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Solution confirmed: Remade KJV Go Bible with obfuscated Java class names.
Send SMS functionality fully restored.

Also updated GBC_2.4_Readme.txt as follows:

August 26, 2012

GoBibleCore updated as follows.
 BUG FIX: (Issue 163 follow-up - see below)
 - Viewer Version 2.4.2 updated to use obfuscated Java class names
 - In January 2012, it became apparent that obfuscation is really necessary!
 - This is a long overdue corrective action that had been deferred for no reason whatsoever.
 - Apologies for any inconvenience caused by the delay.
 - N.B. The software revision number has not been changed!
 - i.e. Viewer Version remains as 2.4.2 despite the above change.

Original comment by DFH...@gmail.com on 26 Aug 2012 at 8:40

GoogleCodeExporter commented 8 years ago

Original comment by DFH...@gmail.com on 14 Dec 2012 at 2:11