Adobe AIR Development

[Smugrik]

Hi, I am debugging my app on the real PlayBook,

I decided to change the application id in the -app.xml, since then I get a "500 unexpected override" error when trying to launch the app from FB4.5.

Browsing this thread 500 unexpected override when launching app I understood the problem came from the application ID being changed, but not the internal package ID used to reference the app in the PlayBook.

This is verified by looking inside the generated bar file, for both old application id and new application id, the package id stays unchanged. (I believe this is actually a bug in the SDK, I'd love to have confirmation of this from someone knowledgeable)

so I thought OK, I'll just delete the app from the PlayBook to erase the old applicationid-packageid association and reinstall...

but still no hope.

So here is a detailed description

old application id was myOldAppID

new application id is myNewAppID

generated package id: myPackID (same for both application ID)

it seems the PlayBook keeps a list of all apps that have ever been installed on it: I tried deleting the app from the command line using blackberry-deploy and the package id (obtained from the .bar):

blackberry-deploy -uninstallApp -device 169.254.0.1 -password *** -package-id myPackID

The app is deleted as expected, it is removed from the PlayBook menu, the command prints the result

Info: Sending request: Uninstall
Info: Action: Uninstall
Info: Uninstalling myPackID...
Info: Processing 0 bytes
actual_dname::myOldAppID.debug.myPackID
actual_id::myPackID
actual_version::
result::success

From the result, we see that the PlayBook finds the old reference to my App, and displays its application ID on the line actual_dname

now if I run the same command, but with an obviously wrong package ID:

blackberry-deploy -uninstallApp -device 169.254.0.1 -password *** -package-id someWrongID

 I get the result

Info: Sending request: Uninstall
Info: Action: Uninstall
Info: Uninstalling someWrongID...
Info: Processing 0 bytes
actual_dname::
actual_id::someWrongID
actual_version::
result::success

 note the actual_dname line is empty, there is no reference for the application with package ID someWrongID

here I'd prefer to see an output like "application not found for package id someWrongID" but anyway...

So if I run the same command again, with my application package ID, I expect the actual_dname line will be empty, as the app has already been deleted, but result is still:

Info: Sending request: Uninstall
Info: Action: Uninstall
Info: Uninstalling myPackID...
Info: Processing 0 bytes
actual_dname::myOldAppID.debug.myPackID
actual_id::myPackID
actual_version::
result::success

 Here I see that the PlayBook still holds the old association of myOldAppID with myPackID, even though the app has been deleted...

I tried rebooting the PlayBook, cleaning and rebuilding the project, all to no avail... the reference stays in the PlayBook, and myPackID stays unchanged.

Now I am stuck, if I want to debug my app, it seems I must leave application ID to the old value...

I would like to know, is there a way to fully delete an application, and all of its references, from the PlayBook?

And is there somebody who can explain how Package Id is generated, and if this is a bug or a feature?

Thanks!

[pgarcia · Accepted solution]

Hi Julien,

this problem is supposed to be fixed on the latest SDK version available: 1.1.1. Could you please confirm what command line tools are you using. 

blackberry-airpackager -version

will show you the proper version.

Cheers!

[Smugrik]

I just checked and I have blackberry-airpackager version 1.1.0, I'm gonna give 1.1.1 a try and come back to confirm it's OK, thanks for the hint!

[pgarcia]

Hi Julien,

Did you have a chance to upgrade your SDK? Is everything ok now?

Thanks

[Smugrik]

I installed the new sdk, but couldn't test it yet because I gave my PlayBook to my mother who's in hospital for a few days... I will give you news as soon as she gets out :-)

[Smugrik]

Hi Paulo,

SDK version 1.1.1 fixed the problem with changing application id.

When changing application id in 1.1.1, app is generated with a new package id and gets installed as a new application, as it should be.

Thanks for support!!

[Smugrik]

A few more thoughts,

the issue with the reference of apps being kept in the PlayBook memory is still there, as well as the inconsistent output of the blackberry-deploy tool when trying to delete an app with a false package id...

[pgarcia]

Hey Julien,

we're looking at this two issues. 

Thanks for helping!

Best Regards