BlackBerry® World™ Development

[gyubok]

Make sure your App World version is 3.0.1.29 as it was fixed approx a month ago.

Also, make sure you're entering the correct SKU.

[Roshni]

I upgraded to BlackBerry App World to 3.1.0.56 version and my Wify is also connected and working properly but still I am getting message as below even after entering the correct SKU in the pop-up:

"We cannot connect you to Blackberry App World. Please ensure that your device is connected to the wireless network and try again."

Does anybody have any clue what's wrong here? 

Thanks,

Roshni

[himanshupatel]

I am also having the same issue as Roshni,Can any one from Blackberry team suggest some sollution.

Please give your inputs

[oros]

Hello all,

I've reproduced this issue on a 9900 running App World 3.1.0.56 this morning. I'm reaching out to our App World team for more information on the status of this and will follow-up here. If you are also still seeing this issue, please stay tuned; I'll do my best to provide an update ASAP.

Erik Oros

BlackBerry Development Advisor

[oros]

Hello again all,

I need to attribute my previous repro of the issue to user error unfortunately. After adding my specific BBID to the Sandbox users section within my App World vendor configuration, I am able to access the application download just fine.

If anyone is still seeing this issue, could you please verify that your BBID is included as a Sandbox user and if so, provide the App ID/SKU being tested?

Erik Oros

BlackBerry Development Advisor

[Roshni]

Hi Erik,

Thanks for the reply.  Previously I was giving the SKU Id which i gave while registering the product on vendor portal.  But actually I was supposed to give the product id for downloading the draft application.  

The problem is resolved now.

The other thing I observed is that the sandbox id's are case sensitive.

BR,

Roshni

[himanshupatel]

Hi Erik,

The issue i am facing is with Payment api jar 1.5 On OS5 it gives below error when i called PaymentEngine.purchase()

IllegalArgumentException: classname does not exist in the current application package

Now as per documentation it says that with Payment Api 1.5 they support >= OS5.0 but payment api 1.5 works fine with OS6. same jar has above issue on OS5.0

can you help me here I am bit trouble now due to this.

Need Payment service SDK 1.0  or sollution to this issue . Please help urgent.

Thanks In Advance

[himanshupatel]

Hi Erik,

The issue not reproduced if the same code executed as part of UI Application,

But for MIDlet type of application we find this issue.

Please help, we are in critical stage.

Somebody from Blackberry.Please help urgently.

Himanshu

[Roshni]

Hi Erik,

I am also facing same issue as himansupatel.

My application is a MIDlet application.  This issue is arising in OS5 device only, in OS6 and OS7 device it is working properly.  Seems that some issue is coming in paymentapi.jar while using the Registry api. (I have tried using both version of paymentapi.jar - 1.0 as well as 1.5 but the issue remains same.)

Debug information is as follows:

RegistryImpl.verifyClassname(String) line:1170

RegistryImpl.getRegistry(String) line:168

Registry.getRegistry(String) line: 304

f$TestMidletInApp.b() line:142

f$TestMidletInApp.a() line:126

f$TestMidletInApp.a(PurchaseArguments$TestMidletInApp, int) line:67

f$TestMidletInApp.a(PurchaseArguments$TestMidletInApp, int) line:27

PaymentEngine$TestMidletInApp.purchase(PurchaseArguments$TestMidletInApp) line: 208

MyScreen.fieldChanged(Field, int) line:65

The message in IllegalArgumentException is : "classname does not exist in current application package."

Supporting OS5 devices are very important to us so if anyone has any idea related to this issue then please reply, its urgent.

If not anyone than I hope Blackberry Development Team has some answer to this issue.

Thanks in advance.

-Roshni

[oros]

Hi guys,

There have been reported cases where the Payment SDK does work with MIDlets on 6.0+, however MIDlets are not officially supported in conjunction with the SDK.

It's something that's being looked into, but currently no workaround exists for 5.0 MIDlets, or even MIDlets in general that are not working with the Payment SDK.

The recommendation is to create a RIM application for full support.

Erik Oros

BlackBerry Development Advisor