Cascades Development

[dbigham]

I've used the sample project provided for adding "invite to BBM" functionality to my app.

When I test it out, the invitation shows up on the BB device, but when I click "OK" to download the app, I get an error:

"Baby Names is not on App World.

Launch App World anyway?"

... is this to be expected?  This app *is* live on App World, so I just want to be sure.

Thanks,
Daniel

[peter9477]

Are you running a development mode version of your app, or a signed one? And if signed, is the id definitely the same?

[dbigham]

Good question... I was using a debug version of my app.

That said, when I sign my app and deploy a release version to my device, initiating the invite feature starts promising in that it says that BBM is connected, and then as it is opening the invite screen, it suddenly reverses course and closes the invite screen before it's fully opened.

Boo. That can't be good. Why on earth would it behave differently in debug deploy VS release deploy?

[dbigham]

Well apparently the debug version isn't working anymore either.

Sigh.

I had been using/testing the debug version fine for 1.5 hours. Look great. Compiled release version, submitted to app world.

Then went back to debug mode and it's no longer working. Didn't change any code.

Pretty frustrating...

[dbigham]

RegistrationEventHandler:ushPermissionEvent : - "Success" -
ApplicationDelegate::notifyRegistrationEvent "Success"
Received a BBM Social Platform registration access state= 0
Ignoring BBM Social Platform access state= 0 when progress= 0
ContactListEventHandler:ushGetPlatformContactListEvent
List Updated! - size 0
Received a BBM Social Platform registration access state= 0
Finished BBM Social Platform registration, success= true temporaryError= false
entering MessageServicePrivate::MessageServicePrivate
InvocationManager:ushDownloadInvite "{"contactPicker":{"gid":"900","payload":{"DownloadContactPicker":{}}}}"

[dbigham]

Ok, so something funny is going on.

I eventually gave up, crossed my fingers, and restarted my dev alpha.

When I did, the debug version of the app started working again. (able to show the invite screen)

I deployed my signed version, and it would fail.  

I re-built another release version (unsigned), deployed it, and it worked ok.

So I signed that version, and deployed it, and it wouldn't work.

So I crossed my fingers again, rebooted my device, and tried the newly signed version, and it would finally work.

So, something strange.  It's as if you use a non-signed version of an app and connect it to bbm, then the signed version won't be able to trigger the invite function until you reboot your device.

[dbigham]

The other curious thing is that if I send an invite (with either the non-signed or signed) version of the app to my bold 9900 (instead of my wife's curve), then the message is:

Rather than:

"Baby Names is not on App World.

Launch App World anyway?"

It is:

"This app version is not available

on App World.

Launch App World anyway?"

[mzex · Accepted solution]

Final step of BBM invitation for dowload, is possible only when your app is on AppWorld, and downloaded from it, otherwise it would not work.

[peter9477]

Yeah, that's why I asked in the first place. The unsigned version has a different app id, so of course you can't download it from BB World. As long as the contact picker comes up though, it's working fine, since anything after the sendDownloadInvitation() call is out of the hands of your app anyway (it's an asynchronous call and you never hear back about the results).