Testing and Deployment

[abx]

When I create a signed package using the BlackBerry 10 NDK, the native packager generates a "manifest.bbr" file that the PlayBook NDK's packager does not generate.   What is the purpose of this file? 

We are using the packager from PlayBook NDK to package builds for BB10 (though compiled using NDK10).  Can we foresee any issues doing so?  Will our apps be accepted if they are missing this manifest.bbr file? 

(we are using the 1.4.2 packager, instead of 1.6)

[MSohm]

You should always package with the packager that comes with the BlackBerry NDK you are building with.  Newer releases will support new features, which older packagers will not.  This could lead to issues installing or running your applications.

[abx]

Thank you for your reply.  We will be switching to the correct packager.   

As for the purpose of manifest.bbr, can you shed some light on this file, which seems to repeat what exists in the .mf?

[MSohm]

I haven't seen this file before.  How are you packaging the application?  Are you building from the NDK (Export -> Release Builder) or command line?  If you built using the command line try using the NDK and let me know if you still see the file there.

[abx]

I'm using the IDE that came with the NDK (using Export).

[MSohm]

You can ignore this file.  It won't be created in the gold release of the BlackBerry NDK.