Originally Posted by ctpuk
@MisterGriffiths - thanks for your reply. Most
One thing I learned along the way... I didn't fully appreciate the whole "unlisted applications" thing. So when creating a test software config I, at one stage, set "disposition for unlisted applications" to "disallowed". This forcibly removed every 3rd party app from my device other than those explicitly defined in that s/w configuration (thankfully I only tested on mine!), including 3rd party apps that are on the device as standard (e.g. yahoo chat, google talk, twitter, facebook, bb app world, etc). This is probably just my naivety and lack of experience on display to be honest so I expect most of you are probably thinking "duurrrrr... of course it'd do that"... but just in case you're on the same page as me... learn from my mistake!
The exact same thing has happened to me, except I didn't have the sense to do it on a test handset first. That was fun!
What I do with our apps is ensure that all of their software configs are set to OPTIONAL, rather than REQUIRED. Optional rolls out the app in the exact same way, but allows the apps to be removed in a more straightforward fashion.
Don't know if this applies to your situation (you mention you have custom ACPs, how many different layers of control is it possible to implement, RIM?!), but I've found it saves a lot of grief.