Restoration didn't work using "production" server (In-App/Qt-/Symbian)

[felipecrochik]

When I try my application using the test server any time I try to purchase a product (after the first) I am presented with the login to the ovi store screen and then get a message saying that "no payment is needed" and my application gets the "purchase complete signal" like it was purchased for the first time. Exactly the behavior I would expect.

The exact same code (after I remove the test_mode.txt file and change the IAP_VARIANTID.txt to my product Id) just ignored that I had purchased the same product and presented all the screens like it was the first time - I ended up being charged for my application again

When I tried to check for upgradable products using the same account I get one as expected but when I try to restore it I get a RestorationNotSupported error.

Is this a BUG on the production server? Is it a delay before the product can be restored after being purchased the first time (even if shows as restorable)?

Thanks in advance
Felipe

[izinin]

Hi Felipe

It looks like there is application packaging problem. Please let me know more about your application to move further in the problem analysis

1. please detail what IAP model your application is to implement : either Nokia DRM or non-DRM, subscription model?
2. you say you have changed VARIANTID.txt content with your production id value, how did you obtain that? The point is product id, if i understand you correctly, shall not be coded in VARIANTID.txt. This file must contain your application ID. Application ID is allocated by OVI Store and updated in VARIANTID.txt during the application signing and DRM encrypting automatically by OVI Store. Application ID initial value is '000000' -- six zeroes. You shall never change it manually.
3. And you mention IAP_VARIANTID.txt is it correct filename in your application?

Regards,
Igor

[felipecrochik]

Hi Felipe

Hi Igor,

[*]please detail what IAP model your application is to implement : either Nokia DRM or non-DRM, subscription model?

I am not using DRM. I just call

pIAPClient->purchaseProduct(productId, IAPClient::ForcedAutomaticRestoration);

When using the testserver (normal mode) after I login I get a simple message saying that no payment is necessary and my application gets the purchaseCompleted signal. When I use the production server after login the I am presented with the "price screen".

[*]you say you have changed VARIANTID.txt content with your production id value, how did you obtain that? The point is product id, if i understand you correctly, shall not be coded in VARIANTID.txt. This file must contain your application ID. Application ID is allocated by OVI Store and updated in VARIANTID.txt during the application signing and DRM encrypting automatically by OVI Store. Application ID initial value is '000000' -- six zeroes. You shall never change it manually.

This may be the problem. I had the 6 digits Application ID assigned to my in-app purchase on VARIANTID. The purchase worked just fine, only the restoration failed. I will give it a try with all zeroes.

[*]And you mention IAP_VARIANTID.txt is it correct filename in your application?

Yes.

Regards,
Igor

Thank you,
Felipe

[felipecrochik]

I changed the IAP_VARIANTID.txt to all zeroes and didn't make any difference as was expected since the issue seems to be with the server side not client.

Is this related to this other issue: http://www.developer.nokia.com/Commu...l=1#post885222

Any other ideas? Is it even worth to worry about the IAP with we can only deploy to a VERY LIMITED set of devices?

[izinin]

Hi Felipe,

IAP_VARIANTID.txt name is correct , if your application has been gone through OVI Store publishing process it has assigned application ID as you mentioned

I had the 6 digits Application ID assigned to my in-app purchase on VARIANTID

-- six zeroes here must be for application before publishing on OVI. So it seems all is correct here

There is only one point : non-DRM model or in other words "subscription model" does not support purchase restoration and you mentioned about having RestorationNotSupported error in the log. Subscription model implies you have to implement a product resource server that will have logic around purchase handling, in this case OVI provides only purchase ticket verification API and UI purchase flow on device. Purchase restoration you have to implement yourself for example by this sequence :

1. user selects a product from catalog list
2. the application obtains user and device id and passes that data along with product id to the resource server
3. the resource server checks by using Purchase Ticket Verification API whether requested product has been bought by this user and device id combination (you can minimize network data round-trip by using a database on server side where to store purchase tickets)
4. if user request for a product is found to be already bought you can allow user to download the item (that will be restoration) or force him to buy the item once again (as it is common for subscription model)

For more details how to implement non-DRM IAP please check
Purchase and restoration with no built-in DRM protection , Purchase Ticket Verification API and sample application found in IAP SDK iap_qt_sdk_0.3.1_24.01.12\Examples\InApplicationPurchase\BuyAndDownloadExample

As Belle supporting it temporary problem with highest priority to solve -- i sure you will not waste your time on IAP implementation.

if you have more questions please ask.

[felipecrochik]

I am not sure we are on the "same page" about this. Let me try again:

This is the flow I would like to see - it makes sense and that currently works with the testserver on "Normal" mode:

1. use clicks a button; my application calls pIAPClient->purchaseProduct(productId, IAPClient::ForcedAutomaticRestoration);
2. Ovi "client" takes over and ask user to enter credentials
3. Ovi client presents product information, including price and "default" method of payment
4. User clicks "Buy"
5. Ovi client presents "thank you" screen
6. User clicks "OK", Ovi client closes and sends signal purchaseComplete to my application

...User happily plays with the application for a long time and eventually has to reinstall it, then:

1. use clicks a button; my application calls pIAPClient->purchaseProduct(productId, IAPClient::ForcedAutomaticRestoration);
2. Ovi "client" takes over and ask user to enter credentials
3. Ovi client check user/in-app content id and realize the user has purchased it already
4. Ovi client presents window saying "No payment is necessary"
5. User clicks "OK", Ovi client closes and sends signal purchaseComplete to my application

What my application does after the purchase signal does not really matter.
IMPORTANT: This entire flow currently WORKS using the test server in normal mode.
When I tried on the production server it failed to recognize that the user had already purchased the product and presented the regular buy flow.

[rstalin]

Thanks wizard_hu,
I still have some question...
PurchaseProduct api in doc said that
If you build purchasable items into your app and use Nokia's DRM encryption,
the API always uses the flag EForcedAutomaticRestoration.

I check the restorableProductsReceived signal that have two item can restore.
If the restorable iap id 823138 and put drmtesttools attach encrypted.dat file in <uid>/drm/resourceid_823138
whether I can let purchaseproduct api adapt EforcedRestroation flag even I don't use any drm library.
Although in fact I build that into app it still can't restore,if I miss something?
Or I need build into app and sumbit it for nokia sign I just can test if restoration work?

[rstalin]

I add a text file into <uid>/drm/data/resourceid_<iap_id> and app have passed qa.
but I purchase can't store.

I purchase itme show below failed message but still got a purchase success sms!?
The message is meaning "payment service have problem will guide you back to the app"
why purchase failed still need to pay and restoration how can work.
Someone can help me?

[izinin]

LKM problem is related to your local network operator environment setup , it is also handled by IAP supported team world-wide--- but how soon the problem will be solved i don't know. At least the bug report is filled and handled.

There is workaround for LKM problem -- the idea is to preserve purchase ticket on device in application private directory and then check: if the ticket exists then to allow access to protected functionality. That will work if you don't use actual DRM encrypted content but just verify with DRM file read operation that license is on device. -- From the other hand , following DRM protected model conventions -- i.e. <drive>:\private\<UID>\drm\data\resourceid_XXXXXX\ -- will allow you to use automatic restoration --- for example if user tries to buy already bought product , the product will be restored automatically -- i.e. device will receive purchase ticket but user money account will not be charged. Note if you don't use that convention -- Nokia Store will decide your application implements non-DRM model and automatic restoration will not be available.

This workaround has some risks as your resources are not protected in the application package , ticket may not come and so on , but as temporary solution it is worth to try.

[izinin]

In case you see IAP purchasing problem as money paid but content is still locked , please mail your complaint directly to developer support -- please don't forget to point money transaction details: username and purchase number you can find in SMS confirmation message