Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 22
  1. #11
    Member
    Join Date
    Nov 2012
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    You have useful technical solutions to this problem. I think this is how far we as developers can reach with this issue now.

    I think that the issue is serious and Google needs to investigate it. Imagine a bank which uses a financial software where 0,5% of all transactions disappear and those customers loose their money. The same thing happens here. If customers know that they can loose their money when buying In-app upgrades, they are less likely to buy apps on Google play in the future. The buying ratio is already higher on iOS and this issue is not favorable for Android in the competition with iOS.

  2. #12
    Member
    Join Date
    Nov 2012
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    I think that this is a very serious issue. Imagine a bank where 0,5% of all transactions get lost and those customers loose their money. That is how serious this problem is. It makes customers not want to buy apps on Google play, because the purchasing process is not reliable. This is very damaging to Android developers and to Google Play, especially since the purchasing rate is already higher on iOS Appstore. This issue makes me not want to use
    IAB until it is solved. I am so tired of getting blamed by customers for an error that I am not responsible for.
    Last edited by MobileVisuals; 2016-10-06 at 05:08 AM.

  3. #13
    Member
    Join Date
    Nov 2012
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    We know how to implement In app billing. You don't have to explain this for us. The issue is that Google's servers don't work in 0,5% of the cases, so these customers loose their purchases. We developers can not do anything about this, except to try to inform Google about it, so they fix the problem.

    Quote Originally Posted by adam_jones View Post
    To implement android app Billing in your application, then do the following:

    1:>Add the In-app Billing library to your project.
    2:>Update your AndroidManifest.xml file.
    3:>Create a ServiceConnection and bind it to IInAppBillingService.
    4:>Send In-app Billing requests from your application to IInAppBillingService.
    5:>Handle In-app Billing responses from Google Pla

  4. #14
    Member
    Join Date
    Nov 2012
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    I totally agree, Adam. This bug is so serious and I have tried to contact Google and inform them about it. I have got no answer so far. I really appreciate Google for their invention of Android , but I don't understand why there is no interest from them in fixing this bug.
    It has so serious consequences for my company, that we are considering to stop all Android development and focus on iOS instead. It just does not pay off to produce Android apps, when there is no reliable way to sell upgrades through In-app billing. My shareholders say that they do not want to invest more in Android app development until In-app billing can be used in a reliable way.

  5. #15
    Member
    Join Date
    Nov 2012
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Does anyone know how to contact Google about this issue?

  6. #16
    Member
    Join Date
    Nov 2012
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    I have exactly the same problem, Adam. It seems like ALL developers and customers on Google play are affected by this.

    oswaldmandus, does your code fix with querying purchases on startup less frequently improve this problem? I mean does it make In-app billing work more often? I understand that you also have the same problem with 0,5% of the customers not getting their upgrade and their paid app. But will querying purchases on startup less often decrease this error rate in some way?

    I mean would querying purchases on startup more frequently (like we have in our apps) increase this error rate?

    Quote Originally Posted by adam_jones View Post
    Customers sometimes report that they don't get the In-app billing (IAB) upgrade to full version, eventhough the apps are carefully tested on our test devices. We use managed IAB in 3 apps. We test through alpha testing and we have not found any problems with upgrading. 2 of the apps have IAB version 3 and 1 have IAB version 5. It is the same problem. The apps are developed according to IAB guidelines.

    Why does this happen? Is there some problem with Google's servers, which causes these IAB errors, which prevents some customers from getting the upgrade? Has anyone else encountered the same issue?

  7. #17
    Member
    Join Date
    Nov 2012
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    I tried to implement your solution with re-checking license and calling queryInventoryAsync() once a week. Do you mean storing a timestamp when the app was installed? Then checking the current time every time the app starts and compare if a week has passed since then?

    What is the purpose of storing the purchases locally in an Internal Storage?

    I actually do not think the solution with re-checking license only once a week will decrease the IAB errors in my case. The reason is that queryInventoryAsync() in my setUpInventory method is only called if the user has not upgraded to full version in my apps. These methods are not called after the user has upgraded, so they can not cause any loss of purchases.

    Quote Originally Posted by oswaldmandus View Post
    That's how it is and the simplest solution for that is not to care - I mean I try to help users with issues but if someone leaves 1 star rating without comment and/or stupid review he/she may GTFO.



    Yes, I use SharedPreferences to save license state and recheck only once a week.

  8. #18
    Junior Member
    Join Date
    Nov 2013
    Posts
    26
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Oh, sorry I was sure you check inventory regardless of current purchase status. In such case there's no need for this. I re-check purchases every week to handle refunds (I issue refund quite if user ask me to do so even to avoid negative review and in such case I'd like to revoke purchase).

  9. Likes MobileVisuals liked this post
    Thanks MobileVisuals thanked for this post
  10. #19
    Member
    Join Date
    Nov 2012
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Quote Originally Posted by adam_jones View Post
    When you utilize the in-application charging administration to offer a thing, whether it's an in-application item or a membership, Google Play handles all checkout points of interest so your application never needs to specifically prepare any money related exchanges. Google Play utilizes similar checkout backend benefit as is utilized for application buys, so your clients encounter a predictable and recognizable buy stream.

    Any application that you distribute through Google Play can execute In-application Billing. No exceptional record or enlistment is required other than a Google Play Developer Console account and a Google Wallet trader account.
    Well, we already know all of this.

  11. #20
    Member
    Join Date
    Nov 2012
    Posts
    150
    Post Thanks / Like
    Mentioned
    0 Post(s)
    oswaldmandus , do you know any way of reporting this bug to Google or how to contact them? You are so far the only one, who has answered and supplied useful information about this issue.

    It is possible to report bugs about open source Android code on https://code.google.com/p/android/issues. In-app billing is included in Play services, which is not open source, so the In-app billing bugs here can not be reported to https://code.google.com/p/android/issues.

    I can not find any developer forum or Google+ community about In-app billing. There are Google+ communities for Chromecast and lots of other Android technologies, but none for In-app billing. I often get complains about In-app billing not working and this is very frustrating. It decreases my motivation for working with this, especially since the errors are not caused by my apps and I can not do anything to fix the bugs!

Page 2 of 3 FirstFirst 123 LastLast

Similar Threads

  1. Upgrade - Mobile App Training for Android & iOS
    By ImagiNET Ventures in forum Android Development
    Replies: 0
    Last Post: 2014-11-03, 05:02 AM
  2. Replies: 8
    Last Post: 2014-04-29, 12:04 PM
  3. Replies: 0
    Last Post: 2014-04-24, 11:19 PM
  4. Replies: 0
    Last Post: 2014-02-14, 03:05 PM
  5. Any Android Developers looking for work?
    By Mitch in forum Android Development
    Replies: 10
    Last Post: 2013-12-16, 11:10 PM

Posting Permissions

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