×

Discussion Board

Results 1 to 15 of 15

Hybrid View

  1. #1
    Regular Contributor
    Join Date
    Oct 2009
    Posts
    59

    Having to enter the password twice for in app purchase (IAP)

    Hi,

    I'm not sure this is the right forum to discuss this issue. If you know a better place, please let me know.

    Here is the situation:
    Our Symbian (Qt) app is using IAP with our own backend server. Users are allowed to restore (re-install) content based on our own restoration policy. The information whether or not a user is allowed to restore a content item is stored on our backend and referenced by the users Nokia Store account name.

    So in order to find out if a user is able to freely restore an item we get the account name via the IAP API. Then we send that account name to our backend server which returns whether or not the item can be restored.

    In case it can be restored we download that item bypassing IAP completely, which is no problem. In case it cannot be restored we start the purchase process via the IAP API.

    This basically works fine, but the problem is that the user has to enter the Nokia Store password two times in a row.
    1) To get the Nokia Store account name [ IAPClient::getUserAndDeviceId() ]
    2) To start the purchase process [ IAPClient::purchaseProduct() ]

    This is really bad for the user experience. Does anyone know a way around this issue? Am I using the API in a wrong way?

    Help would be highly appreciated :)

    Thanks!
    Conny

  2. #2
    Regular Contributor
    Join Date
    Oct 2009
    Posts
    59

    Re: Having to enter the password twice for in app purchase (IAP)

    Could someone please move this to the "Qt for Symbian" forum. I think it would fit better there.

  3. #3
    Nokia Developer Moderator
    Join Date
    Aug 2011
    Posts
    492

    Re: Having to enter the password twice for in app purchase (IAP)

    Hi Conny,

    I've contacted the Technical support team to provide a solution for this problem. I will update you when I receive further information.
    Andrew
    Follow @AndrewAtNokia on Twitter for news and updates about Nokia Publish!
    Andrew is now on Facebook to assist you with any publishing related inquiries.

  4. #4
    Regular Contributor
    Join Date
    Oct 2009
    Posts
    59

    Re: Having to enter the password twice for in app purchase (IAP)

    Thank you Andrew. That's great because I really can't find any information about that. Looks like not too many people are using IAP yet.

  5. #5
    Nokia Developer Expert
    Join Date
    Oct 2007
    Posts
    441

    Re: Having to enter the password twice for in app purchase (IAP)

    Hi Conny,

    IAPClient::getUserAndDeviceId() call accepts flag for silent invocation, IAPClient::OnlyInSilentAuthentication, but unfortunatelly it may fail. In failure case response signal comes with status IAPClient::UserAndDeviceDataHash response == "SilentOperationFailed"

    to diminish user impact you can use the following approach:

    1) on application start call getUserAndDeviceId(IAPClient::OnlyInSilentAuthentication)
    2) check status in the call response if it is "OK", cache the user data,
    3) otherwise call getUserAndDeviceId() with default parameters to pop up user credentials dialog
    4) cache the user data

    Please note user can change his ovi username only by phone factory reset , so i think it is safe to cache user data only once on your application first launch.

    Regards,
    Igor

  6. #6
    Regular Contributor
    Join Date
    Oct 2009
    Posts
    59

    Re: Having to enter the password twice for in app purchase (IAP)

    Hi Igor,

    I thought the user has the option to change user names at will, but if this is not the case saving the account name on the device is actually a sensible workaround. I wonder what the "official" way of doing this would be. To me it looks like this is a use-case the people at Nokia simply forgot...

    Anyway, thank you a lot for your help! I can certainly work with that.

    Cheers,
    Conny

  7. #7
    Regular Contributor
    Join Date
    Oct 2009
    Posts
    59

    Re: Having to enter the password twice for in app purchase (IAP)

    Hi Andrew,

    what's the current state of this? What did the technical support team say? Is there any better place to bring up this issue?
    We're planning to launch at the 1st of March and I'm still looking for a solution that doesn't make my customers run away.

    Thanks,
    Conny

    Quote Originally Posted by Andrew Nokia View Post
    Hi Conny,

    I've contacted the Technical support team to provide a solution for this problem. I will update you when I receive further information.

  8. #8
    Nokia Developer Expert
    Join Date
    Oct 2007
    Posts
    441

    Re: Having to enter the password twice for in app purchase (IAP)

    Hi Conny,

    I am from Techsupport and my advice has been already sent in this discussion thread --- in the API there is no way to force suppressing credentionals input dialog in getUserAndDeviceId call. The call parameter OnlyInSilentAuthentication flag value does not garantee the dialog will not be shown it depends on whether the user credentials were already cached on the device.

    Please implement work around in your application --- don't call getUserAndDeviceId() each time you need to provide the data to your backend , use cached data instead:

    1) on application start call getUserAndDeviceId(IAPClient::OnlyInSilentAuthentication)
    2) check status in the call response if it is "OK", cache the user data, to use it during the application session
    3) otherwise call getUserAndDeviceId() with default parameters to pop up user credentials dialog
    4) cache the user data, to use it during the application session

    Regards,
    Igor

  9. #9
    Regular Contributor
    Join Date
    Oct 2009
    Posts
    59

    Re: Having to enter the password twice for in app purchase (IAP)

    Hi Igor,

    thanks for writing me again. I'm sorry I didn't realize that you are from Techsupport and thus I was looking for an official answer. Well, now I know it's official

    I understand the work-around you described. Unfortunately I don't think it's a work-around because after starting my app the silent call to getUserAndDeviceId() _never_ succeeds. Because of that after starting the app the user _always_ has to enter the Nokia Store password just to see the content. That is totally user unfriendly.

    The other option (calling getUserAndDeviceId() just before purchaseProduct()) is also no option because it brings up the password dialog two times in a row which is even worse.

    I really appreciate your help Igor, but I'm totally disappointed by the IAP framework. It would be great if you could create an internal bug report on that issue. And if you're on it: The IAP framework needs around 3 seconds to load. During that time the UI freezes and the display flickers. But that's another issue...

    Well, I'll try to find a solution to this problem. Maybe I'll bind the purchases to the IMEI or IMSI (that I can get via Qt Mobility) instead of using the Nokia Store user name. That's not as nice but might save my users from a flood of password dialogs....

    Anyway, thank you very much for your help!
    Conny

Similar Threads

  1. Uninstalling a password protected when not knowing the password
    By mehmetgns in forum Symbian Signed Support, Application Packaging and Distribution and Security
    Replies: 18
    Last Post: 2011-06-08, 07:37
  2. In app purchase
    By remy_david in forum [Closed] Publishing to Nokia Store
    Replies: 6
    Last Post: 2011-01-12, 17:58
  3. Enter Password in a Password Format
    By meghali21 in forum Mobile Java Networking & Messaging & Security
    Replies: 6
    Last Post: 2009-08-24, 18:50
  4. Enter password before unistalling
    By santu.paul@gmail.com in forum Symbian
    Replies: 9
    Last Post: 2008-11-20, 06:47
  5. TextBox to enter numeric password Ser 40
    By andretr in forum Mobile Java Tools & SDKs
    Replies: 0
    Last Post: 2004-06-14, 20:58

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •