Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
06-27-2011 12:26 AM
Is there a way to update the Product Description for an app at the same time a new version of the app is submitted? I just tried it and it looks like 2 separate requests have to be made -- one to update the Product Description and another to approve a new version of the app.
I wouldn't want only one or the other to go through -- It should be a both-or-nothing deal so that the app and description are always in alignment. I'm sure both will be reviewed at the same time, however it seems like this should be a single change request ticket rather than 2 separate tickets to avoid any possible errors (approving just one but not the other).
06-27-2011 05:06 AM
yes, would be nice to have a unique ticket for both updates indeed.
Note that the "description" ticket is validated a lot faster than the release ticket - not at the same time, not the same "validator" I'd say.
My "solution" is to specifiy a "pending" closure in the description. When the release is validated, I open a 3rd ticket for the final description....
06-27-2011 11:51 PM
The only way I can think of is to take the app off the market temporarily until both the release and the description are approved. The notorious App World server and client caching also needs to be taken into account.