SEND BUILDS TO SERVER: IOS, J2ME, WIN & BB EXCEPT ANDROID ALL REPORT ERROR

[ventis]

Hello,

I am in a very serious situation here.

I just finished building an app with codenamone and thought I could send the builds at any time I liked not minding the time of the app.

My delivery of the app in in the next 2 days and unfortunately when I sent the request to build the app,

I have these errors that I really dont understand preventing the app from successfully building.

The same app fails on iOS build, J2ME build, WIn build, RIM build even on windows desktop build but the same app successfully builds on Android build although with TextField issues.

Please I need serious help here to get this overwith.

I have attached the logs of 3 of the platforms to see if it could be diagnosed and possibly I am directed to the right track.

Please might I have any possible help here

Thank you.

If you are experiencing an issue please mention the full platform your issue applies to:
IDE: NetBeans/Eclipse/IDEA
Desktop OS
Simulator
Device

---

iPhone Error Log.txt

RIM Error Log.txt

J2ME Error Log.txt

[Chen Fishbein]

Hi,

From looking at the logs, it seems like it's related to pubnub integration.

Did you added the cn1lib properly to the project? if yes I'd suggest you to follow up with the pubnub guys to figure out why it's not building properly.

 

 

[ventis]

Hi,

But my point is why the build could only succeed on android and not on others.

I added the cn1lib but am not only certain what you could mean by "properly". Am of the opinion that if it was not added properly, android would also not have compiled.

Let me just test the pubnub feature from android and see what happens.

but am sure pubnub works on all these platforms that did not compile.

[ventis]

I just tested the pubnub feature on the successful android build and the feature is working perfectly.

So I am lost but will look into the cn1lib again and rebuild.

On Sunday, January 25, 2015 at 10:51:33 AM UTC+1, ventis wrote:

[ventis]

Here are a list of the cn1libs attached to the project

BouncyCastleCN1Lib.cn1lib

json.cn1lib

Pubnub-CodeNameOne-3.6.3.cn1lib

Pubnub-CodeNameOne-3.7.1.cn1lib

Pubnub-CodeNameOne-Debug-3.6.3.cn1lib

Am I in order like this.

On Sunday, January 25, 2015 at 10:51:33 AM UTC+1, ventis wrote:

[ventis]

Also, I think you maybe right on your suspicion of pubnub being  the problem.

I probed further, so I used the downloaded codenameone pubnub example project and only android and RIM builds succeeded. 

I cant conclude completely seeing that RIM also successfully built buts it more or less seems like thats the case.

Am sure a number of people haved used pubnub in codenameone projects and perhaps had one or 2 similar issue slike this.

Maybe I should start another thread on Building pubnub projects for this platform perhaps someone might have an answer.

Thank you

On Sunday, January 25, 2015 at 10:51:33 AM UTC+1, ventis wrote:

[ventis]

Chen,

Please how can I or wherecan I set ios.newvm= false to try build server with old vm. Shai opins thats why its not successfully building on iOS platform.

Thanks

On Sunday, January 25, 2015 at 10:51:33 AM UTC+1, ventis wrote:

[ventis]

Chen,

Please how can I or where can I set ios.newvm= false to try build server with old vm. Shai opins thats why its not successfully building on iOS platform.

In addition would you know the version of pubnub sdk that your server is using to build pubnub projects.I have spoken with them at pubnub and they asked to confirm which version codenameone server is using to build pubnub projects because there are some methods that are missing based on the error log i forwarded to them.

Thanks

On Sunday, January 25, 2015 at 10:51:33 AM UTC+1, ventis wrote:

[ventis]

Hi,

Clearly Shai was right, i just found my way in to make set build arguments ios.newvm= false and iOS has sucessfully build. So we are left with Windows, RIM and J2ME.

Did you get my last message?

On Sunday, January 25, 2015 at 10:51:33 AM UTC+1, ventis wrote:

[Shai Almog]

Hi,
I'm assuming those ports have issues related to the pubnub implementation. I'm not sure this is fixable on our side.

[ventis]

Shai,

Thank you but can you pls recommend another alternative to pubnub that builds on codenameone server for RIM/J2ME and WIN platforms.

[Shai Almog]

You can use the ConnectionRequest and http or you can use Steve's socket cn1lib. Notice it too has an issue on Windows Phone as far as I recall.

[ventis]

Shai,

Am sure you are aware of all that has been going on with the pubnub lead team on the prevailing build issues I have been having for like 4-5 days with building my project successfully on the account/grounds of pubnub integration.

Based on the recent instructions of their lead developer (Devendra) to use the following;

https://github.com/pubnub/java/raw/DESK-10801/codenameone/Pubnub-CodeNameOne-3.7.2.cn1lib

AND

https://bouncy-castle-codenameone-lib.googlecode.com/svn/trunk/BouncyCastleCN1Lib.cn1lib

Which made them build successfuly from their end, I have still not been able to build successfully on RIM. J2ME and WIN platforms. Also these updates did not allow build on iOS until i changed newVM = true.

I have attached the logs here and would appeal that you check then out should it be an issue arising from codenameone build servers bearing in mind that there were able to successfully build from their ends.

Thank you.

[Shai Almog]

As far as I understood from Devendra the Windows Phone build issue was resolved by updating to the latest version of our bouncy castle integration.
The J2ME/RIM issue is something I followed up with them quite a while back.

[ventis]

Eventually Devendra adviced I should is change my project to avaoid any pubnub cn1lib with a view to check if there were other issues am I contending with. He said so because he was able to build successfully on their end on J2ME and RIM. 

I followed his advice and unfortunately the builds on RIM/J2ME and WIN did not evntually succeed. Meaning that there could be other things involved. I have attached the logs of the error one again.

I will be glad if you could help to arrive at a safe haven with regards to this issue.

Thanks

[Shai Almog]

The J2ME problem seems to be a temporary glitch in J2ME builds related to some new features.
The RIM problem is a known issue with RIM builds, they just "sometimes" don't work when you have a file that's too large for some reason. The only workaround is to shift some code around... Sucks.
In the Windows Phone port its hard to say what went wrong.

[ventis]

Alrite ths means all are looking good despite the build errors. I might not just be able to produce RIM/J2ME/WIN platforms of the app that  easily. Will this have anything to do with my type of subscription?

Then could you recommend compiling/building the app on another service for each of the platforms. Am sure when you design apps like this an have such problems on size and unknown as in WIN you do resolve them somehow either by using something else to build them or taking the same code with little refactoring to another product/ervice to achieve the builds.

I just need to be able to produce the same app for at least 4 platforms (iOS and Android are good).

Thanks for your advice.

[ventis]

Also can you advice based on your experience with codenameone, what do you think should be the maximum file size or number of lines in a file n order to achieve a build in a RIM.

That might also help as a guideline.

Thanks

[ventis]

Shai,

Thanks a lot for your advice and follow ups.

I followed your advice on the RIM and broke codes into parts, and RIM compiled even with the pubnub integration.

Now I will be waiting on your team to fix the J2ME platform due to the new features.

However, I tried installing the RIM and IOS builds on a Blackberry, iPohone and iPad but there are not just installing.

Could this be as a result of the lack of appropriate certificates. I actually want to first test run like the android before obtaining the right certificates and sign in

Thank you.

[Shai Almog]

Try installing the RIM app thru the install link.
The iPhone app requires that you pay apple.

[ventis]

I have a developer account with apple, so IOS wont be a problem. I suppose you mean building with paid certificates.

For the RIM, i used the download link but its not installing.

Thanks

[Shai Almog]

Use the install link and type it on the device (or use the email envelope to email it to yourself and open the link on the device).

[ventis]

Perhaps I should rebuild the app using isNewVM = true and isNewVm=false and recheck the builds at both instances and see what I get. Then i ll get back to your with a report again. Because i have been doing all you suggested. 

What is the timeline on the J2ME build error resolution.

Cheers

[Shai Almog]

The J2ME issue should be resolved by now.
Let me know if newVM=true fails with pubnub, if so we need to fix that.

[ventis]

Thanks Shai

I was able to build J2ME using both isNewVM =true and false only without pubnub. When i added pubnub integration to the application, it failed.

The error log is attached for easy troubleshooting.

[Shai Almog]

That's back to being the pubnub issue I mentioned earlier.

[ventis]

Should I escalate it to them with the error log or you will handle it from your end?

[Shai Almog]

I see that they are looking at that.

[ventis]

I think i have been using the wrong combination of pubnub cn1lib files.

I have been able to buil on iOS/Android/RIM/J2ME successfully with quiance from Shai.

Only windows still looks a bit problematic with coenameone.

Thanks

[Shai Almog]

The Windows Phone VM is a painful one. We might rewrite it in the future but we don't have the resources right now and it isn't important to any of our enterprise clientele.

[ventis]

Shai,

Is there an issue with the server build particularly for iOS. I just tried an IOS build now but it gave an error and thats strange because RIM, J2MW and Android build successfully.

The error is a recoccuring one I think. Please use the error log attached error log for ease of troubleshoot.

Also, are there other options to use to sign a j2me application other than Spring WTK. I can not find a place to download it, You can help me with a download link for the tool or advice another one.

On Tuesday, February 3, 2015 at 7:16:55 AM UTC+1, Shai Almog wrote:

The Windows Phone VM is a painful one. We might rewrite it in the future but we don't have the resources right now and it isn't important to any of our enterprise clientele.

---

error (3).txt

error (2).txt

[Shai Almog]

You need to build with a valid certificate for iOS to work. Its problematic to build without it.
Signing J2ME apps is a world of pain, there is a reason we don't support that in the cloud. I haven't done it in at least 7 years and can't really help you there.

[biyiex...@yahoo.com]

But its been building without a certificate all along. Is this a new requirement?

[Shai Almog]

It just sometimes doesn't work and we're not sure why. Certificates were always required we just let you build with ours sometimes.

[ventis]

Alrite.

You are atually right on the IOS certificate. Just created one following your tutorial and I have been able to.

Thanks

[ventis]

Hi Shai,

Is the Windows Phone VM and the issue of the pubnub.com still the same?
Has anything been done to it yet in reference to your previous responses about the VW needing to be rewritten to accommodate the pubnub.com websockets.

Secondly, I was trying to submit the J2ME application after building but it seems to be returning an invalid build while using Opera Mobile Store to submit the app.
Please may I ask what can be used to submit the J2ME applications for easy download by any user. In addition I have not sign the app with anything yet. Can you please let me know what really works.

[Shai Almog]

Hi,
I can't help you much with J2ME. What we have worked when we last tested it but its not our focus and we haven't tested the opera store.
If other platforms work and Windows Phone fails then its an issue on our side. It will take us quite a while to address though since we need to completely rewrite the windows phone port and that isn't even scheduled yet.