I am currently trying to implement in-app purchases into our app in order to provide the option to buy an additional feature.
We have uploaded a draft version into the App World and created a sandbox user. We have successfully bought the draft version on a test device with the sandbox user.
I was also able to successfully perform the in-app purchase with the sandbox user.
Our app usese the following code to check if the user has already purchased the additional feature:
public boolean isLocalPurchase() {
try {
ExistingPurchasesResult result = paymentEngine.getExistingPurchases(false);
Purchase[] resultPurchases = result.getPurchases();
if (resultPurchases != null) {
for (int i = 0; i < resultPurchases.length; i++) {
if (´_DG_SKU.equals(resultPurchases[i].getDigitalGoodSku())) {
return true;
}
}
}
} catch (PaymentException e) {
...
}
return false;
}
After the purchase this successfully returns true, even after a battery pull of the device. But if I turn off Mobile Network and WiFi on the device, the purchase is not found and I get the following error message:
"You do not have sufficient wireless coverage or your connection to the wireless network is turned off."
Isn't paymentEngine.getExistingPurchases(false) meant to perform a local check without connecting to the App World server? Why does it need any wireless coverage then?
But this is not the only problem. If I turn back on Mobile Network and WiFi afterwards, the local check now fails with a PaymentException and the message "Couldn't get get response from AppWorld". This also happens if I use paymentEngine.getExistingPurchases(true) instead. The boolean parameter doesn't seem to make a difference.
I then tried to simply buy the feature again. However this resulted in two NullPointerExceptions that are thrown by the Payment API. This is our code for the in-app purchase:
public boolean purchase() throws PaymentException {
PurchaseArgumentsBuilder arguments = new PurchaseArgumentsBuilder()
.withDigitalGoodSku(OUR_FEATURE_DG_SKU)
.withDigitalGoodName(OUR_FEATURE_DG_NAME)
.withPurchasingAppName(PURCHASING_APP_NAME);
try {
PurchaseResult purchaseResult = paymentEngine.purchase(arguments.build());
serviceRegistry.getLoggerService().debug("Status message: " + purchaseResult.getStatusMessage());
return purchaseResult.isSuccessful();
} catch (IllegalArgumentException e) {
serviceRegistry.getLoggerService().error("Purchase failed", e);
} catch (PaymentException e) {
serviceRegistry.getLoggerService().error("Purchase failed", e);
throw e;
}
return false;
}
And this is from the system log:
Name: NullPointerException
GUID: 9c3cd62e3320b498
Time: Feb 01, 2012 14:51:20
No detail message
net_rim_cldc(4D38A7C0)
Hashtable
put
0x5F0B
OurApp-14(4F1EDAB4)
a
c
0x341
OurApp-14(4F1EDAB4)
a
<init>
0x42A
OurApp-27(4F1EDAB4)
h
run
0xD5F
OurApp-27(4F1EDAB4)
a
run
0x270
net_rim_cldc-2(4D38A7C0)
Thread
run
0xAAC9
Name: NullPointerException
GUID: 9c3cd62e3320b498
Time: Feb 01, 2012 14:51:20
No detail message
OurApp-15(4F1EDAB4)
PaymentEngine
<private>
0x2C8
OurApp-15(4F1EDAB4)
PaymentEngine
purchase
0x113
OurApp-2(4F1EDAB4)
PurchaseServiceImpl
purchase
0xA5E1
OurApp-5(4F1EDAB4)
InAppPurchaseScreen
fieldChanged
0x2EA8
net_rim_cldc-13(4D38A7C0)
Field
fieldChangeNotify
0xB2D
net_rim_cldc-16(4D38A7C0)
ButtonField
<private>
0x85E1
net_rim_cldc-16(4D38A7C0)
ButtonField
trackwheelUnclick
0x84E4
net_rim_cldc-14(4D38A7C0)
Manager
trackwheelUnclick
0x265B
net_rim_cldc-14(4D38A7C0)
Manager
trackwheelUnclick
0x265B
net_rim_cldc-14(4D38A7C0)
Screen
trackwheelUnclick
0x91E7
net_rim_cldc-14(4D38A7C0)
Screen
dispatchNavigationEvent
0x6B8D
net_rim_cldc-15(4D38A7C0)
UiEngineImpl
processMessage
0x6C3C
net_rim_cldc-9(4D38A7C0)
Application
<private>
0x2D18
net_rim_cldc-9(4D38A7C0)
Application
processNextMessage
0x1C3E
net_rim_cldc-9(4D38A7C0)
Application
enterEventDispatcher
0x1B63
OurApp-1(4F1EDAB4)
OurApp
main
0x69AD
Any ideas?
After a battery pull, paymentEngine.getExistingPurchases(false) correctly returns the purchase again, but the behavior described above is reproducable.
. The network connectivity is required even when polling from cache as App World needs to make a call to the server to verify the identity of the application. 
