IOS Build Error in Build-Server [ Log File is Attached ]

[Mohammed Ghouse]

TEAM

We are getting Build error while creating Build for IOS device in Build-Server. The Log File is attached for reference.

The Log file is showing some exceptions like :

Dfilesharingenabled=false Exception in thread "main" java.lang.reflect.InvocationTargetException

Caused by: java.lang.RuntimeException: Color conflict with neighbor in interface com.NetScaleToGo.App.ClientSV!

Please go through attached Log File [ error.txt ] for full information for Build Error in Build-Server.

In eclipse, the project is compiling successfully and also running in Simulator. But while creating Build for IOS device in Build-Server, we are getting Build-Error. 

But build is creating successfully for Android device. The component one build system seems to convert the code first to android build and then converts android code to iPhone. The errors in the document suggests they use a framework - xmlvm [ http://xmlvm.org/overview/ ]. The error in build suggests that the class used has some hierarchy issues. This issue might be due to codenameone bug or because of conflict in interface, classes. - ClientSV.java might be causing this issue. There are 6 errors count (details of only two are shown in error log). Not only ClientSV.java but other files also there, But error log showing only 1 to 2 details [ at the end of the log file there is  ... 6 more ] hiding 6 more errors.

Kindly find the attachment for BuildError_in_BuildServer.png showing Android-Build is success and IOS Build Error.
Kindly find the attachment for ClientSV.java [ Not exact same file due to confidential, but it is similar file [ identical ] ]
Kindly find the attachment for Log-File [ error.txt ]

If you have faced any such scenario, please let us know. Any suggestions to fix this issue would be great.

[Shai Almog]

Hi,
are you using Eclipse? Is it possible you aren't using the latest version of the plugin?

There was a conflict between the translation code and the Eclipse ADT compiler so we switched to using pure javac for sending builds on Eclipse.

[Mohammed Ghouse]

Yes,  i am using updated Eclispe [ indigo ] with updated & latest Codename1 plug-in.

[Shai Almog]

Did you edit the build.xml?
Can you right click the project, go into settings the click OK.
Then you should be prompted to update the build.xml.
Once this is up to date you might get compilation failures and you will need to edit the build.xml to point at the right location for the javac compiler.

[Mohammed Ghouse]

There is no option like setting when right clicking on project.  [ Kindly find the attachment ]

What i did is:  right click the project ---- Clicked codenameone ---- Clicked Run Tests  [ Kindly find the attachment ]

When i clicked Run Tests then i am getting Run Tests Console information [ Kindly find the attachment ]. With the help of Run Tests Console information, you can find out the problem.

My CodeNameOne Plugin version number is :  1.0.0.201307290116

Please help me to make Build success in Build-Server for IOS devices. Thanks in advanced.

[Shai Almog]

Project properties not settings.
Running test cases has absolutely nothing to do with it.

[Mohammed Ghouse]

YES  Shai  Almog,

Yes, I updated Build.xml. No issues with Build.xml. java 1.5 version only, we are using. But, still Build-Error in Build-Server.

I had given a lot of information in my all previous post with attachments  to solve this issue. i am not getting relevant response.

The Log file is showing some exceptions like :

Dfilesharingenabled=false Exception in thread "main" java.lang.reflect.InvocationTargetException
Caused by: java.lang.RuntimeException: Color conflict with neighbor in interface com.NetScaleToGo.App.ClientSV!

Please go through attached Log File [ error.txt ] for full information for Build Error in Build-Server.

The error in build suggests that the class used has some hierarchy issues [ http://mc.coolman.ca/mc-artifacts/lib/apidocs/index.html?org/xmlvm/util/ObjectHierarchyHelper.html ].  . This issue might be due to codenameone bug or because of conflict in interface, classes. - ClientSV.java might be causing this issue. There are 6 errors count (details of only two are shown in error log). Not only ClientSV.java but other files also there, But error log showing only 1 to 2 details [ at the end of the log file there is  ... 6 more ] hiding 6 more errors [ is it CodeNameOne BUG  ?? ].

Kindly find the attachment for ClientSV.java [ Not exact same file due to confidential, but it is similar file [ identical ] ]
Kindly find the attachment for Log-File [ error.txt ]

Kindly find the attachment for Build.xml

In Build-Sever, Builds are getting success for Android, Blackberry, Windows. But for IOS, it is getting Build-Error. Is it CodeNameOne BUG  ??

 From last 2 weeks happen, issue is not getting resolved. We are having Basic account. Let me know, If you need PRO-Account to Solve this issue.

Waiting for your reply with lots of hopes.

On Wed, Aug 14, 2013 at 10:39 PM, Shai Almog <shai....@gmail.com> wrote:

Project properties not settings.
Running test cases has absolutely nothing to do with it.

--
You received this message because you are subscribed to a topic in the Google Groups "CodenameOne Discussions" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/codenameone-discussions/mkSjXd8CupM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to codenameone-discu...@googlegroups.com.
Visit this group at http://groups.google.com/group/codenameone-discussions.

To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/c18dabd6-5afa-4aad-973f-386aba8330ba%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Mohammed Ghouse]

HI  Shai Almog,

Hence we have upgraded to the pro account for you to provide the solution for us to resolve the build error.
I have send mail also.
Please help US to resolve the Build-Error in Build-Server.

Thanks & Regards:

Mohammed Gouse
Bangalore
INDIA.

[Shai Almog]

For general information this issue was triggered because of an issue with interfaces containing String arrays within them. Once this was fixed the problem was resolved.