search

android / play-billing-samples

Samples for Google Play In-app Billing
Apache License 2.0
2.38k stars 1.34k forks source link

In-app purchases with multiple accounts #2

Closed TonyTangAndroid closed 7 years ago

TonyTangAndroid commented 8 years ago

Hey there, there will be issue when users have multiple accounts added in device. This is an issue that everyone who has ever integrated android play billing is experiencing. Please refer to this link https://plus.google.com/+ChrisLacy/posts/BAahtLEw9gy or this link for more details. http://stackoverflow.com/questions/28811490/in-app-purchases-with-multiple-accounts#

ashughes commented 5 years ago

@AhmMhd Not every app has user accounts and a server.

boywert commented 5 years ago

This issue hasn't been closed, has it?

wingsuit commented 5 years ago

Man this issue is frustrating, I use a personal account for all my apps and ever since I added my schools google account apps have started reporting that their subscriptions are no longer valid....

Another issue related to this is the fact that in app purchases seem to default to a specific account with no way to switch, even when going to the play store and changing which account photo is selected.

huehnerlady commented 5 years ago

I am frustrated with this issue too.

I did buy a pro version (no subscription, one time buy) with an old account. Now using my new account I cannot see the pro features unless I actually select my old account as my default account in google play. But this in exchange means that other subscriptions won't work anymore.

I wouldn't mind it so much if there would be a possibility to move purchases to another account, but there isn't.

So please finally fix this issue that seems to be there for so long!

arberg commented 4 years ago

Yeah I also just ran into problem. To resolve B ashughes mentioned in second post I had to Uninstall, then switch to main account, then switch back to 2nd account on Google play, then reinstall

dnhyde commented 4 years ago

This is so frustrating... I am almost ashamed to develop on Android, no real support from the platform, most of the APIs for devs are just a nightmare... I lost countless hours on the Camera2 API a huuuuge failure! Now I ran into the subscription flow, thinking about using external services rather than play store subs...

LordByron1788 commented 4 years ago

This is so frustrating... I am almost ashamed to develop on Android, no real support from the platform, most of the APIs for devs are just a nightmare... I lost countless hours on the Camera2 API a huuuuge failure! Now I ran into the subscription flow, thinking about using external services rather than play store subs...

Yes we feel the same, awful apis. You think one api is bad, only to find another that is just as worse. This billing github repo has been abandoned also. Poor attitude from Google.

ashughes commented 4 years ago

Here's a link to the latest version of this bug on the official Google issue tracker: https://issuetracker.google.com/issues/139597485

Please star that issue if it affects you.

gitgeek4dx commented 2 years ago

@netomarin One point of my doubt is why Google made such a setting: The purchases are always related to the account that was selected on Play Store app when users installed the app, and not related to the Google account currently active in Play Store when the purchase occurred. I suggest the latter is obviously more logical, so when users complain about subscription lost, we only need to tell the user, please make sure that you have selected the correct account in the Play store app, instead of telling the user to uninstall our app, and confirm you have switched the Google account to which you purchased our app, and then reinstall our app.

I don't think you can not get knowledge of which account is active currently either. If you guys don't expose the relevant interface, the developer will not be able to get the user's currently logged-in Google account, but as a Google in-app purchase team, you can definitely know which account the user logged in. It is logical to use the currently logged-in account to make a purchase.

Now the situation seems to be that you confuse multiple accounts with multiple users

AndroidDeveloperLB commented 2 years ago

@ashughes For some reason I can't reach the link of the issue-tracker you've shown. I think I could do it in the past, but not now. Maybe Google is finally working on a solution?

casolorz commented 2 years ago

I don't know if it the same issue but the main one discussing the update issues got marked as private. I'm guessing there has been no progress but they got tired of developers complaining.

ashughes commented 2 years ago

@AndroidDeveloperLB @casolorz I can't reach the link either. I actually discovered this back in March and reported it as a new issue, which I also can no longer see. I did take a screenshot of it though:

image

Unfortunately, it appears that now I can't see any issues in the Google Play Billing Library component, even those I created. :frowning_face:

casolorz commented 2 years ago

I guess there were too many complaints about the multiple account bug and they made it all private.

Kaiyusa commented 1 year ago

Hi,

I'm sorry to hear that has happened to you maybe you should try calling customer care they might be able to assist you with your queeries.

,🙂

duanemalcolm commented 1 year ago

I can't believe this has been a problem since 2016 and Google is shutting us out and not giving feedback or updates. It's highly frustrating having to explain this problem to users on a regular basis. I just got a user email me asking why he could not see his subscriptions and whether it's the same Google multi-account problem.

I have suggested just including a "CHECK_ALL_ACCOUNTS" flag when making Google Play Services requests.

This problem is 7 years old. As developers, what can we do? An open letter on Hacker News? Protest? Start submitting issue reports to Google everyday en-mass?

AndroidDeveloperLB commented 1 year ago

@duanemalcolm They have talked about it and gathered suggestions on the issue tracker, and then at some point the post on the issue tracker was closed and nobody can reach it...

casolorz commented 1 year ago

I can't believe this has been a problem since 2016 and Google is shutting us out and not giving feedback or updates. It's highly frustrating having to explain this problem to users on a regular basis. I just got a user email me asking why he could not see his subscriptions and whether it's the same Google multi-account problem.

I have suggested just including a "CHECK_ALL_ACCOUNTS" flag when making Google Play Services requests.

This problem is 7 years old. As developers, what can we do? An open letter on Hacker News? Protest? Start submitting issue reports to Google everyday en-mass?

It is actually much older than 2016, just this issue is from then and it isn't the first one. The issue already existed when I started using in app purchases on 2014. I suspect it has been there since in app purchases were released.

duanemalcolm commented 1 year ago

@AndroidDeveloperLB Yes, I know about the post on issue tracker and it was great when the Google dev was giving feedback. It felt like progress was being made. Now the post is gone private and we can't see anything. We don't know if progress is being made or will this be an issue for another 5 years. It is extremely frustrating.

As @casolorz rightly pointed, this issue is probably 10+ years old. This is just silly.

What I'm asking here is whether there is something we can do to get Google to help because it's my biggest user support issue and I can't do anything about it. I am frustrated.

maickonn commented 1 year ago

I've known this problem for 9 years and to this day they haven't solved it. 🙄

berteodosio commented 6 months ago

We should start celebrating a birthday party for this issue 🥳

hardikbhalodi commented 6 months ago

seems this issue will stay forever!

ysy950803 commented 4 months ago

The bug not fixed 2024. Fuck Google! @google

AndroidDeveloperLB commented 4 months ago

Can't we have some flags of how to handle it? For example: Automatic - choose the account that has purchases if possible. If both have, show dialog to user (which shows information of purchases for each, including when was the last time each was used). Use latest - uses the latest account that was used with purchases. Always ask - show dialog to user which account to use. Default (current behavior) - uses main account. Manual - let us query things ourselves and then show our own dialog (or of Google if that's a security risk).

Once the dialog option is chosen, we should be able to clear-data of the app and start using the selected account from this point. Sadly though, even though the API of clear-data exists, it doesn't have the ability to start the app, but this can be "fixed" by telling Play Services to start it for us afterwards.

Kaiyusa commented 4 months ago

Lol frothing over play store?

Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: AndroidDeveloperLB @.> Sent: Wednesday, May 8, 2024 4:42:19 PM To: android/play-billing-samples @.> Cc: Kaiyusa @.>; Comment @.> Subject: Re: [android/play-billing-samples] In-app purchases with multiple accounts (#2)

Can't we have some flags of how to handle it? For example: Automatic - choose the account that has purchases if possible. If both have, show dialog to user (which shows information of purchases for each, including when was the last time each was used). Use latest - uses the latest account that was used with purchases. Always ask - show dialog to user which account to use. Default (current behavior) - uses main account. Manual - let us query things ourselves and then show our own dialog (or of Google if that's a security risk).

Once the dialog option is chosen, we should be able to clear-data of the app and start using the selected account from this point. Sadly though, even though the API of clear-data exists, it doesn't have the ability to start the app, but this can be "fixed" by telling Play Services to start it for us afterwards.

— Reply to this email directly, view it on GitHubhttps://github.com/android/play-billing-samples/issues/2#issuecomment-2099852268, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A5BJGAZVGNOTQLHLR57MTVLZBHCMXAVCNFSM4BYDEHR2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBZHE4DKMRSGY4A. You are receiving this because you commented.Message ID: @.***>