search

wei-spring / codenameone

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

RIM build with push support fails #829

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Please clearly state whether the issue relates to a device/the simulator or
the tools.
Build server.
If related to a device be sure to specify exactly which device with as much
details as possible.
 Blackberry build

What steps will reproduce the problem?
1. Set the property of 
rim.pushBpsURL==https://cp12173.pushapi.eval.blackberry.com
2. And send RIM build
3.

What is the expected output? What do you see instead?

The build should be successful. Instead the build fails with error as in the 
attached file.

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

Latest version. On Mac.
Please provide any additional information below.

Original issue reported on code.google.com by nir...@nvsoft.com on 8 Aug 2013 at 4:48

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks, that's really odd. I must have broken it recently.
It should be fixed on the build server now.

Original comment by shai.almog on 8 Aug 2013 at 5:26

GoogleCodeExporter commented 9 years ago 
It is now giving another set of errors as in the attached error file.

Original comment by nir...@nvsoft.com on 8 Aug 2013 at 7:06

Attachments:

GoogleCodeExporter commented 9 years ago 
Thanks, this should be fixed now too.

Original comment by shai.almog on 8 Aug 2013 at 8:09

GoogleCodeExporter commented 9 years ago 
Ok, those errors are gone, however I am getting another error as given in the 
attached file.

Original comment by nir...@nvsoft.com on 8 Aug 2013 at 8:34

Attachments:

GoogleCodeExporter commented 9 years ago 
That's a different issue altogether. Its probably been there for a while.

Original comment by shai.almog on 8 Aug 2013 at 9:40

GoogleCodeExporter commented 9 years ago 
Fixed on the server.

Original comment by shai.almog on 8 Aug 2013 at 9:40

GoogleCodeExporter commented 9 years ago 
Just tried a build again, but got the same error. Is it already deployed on 
server?

Original comment by nir...@nvsoft.com on 8 Aug 2013 at 9:50

Attachments:

GoogleCodeExporter commented 9 years ago 
It is on the server but for some reason this isn't working. I think the only 
workaround is to build with the obfuscation switch set to false.

Original comment by shai.almog on 8 Aug 2013 at 10:16

GoogleCodeExporter commented 9 years ago 
Hmm, when I set rim.obfuscation to false, and save,  And then when I re-open 
the project and check the build hints it again becomes true.

Original comment by nir...@nvsoft.com on 8 Aug 2013 at 10:34

GoogleCodeExporter commented 9 years ago 
ok, I made the property false in codename_settings.properties file and then 
sent a build. It seems to have progressed further and I got the email from RIM 
that my code was signed. However on the build server the build seems to be 
stuck in "building" state only.

Original comment by nir...@nvsoft.com on 8 Aug 2013 at 11:03

GoogleCodeExporter commented 9 years ago 
Did you try canceling and sending again?

Original comment by shai.almog on 8 Aug 2013 at 11:40

GoogleCodeExporter commented 9 years ago 
yes, did that. And again it has got stuck in building only since last 50 mins. 
(Btw I am get successful the signing email msgs from Blackberry).

Original comment by nir...@nvsoft.com on 8 Aug 2013 at 12:14

GoogleCodeExporter commented 9 years ago 
I'm looking at the build servers for RIM right now and I can't see your build. 
Can you send one again? Might have been a hickup on App Engine.

Original comment by shai.almog on 8 Aug 2013 at 12:22

GoogleCodeExporter commented 9 years ago 
I had cancelled that again. Just now sent one more RIM build request.

Original comment by nir...@nvsoft.com on 8 Aug 2013 at 12:41

GoogleCodeExporter commented 9 years ago 
Did it pass?
On the server it seems to have passed.

Original comment by shai.almog on 8 Aug 2013 at 1:02

GoogleCodeExporter commented 9 years ago 
yes, this time it passed. Thanks

Original comment by nir...@nvsoft.com on 8 Aug 2013 at 1:04

GoogleCodeExporter commented 9 years ago 
Even though the build passed and the app got installed in the device. But when 
I start the app, it causes an exception and crashes saying: Error starting 
S2PayApp5: Module 'S2PayApp5-1' has verification error 190 at offset 6c21"

How to debug this further?

Original comment by nir...@nvsoft.com on 8 Aug 2013 at 3:17

GoogleCodeExporter commented 9 years ago 
I think this is related to the Codescan library. I don't think its working 
anymore for some reason. If you comment out the scan code does it work then?

Original comment by shai.almog on 8 Aug 2013 at 4:45

GoogleCodeExporter commented 9 years ago 
I comment out codescan library and then built a new version. It is still giving 
following error and does not start.

"Error starting S2PayApp5: Module 'S2PayApp5-1' has verification error 190 at 
offset  6998 (codfile version 78)"

Original comment by nir...@nvsoft.com on 9 Aug 2013 at 11:16

GoogleCodeExporter commented 9 years ago 
Odd. If you build with obfuscation (to strip out that code) would that work?
If you build a hello world would that work?

Original comment by shai.almog on 9 Aug 2013 at 11:34

GoogleCodeExporter commented 9 years ago 
ok, if I build a hello world app, then it works.

If I try to build my app with obfuscation, then the build fails with the 
attached error.

Original comment by nir...@nvsoft.com on 9 Aug 2013 at 1:57

GoogleCodeExporter commented 9 years ago 
Here's the error.txt for previous comment.

Original comment by nir...@nvsoft.com on 9 Aug 2013 at 1:58

Attachments:

GoogleCodeExporter commented 9 years ago 
This is weird. Can you look in the alt-lglg log after you get the verification 
error and see what is written there. It should usually provide more details 
about the failed class/screen.

Original comment by shai.almog on 9 Aug 2013 at 6:39

GoogleCodeExporter commented 9 years ago 
Checked the alt lglg logs and it shows following:
Linker error
VM.VECPs=com.codename1.impl.blackberry.codescan
VM:VECCs=CodeScannerImpl
VM:VECMm=callDecode()

Even though I have commented the calls to CodeScanner in my app.

Original comment by nir...@nvsoft.com on 10 Aug 2013 at 1:43

GoogleCodeExporter commented 9 years ago 
That probably means that for some reason its still included. Its the only 
portion of the code we have in binary form so the bug might be in there but we 
can't fix it. I have an idea for a workaround but it won't be trivial, I 
suggest you file a different issue to cover that.

Original comment by shai.almog on 10 Aug 2013 at 4:31

GoogleCodeExporter commented 9 years ago 
Thanks Shai, a separate issue 831 is created for it.

Original comment by nir...@nvsoft.com on 10 Aug 2013 at 12:40

GoogleCodeExporter commented 9 years ago 
ok, now I am able to run my app on the device, however the push registration 
fails with following error:

java.io.IOException: APN is not specified

I have specified the following rim related push properties in codename_settings.

rim.pushAppId
rim.pushPort
rim.pushBpsURL
rim.ignor_legacy=true
rim.includePush=true

Original comment by nir...@nvsoft.com on 12 Aug 2013 at 1:51

GoogleCodeExporter commented 9 years ago 
Does networking work on this device?
Do you configure APN manually in code?

Original comment by shai.almog on 12 Aug 2013 at 3:01

GoogleCodeExporter commented 9 years ago 
Yes networking is working on this device and currently it is using WIFI.

I am not configuring APN manually in code.

Original comment by nir...@nvsoft.com on 12 Aug 2013 at 3:57

GoogleCodeExporter commented 9 years ago 
Do you have a stack for that exception? Maybe from the alt-lglg

Original comment by shai.almog on 12 Aug 2013 at 4:53

GoogleCodeExporter commented 9 years ago 
Here's the relevant stack trace from the alt-lglg:

a CN1 - [Thread-371310592] 0:1:3,732 - pushRegistrationError
currentForm[{}] error[{}] errorCode[{}]null,java.io.IOException: APN
is not specified.,1, - 8/13 13:38:45
d net.rim.blackberry.api.push - Ansc   8 - 8/13 13:38:45
d net.rim.blackberry.api.push - Bsto - 8/13 13:38:45
W net.rim.blackberry.api.push - Berr java.io.IOException: APN is not
specified. - 8/13 13:38:45
a net.rim.tcp - open
tcpsocket://cp12173.pushapi.eval.blackberry.com:443;interface=cellular
- 8/13 13:38:45
i net.rim.networkapi - FatF java.io.IOException: APN is not specified.
- 8/13 13:38:45
i net.rim.networkapi - Fatf   1 - 8/13 13:38:45
a net.rim.tcp - open
tcpsocket://cp12173.pushapi.eval.blackberry.com:443;interface=cellular
- 8/13 13:38:45
d net.rim.networkapi - FcoC
https://cp12173.pushapi.eval.blackberry.com/mss/PD_subReg?serviceid=12173-es6966
19D4r907I7456c979mm91a23r079&osversion=5.0.0.1036&model=8520;deviceside=true
- 8/13 13:38:45
i net.rim.networkapi - Fatt   1 - 8/13 13:38:45

i net.rim.networkapi - FatF java.io.IOException: APN is not specified.
- 8/13 13:38:14
i net.rim.networkapi - Fatf   1 - 8/13 13:38:14
a net.rim.tcp - open
tcpsocket://cp12173.pushapi.eval.blackberry.com:443;interface=cellular
- 8/13 13:38:14
d net.rim.networkapi - FcoC
https://cp12173.pushapi.eval.blackberry.com/mss/PD_subReg?serviceid=12173-es6966
19D4r907I7456c979mm91a23r079&osversion=5.0.0.1036&model=8520;deviceside=true
- 8/13 13:38:14
i net.rim.networkapi - Fatt   1 - 8/13 13:38:14
d net.rim.blackberry.api.push - BRqt
https://cp12173.pushapi.eval.blackberry.com/mss/PD_subReg?serviceid=12173-es6966
19D4r907I7456c979mm91a23r079&osversion=5.0.0.1036&model=8520
- 8/13 13:38:14
d net.rim.blackberry.api.push - BRsr - 8/13 13:38:14
d net.rim.blackberry.api.push - Bsta - 8/13 13:38:14
d net.rim.blackberry.api.push - Rcre   4 - 8/13 13:38:14
a CN1 - [Thread-303953920] 0:0:31,413 - Push registration requested

Original comment by nir...@nvsoft.com on 13 Aug 2013 at 8:21

GoogleCodeExporter commented 9 years ago 
I have no idea?
Can you disable/enable APN in the settings? Make sure its configured correctly?
The IOException is without a stack trace so its effectively useless and the tcp 
networking done internally seems to connect to cellular while our networking 
tries to use your wifi connection.

Original comment by shai.almog on 13 Aug 2013 at 9:39

GoogleCodeExporter commented 9 years ago 
ok, I tried to enable APN settings and after that I am getting following error:

i net.rim.networkapi - FatF java.lang.IllegalStateException: no
application instance - 8/13 15:44:03
i net.rim.networkapi - Fatf   1 - 8/13 15:44:02
a net.rim.tcp - open
tcpsocket://cp12173.pushapi.eval.blackberry.com:443;interface=cellular
- 8/13 15:44:02
d net.rim.networkapi - FcoC
https://cp12173.pushapi.eval.blackberry.com/mss/PD_subReg?serviceid=12173-es6966
19D4r907I7456c979mm91a23r079&osversion=5.0.0.1036&model=8520;deviceside=true
- 8/13 15:44:02
i net.rim.networkapi - Fatt   1 - 8/13 15:44:02
d net.rim.blackberry.api.push - BRqt
https://cp12173.pushapi.eval.blackberry.com/mss/PD_subReg?serviceid=12173-es6966
19D4r907I7456c979mm91a23r079&osversion=5.0.0.1036&model=8520
- 8/13 15:44:02
d net.rim.blackberry.api.push - BRsr - 8/13 15:44:02
d net.rim.blackberry.api.push - Bsta - 8/13 15:44:02
d net.rim.blackberry.api.push - Rcre   5 - 8/13 15:44:02
a CN1 - [Thread-297314304] 0:0:34,360 - Push registration requested

Does that gives any hint what could be the issue?

Original comment by nir...@nvsoft.com on 13 Aug 2013 at 10:34

GoogleCodeExporter commented 9 years ago 
ok, I enabled Blackberry Internet Service (BIS) also on my phone. After that I 
guess it is going a bit further, but gave following error and log is attached 
in the file.

Original comment by nir...@nvsoft.com on 13 Aug 2013 at 1:22

Attachments:

GoogleCodeExporter commented 9 years ago 
I'm still stumped by this? Do you have other applications that use push on this 
device?
Does e.g. does whatsup work with push on blackberry? Can you try it?

Original comment by shai.almog on 13 Aug 2013 at 4:21

GoogleCodeExporter commented 9 years ago 
I installed whatsapp on this blackberry device and it is working with push and 
getting all the msgs.

I have pasted the alt-lglg logs in case anything there helps:
#BlackBerry Event Log (cpt)
#HwID: 0x8c000f03
#DPIN: 0x274529cd
#PVer: 5.2.0.104
#AVer: 5.0.0.1036
a System - JVM:INFOp=274529cd,a='5.0.0.1036',o='5.2.0.104',h=8c000f03
- 8/14 00:10:28
a System - AMGF net_rim_event_log_viewer_app(283) - 8/14 00:10:28
a System - AMNF net_rim_event_log_viewer_app(283) - 8/14 00:10:28
d net.rim.simat - IDLE - 8/14 00:10:24
a System - AMSF net_rim_bb_ribbon_app(102) - 8/14 00:10:24
a System - AMNF net_rim_bb_ribbon_app(102) - 8/14 00:10:24
a UI - GS-D e14ff255 - 8/14 00:10:24
a UI - GS+Q2 e14ff255net.rim.device.apps.internal.ribbon.ui.ApplicationSwitcher
- 8/14 00:10:21
d net.rim.wlan.scan - Wait-idle - 8/14 00:10:00
d net.rim.wlan.blacklist - rstL   0 - 8/14 00:10:00
d net.rim.wlan.scan - Actn-update blacklist - 8/14 00:10:00
d net.rim.wlan.scan - Evnt-update blacklist - 8/14 00:10:00
d net.rim.fd - FDOf   -432693392   43505640- 8/14 00:10:00
d net.rim.fd - FDOf   -432693390   43506757- 8/14 00:10:00
a System - CMM: WhatsApp-17(4866) no sig from 0x33 - 8/14 00:09:22
d App Perms - d WhatsApp:34 - 8/14 00:09:21
d App Perms - d WhatsApp:12 - 8/14 00:09:21
d net.rim.tcp - TXss - 8/14 00:09:21
d net.rim.tcp - TXsb   33 - 8/14 00:09:21
a net.rim.tcp - disc   1 - 8/14 00:09:15
a net.rim.tcp - disc   1 - 8/14 00:09:08
d net.rim.deviceagent - UPDO   83886080 - 8/14 00:09:06
a net.rim.tcp - disc   1 - 8/14 00:09:05
d net.rim.wlan.scan - Wait-idle - 8/14 00:09:00
d net.rim.wlan.blacklist - rstL   0 - 8/14 00:09:00
d net.rim.wlan.scan - Actn-update blacklist - 8/14 00:09:00
d net.rim.wlan.scan - Evnt-update blacklist - 8/14 00:09:00
d net.rim.fd - FDOf   -432693392   43505640- 8/14 00:09:00
d net.rim.fd - FDOf   -432693390   43506757- 8/14 00:09:00
a WhatsApp - SMS Screen - Transition to Alternate Auth:
sms-listener-fail - 8/14 00:08:50
d net.rim.tcp - TXss - 8/14 00:08:49
d net.rim.tcp - TXsb   32 - 8/14 00:08:49
d net.rim.tcp - TXss - 8/14 00:08:49
d net.rim.tcp - TXsb   157 - 8/14 00:08:49
d net.rim.tcp - TXss - 8/14 00:08:48
d net.rim.tcp - TXsb   12 - 8/14 00:08:48
d net.rim.tcp - TXss - 8/14 00:08:48
d net.rim.tcp - TXsb   27 - 8/14 00:08:48
d net.rim.tcp - TXss - 8/14 00:08:48
d net.rim.tcp - TXsb   25 - 8/14 00:08:48
d net.rim.tcp - TXss - 8/14 00:08:48
d net.rim.tcp - TXsb   47 - 8/14 00:08:48
d net.rim.tcp - TXss - 8/14 00:08:48
d net.rim.tcp - TXsb   42 - 8/14 00:08:48
d net.rim.tcp - TXss - 8/14 00:08:48
d net.rim.tcp - TXsb   94 - 8/14 00:08:48
d net.rim.tcp - TXss - 8/14 00:08:48
d net.rim.tcp - TXsb   42 - 8/14 00:08:48
d net.rim.tcp - TXss - 8/14 00:08:48
d net.rim.tcp - TXsb   28 - 8/14 00:08:48
d net.rim.tcp - TXss - 8/14 00:08:48
d net.rim.tcp - TXsb   30 - 8/14 00:08:48
d net.rim.tcp - TXss - 8/14 00:08:47
d net.rim.tcp - TXsb   216 - 8/14 00:08:47
d net.rim.tcp - TXss - 8/14 00:08:47
d net.rim.tcp - TXsb   72 - 8/14 00:08:47
d net.rim.tcp - OPEN - 8/14 00:08:47
a net.rim.udp - clos 33/337 - 8/14 00:08:46
a net.rim.tunnel - Clos-MagicRudyAPN.rim - 8/14 00:08:46
a net.rim.dns - RetQ - 8/14 00:08:46
a net.rim.dns - DnsR   3 - 8/14 00:08:46
i net.rim.dns - RXst - 8/14 00:08:46
d net.rim.udp - RXst   337 - 8/14 00:08:46
d net.rim.udp - RXST   1 - 8/14 00:08:46
d net.rim.udp - TXss - 8/14 00:08:46
d net.rim.udp - TXsb   33 - 8/14 00:08:46
i net.rim.dns - TXst - 8/14 00:08:46
a net.rim.dns - DnsQ   3 - 8/14 00:08:46
d net.rim.udp - OPEN - 8/14 00:08:46
a net.rim.udp - open udpsocket://;tunnelId=3 - 8/14 00:08:46
a net.rim.tunnel - STac-MagicRudyAPN.rim - 8/14 00:08:46
a net.rim.tunnel - Open-MagicRudyAPN.rim - 8/14 00:08:46
a net.rim.tcp - open tcpsocket://c3.whatsapp.net.:443;interface=wifi -
8/14 00:08:46
d net.rim.tcp - TXss - 8/14 00:08:44
d net.rim.tcp - TXsb   308 - 8/14 00:08:44
d net.rim.tcp - TXss - 8/14 00:08:44
d net.rim.tcp - TXsb   65 - 8/14 00:08:44
d net.rim.tcp - TXss - 8/14 00:08:44
d net.rim.tcp - TXsb   6 - 8/14 00:08:44
d net.rim.tcp - TXss - 8/14 00:08:44
d net.rim.tcp - TXsb   265 - 8/14 00:08:44
d net.rim.tcp - TXss - 8/14 00:08:43
d net.rim.tcp - TXsb   116 - 8/14 00:08:43
d net.rim.tcp - OPEN - 8/14 00:08:43
a net.rim.tunnel - STac-MagicRudyAPN.rim - 8/14 00:08:43
a net.rim.tunnel - Open-MagicRudyAPN.rim - 8/14 00:08:43
a net.rim.tcp - open tcpsocket://v.whatsapp.net:443;interface=wifi -
8/14 00:08:43
a net.rim.smsui -  MNS - 8/14 00:08:42
d CC - IsFDNEnabled,"false" - 8/14 00:08:42
a net.rim.smsui -  MRX - 8/14 00:08:42
d net.rim.sms - RXpu - 8/14 00:08:42
i net.rim.sms - RXst - 8/14 00:08:42
i net.rim.sms - TXss - 8/14 00:08:41
d net.rim.sms - TXsb - 8/14 00:08:38
i net.rim.sms - TXst - 8/14 00:08:38
d net.rim.tcp - TXss - 8/14 00:08:37
d net.rim.tcp - TXsb   359 - 8/14 00:08:37
d net.rim.tcp - TXss - 8/14 00:08:36
d net.rim.tcp - TXsb   65 - 8/14 00:08:36
d net.rim.tcp - TXss - 8/14 00:08:36
d net.rim.tcp - TXsb   6 - 8/14 00:08:36
d net.rim.tcp - TXss - 8/14 00:08:36
d net.rim.tcp - TXsb   265 - 8/14 00:08:36
d net.rim.tcp - TXss - 8/14 00:08:35
d net.rim.tcp - TXsb   116 - 8/14 00:08:35
d net.rim.tcp - OPEN - 8/14 00:08:35
a net.rim.tunnel - STac-MagicRudyAPN.rim - 8/14 00:08:35
a net.rim.tunnel - Open-MagicRudyAPN.rim - 8/14 00:08:35
a net.rim.tcp - open tcpsocket://v.whatsapp.net:443;interface=wifi -
8/14 00:08:35
a net.rim.sms - INcn - 8/14 00:08:35
a System - CMM: WhatsApp-1(2318) no sig from 0x33 - 8/14 00:08:35
d net.rim.tcp - TXss - 8/14 00:08:34
d net.rim.tcp - TXsb   269 - 8/14 00:08:34
d net.rim.tcp - TXss - 8/14 00:08:33
d net.rim.tcp - TXsb   65 - 8/14 00:08:33
d net.rim.tcp - TXss - 8/14 00:08:33
d net.rim.tcp - TXsb   6 - 8/14 00:08:33
d net.rim.tcp - TXss - 8/14 00:08:33
d net.rim.tcp - TXsb   265 - 8/14 00:08:33
d net.rim.tcp - TXss - 8/14 00:08:32
d net.rim.tcp - TXsb   84 - 8/14 00:08:32
d net.rim.tcp - OPEN - 8/14 00:08:32
a net.rim.udp - clos 32/48 - 8/14 00:08:31
a net.rim.tunnel - Clos-MagicRudyAPN.rim - 8/14 00:08:31
a net.rim.dns - RetQ - 8/14 00:08:31
a net.rim.dns - DnsR   3 - 8/14 00:08:31
i net.rim.dns - RXst - 8/14 00:08:31
d net.rim.udp - RXst   48 - 8/14 00:08:31
d net.rim.udp - RXST   1 - 8/14 00:08:31
d net.rim.udp - TXss - 8/14 00:08:31
d net.rim.udp - TXsb   32 - 8/14 00:08:31
i net.rim.dns - TXst - 8/14 00:08:31
a net.rim.dns - DnsQ   3 - 8/14 00:08:31
d net.rim.udp - OPEN - 8/14 00:08:31
a net.rim.udp - open udpsocket://;tunnelId=3 - 8/14 00:08:31
a net.rim.tunnel - STac-MagicRudyAPN.rim - 8/14 00:08:31
a net.rim.tunnel - Open-MagicRudyAPN.rim - 8/14 00:08:31
a net.rim.tcp - open tcpsocket://v.whatsapp.net:443;interface=wifi -
8/14 00:08:31
a System - CMM: WhatsApp-22(7364) no sig from 0x33 - 8/14 00:08:31
i net.rim.vpn - Wait-logged out - 8/14 00:08:13
d net.rim.wlan.scan - Wait-idle - 8/14 00:08:13
i net.rim.wlan.link - Wait-active - 8/14 00:08:13
i net.rim.vpn - Actn-user - 8/14 00:08:13
d net.rim.wlan.scan - Actn-user actvty - 8/14 00:08:13
i net.rim.wlan.link - Actn-none - 8/14 00:08:13
i net.rim.vpn - Evnt-user - 8/14 00:08:13
d net.rim.wlan.scan - Evnt-user actvty - 8/14 00:08:13
i net.rim.wlan.link - Evnt-user - 8/14 00:08:13
d net.rim.wlan.scan - Wait-idle - 8/14 00:08:00
d net.rim.wlan.blacklist - rstL   0 - 8/14 00:08:00
d net.rim.wlan.scan - Actn-update blacklist - 8/14 00:08:00
d net.rim.wlan.scan - Evnt-update blacklist - 8/14 00:08:00
d net.rim.fd - FDOf   -432693392   43505640- 8/14 00:08:00
d net.rim.fd - FDOf   -432693390   43506757- 8/14 00:08:00
d net.rim.hrtRT - CNon - 8/14 00:07:25
d net.rim.hrtRT - PRjI - 8/14 00:07:25
a net.rim.hrtRT - EPRj 0x2400000001 - 8/14 00:07:25
a net.rim.tunnel - ECls   1 - 8/14 00:07:25
d net.rim.hrtRT - CNon - 8/14 00:07:24
a net.rim.tunnel - EIna   1 - 8/14 00:07:24
a System - AMSF WhatsApp(281) - 8/14 00:07:17
a System - AMNF WhatsApp(281) - 8/14 00:07:17
a UI - GS-D 526edd41 - 8/14 00:07:17
a UI - GS+Q2 526edd41net.rim.device.apps.internal.ribbon.ui.ApplicationSwitcher
- 8/14 00:07:15
d net.rim.simat - IDLE - 8/14 00:07:13
a System - AMSF net_rim_bb_ribbon_app(102) - 8/14 00:07:13
a System - AMNF net_rim_bb_ribbon_app(102) - 8/14 00:07:13
a System - AMFD net_rim_event_log_viewer_app(282) - 8/14 00:07:13

Original comment by nir...@nvsoft.com on 13 Aug 2013 at 6:57

GoogleCodeExporter commented 9 years ago 
They seem to be using their own push servers and not RIM's push servers. Are 
you using the URL information and device side port you got from RIM?
Can you think of an application that uses the RIM public push servers?

Original comment by shai.almog on 14 Aug 2013 at 5:32

GoogleCodeExporter commented 9 years ago 
Yes, I am using the blackberry push evaluation URL and device side port
which I got from RIM.

Don't know off hand, but I will search for another app which might be using
the RIM public push servers.

-- 

NVSoft

http://www.nvsoft.com

DISCLAIMER: This e-mail and any attachment(s) is for authorized use by the
intended recipient(s) only. It may contain proprietary material,
confidential information and/or be subject to the legal privilege of the
sender of this email. If you have received this message in error, please
notify the originator immediately and destroy the material in its entirety,
whether electronic or hard copy. If you are not the intended recipient, you
are notified that you are strictly prohibited from retaining, using,
copying, alerting or disclosing the content of this message. Please note
that any views or opinions presented in this email are solely those of the
author and do not necessarily represent those of Net Vigil Software Private
Limited. The recipient should check this email and any attachments for the
presence of viruses. Net Vigil Software Private Limited accepts no
liability for any damage caused by any virus transmitted by this email.
Thank you for your co-operation.

Original comment by nir...@nvsoft.com on 14 Aug 2013 at 6:48

GoogleCodeExporter commented 9 years ago 
Unfortunately I am not able to find any app on blackberry world store which may 
be using public push server. Can you send me any of your sample app with your 
rim key which I can try? As I am using the correct values of my rim push 
evaluation setup. Don't know how to otherwise debug this further without 
knowing what is happening underneath the push registration code.

Original comment by nir...@nvsoft.com on 15 Aug 2013 at 5:02

GoogleCodeExporter commented 9 years ago 
More unfortunate is the fact that we can't get it to work either because we 
aren't paying the blackberry subscription costs for our operator. So we can't 
test it either.
Blessing was able to test it though and I implemented the logic, its working 
for him so maybe you guys can workout a test case exchange program?

Original comment by shai.almog on 15 Aug 2013 at 6:23

GoogleCodeExporter commented 9 years ago 
Hi Shai,

I am trying to debug the blackberry push issue by doing a local build, however 
I am running into an issue where it is failing due to the following error:

Application is not instanceof PushApplication. It couldn't be started.

I checked the blackberry push sample app and it seems, our app needs to 
implement the PushApplication interface. Is it possible, for you to share a 
sample AppStub which is generated by the build server for push based RIM app.

Original comment by nir...@nvsoft.com on 11 Sep 2013 at 5:28

GoogleCodeExporter commented 9 years ago 
As far as I can tell we just add the 
net.rim.blackberry.api.push.PushApplication interface to the main generated 
class then just implement the methods of that interface:
public void onMessage(net.rim.device.api.io.http.PushInputStream stream, 
javax.microedition.io.StreamConnection sc) {
     com.codename1.impl.blackberry.BlackBerryOS5Implementation.onMessage(stream, sc);
}
public void onStatusChange(net.rim.blackberry.api.push.PushApplicationStatus 
pas) {
    com.codename1.impl.blackberry.BlackBerryOS5Implementation.onStatusChange(pas);
}

Original comment by shai.almog on 13 Sep 2013 at 3:55

GoogleCodeExporter commented 9 years ago 
Hi Shai,

I tried with the Blackberry Sample push application on the same device and used 
it to register for push to Sample push initiator which RIm has provided. With 
that sample application the push is working fine on this device. So it means 
the device configuration and the push evaluation details for my registration is 
fine.

However when I try to use the codenameone built application(using build 
server), it is giving the following error during registration:

W net.rim.blackberry.api.push - Berr
net.rim.device.cldc.io.ippp.SocketBaseIOException: Connection reset by peer

Anything else we can try out?

Original comment by nir...@nvsoft.com on 14 Sep 2013 at 7:46

GoogleCodeExporter commented 9 years ago 
Do you have more of that stack? Does it lead to our code at some point?

Original comment by shai.almog on 15 Sep 2013 at 4:56

GoogleCodeExporter commented 9 years ago 
I have attached the full stack trace.  Can't figure out where the exception is 
coming from.

Original comment by nir...@nvsoft.com on 15 Sep 2013 at 8:12

Attachments:

GoogleCodeExporter commented 9 years ago 
It looks that someone is catching that exception and not invoking 
printStackTrace.
I googled a bit and this seems to be related to that exception:
http://forum.astrasync.com/Default.aspx?g=posts&m=6856

Hopefully it helps.

Original comment by shai.almog on 17 Sep 2013 at 5:08

GoogleCodeExporter commented 9 years ago 
Hi Shai,

When testing with the blackberry push sample demo app, I was using the 
BB_PUSH_URL which was starting with "https". It was working with it. However it 
seems to be causing the socket error in our code. I changed it to "http" and 
tried it again, now it is not giving the socket error. However it is not 
calling the registeredForPush() callback on my main application class.

I don't see any code in the blackberry port that might be calling it either? Is 
it part of the Stub that gets generated on the server side?

In any case, even with my app built using the server, the callback 
"registeredForPush()" is not getting called. Can you please check that?

Thanks,
Nirmal

PS. I have attached logs which happens after calling registerForPush

Original comment by nir...@nvsoft.com on 17 Sep 2013 at 2:17

Attachments:

GoogleCodeExporter commented 9 years ago 
That seems to be missing. I'll add it to the BB 5 port right now.

Original comment by shai.almog on 18 Sep 2013 at 4:55

GoogleCodeExporter commented 9 years ago 
Hi Shai,
Is this on build server also?

Somehow when I run my app now, it does cause any push request logs or 
Connection requests to the blackberry pusheval API

Original comment by nir...@nvsoft.com on 18 Sep 2013 at 7:27

GoogleCodeExporter commented 9 years ago 
Hi Shai,

I have made one change to the BlackberryOS5Implementation in the registerPush() 
method:
Index: 
Ports/BlackBerryOS_5/src/com/codename1/impl/blackberry/BlackBerryOS5Implementati
on.java
===================================================================
--- 
Ports/BlackBerryOS_5/src/com/codename1/impl/blackberry/BlackBerryOS5Implementati
on.java (revision 1474)
+++ 
Ports/BlackBerryOS_5/src/com/codename1/impl/blackberry/BlackBerryOS5Implementati
on.java (working copy)
@@ -721,6 +721,7 @@
         byte pasStatus = pushApplicationStatus.getStatus();
         if( pasStatus == PushApplicationStatus.STATUS_ACTIVE ) {
             // we already registered, update the statuses
+       onStatusChange(pushApplicationStatus);
             return;

         } else if( pasStatus == PushApplicationStatus.STATUS_PENDING ) {

As shown above for the plus line. May be this is needed, in case due to some 
reason the app was registered but local client app callback was not done.

After that it is able to register for push and getting a cn1 push id.

Thanks,
Nirmal

Original comment by nir...@nvsoft.com on 19 Sep 2013 at 10:53