12-16-2011 12:52 PM
I'm using paymentSDK 1.5 to implement in-app purchasing. I'm having trouble making sure the user is always prompted to upgrade appworld if necessary.
Problem 1: The included PaymentEngine.isAppworldInstalledAndCorrectVersion
Problem 2: I ended up writing a workaround to check installed module versions using CodeModuleManager.getModuleVersion(handle). The version check works, and I can prompt the user to install appworld through the browser, or upgrade it by launching appworld using Invocation. The problem is that when appworld opens, the user may have previously selected 'ignore this update'. Is there an Invocation argument method to force appworld to prompt the user? I considered using the browser so the user would be redownloading appworld instead, which is viable. However I can't test the code right now due to:
Problem 2b: This isn't a development issue, and I cross-posted in general support, but when I open blackberry.com/appworld/download I'm getting "Error: Invalid manifest or application descriptor. The 'Midlet-Name' attribute is missing"
12-21-2011 05:11 PM
Can you please confirm the exact model and OS version of the device you're seeing this issue on? Also, is it a physical device or simulator?
Ideally I would want to confirm/investigate (1) first, and move to (2) and (2b) if necessary (i.e. this does end up being a bug with the APIs.)
BlackBerry Development Advisorhttp://us.blackberry.com/developers/blackberrymess
12-22-2011 11:52 AM
I conducted two tests. The first on a 9900 running 184.108.40.2061, bundle 1346; the newest Rogers bundle available. The App World version distributed with this build is 220.127.116.11; thus the test is expected to identify a newer version of App World to be required.
The sample application I tested:
The results were:
Basically both tests failed. I loaded up a newer OS (18.104.22.1684) which still contained App World 22.214.171.124. Testing on this build (simulator available here) resulted in:
Certainly looks like a bug to me. Can you please report this via the Developer Issue Tracker and our API teams should take it over from there.
BlackBerry Development Advisor