Infeasible
Status Update
Comments
ce...@gmail.com <ce...@gmail.com> #2
I think that IAB automatically uses the account that was used when installing the application. It seems to me that you used the second account to install it and because of that you were not able to restore the purchases made with the first account.
Don't get me wrong, I'm not saying that this behavior is good, just that there's not a bug in code, but rather in usability. I agree that it should be able for the user to change the account used for IAB, no matter which one was used for the installation.
Don't get me wrong, I'm not saying that this behavior is good, just that there's not a bug in code, but rather in usability. I agree that it should be able for the user to change the account used for IAB, no matter which one was used for the installation.
ma...@gmail.com <ma...@gmail.com> #3
I have information from users that even if you install and purchase in-app items with one account, the in-app will disappear when they add another account, so its not tied to the account that installed the application
ma...@gmail.com <ma...@gmail.com> #4
Addition to step 6.
If the application re-validates the purchases upon start, the purchases will be lost directly without uninstall and re-installing the app.
The validation of purchases always checks the last added account and nothing else.
Please move up the priority for this since its about customer not getting what they payed for.
If the application re-validates the purchases upon start, the purchases will be lost directly without uninstall and re-installing the app.
The validation of purchases always checks the last added account and nothing else.
Please move up the priority for this since its about customer not getting what they payed for.
pe...@gmail.com <pe...@gmail.com> #5
I have many (paying) customers complaining about this issue! Please raise the priority of this issue.
be...@gmail.com <be...@gmail.com> #6
A couple months ago, someone from Google contacted me saying "they will look into the issue". Nothing has happened since then. There is also a g+ post on this. By re-sharing it to different Google groups and communities we might attract more attention to this issue. Here is a link to the post: https://plus.google.com/u/0/111471886409455069782/posts/RognJUHbBfc
hb...@gmail.com <hb...@gmail.com> #7
Hi all, this website is for developer issues with AOSP Android not Google apps or services such as Play Store or Play Services like IAP. Officially you should report your issue to Play support directly by going to play.google.com and clicking help at the footer. Alternatively try contacting Ellie Powers on G+ as she manages the dev console team so may be able to help.
jb...@android.com <jb...@android.com> #8
This report applies to a mobile Google application or service, and the issue tracker where you reported it specializes in issues within the Open Source source code of the Android platform.
We are not able to provide support for Google products in this issue tracker. Please use the Google Support site for help athttps://support.google.com/ or report this issue in the most appropriate Google Product Forum at https://productforums.google.com/forum/#!forum/en/
We are not able to provide support for Google products in this issue tracker. Please use the Google Support site for help at
ai...@gmail.com <ai...@gmail.com> #9
More than 3 years after... and still not corrected?
I'm having this same problem...
I'm having this same problem...
[Deleted User] <[Deleted User]> #10
[Comment deleted]
[Deleted User] <[Deleted User]> #11
Any updates on this after someone changed the status to "WrongForum"? We have users experiencing this issue with subscriptions. Thank you.
nk...@gmail.com <nk...@gmail.com> #12
In Android 6 the problem is still here.
al...@gmail.com <al...@gmail.com> #13
I still see the issue exactly as described 4 years ago. Users are blaming my app for their missing purchases. Please provide a solution!
ma...@gmail.com <ma...@gmail.com> #14
The status of this bug is "won't fix". Maybe Google wants to tell use, how we should use this ill-conceived billing API then? I already figured out a lot of other workflow issues which are obviously not considered by Google, not to mention, that you cannot even test this API in a clean way.
ma...@gmail.com <ma...@gmail.com> #15
Same issue faced in application and no answer.
Does google willing to solve this problem or they happy with this problem.
I think Google watching User and Developer fighting for IAP and they enjoying, and also they privately discuss about how nice finghing.
Does google willing to solve this problem or they happy with this problem.
I think Google watching User and Developer fighting for IAP and they enjoying, and also they privately discuss about how nice finghing.
ga...@gmail.com <ga...@gmail.com> #16
i purchased smart launcher app. but not showed in puchase history and also the app didn't unlock
[Deleted User] <[Deleted User]> #17
Smart launcher мо Может у кого ты работаешь у меня она не работает на моем телефоне он оно висит
ro...@gmail.com <ro...@gmail.com> #18
Подскажите пожалуйста кто нибудь
Не работает у меня телефон с этим приложениям он тупо висит
Не работает у меня телефон с этим приложениям он тупо висит
lt...@gmail.com <lt...@gmail.com> #19
Smart Launcher is still having these issues. I'm pretty sure I've installed, uninstalled, re-installed, and purchased the premium version about 5 separate times now. And it's still giving me the same issue.
se...@gmail.com <se...@gmail.com> #20
ive encountered this issue with Smart Launcher. every time I update the app, I lose access to the pro features. is there a permanent fix for this?
rn...@gmail.com <rn...@gmail.com> #21
Pro Smart launcher
as...@gmail.com <as...@gmail.com> #22
Куууу
as...@gmail.com <as...@gmail.com> #23
Что не так?
gy...@gmail.com <gy...@gmail.com> #24
Yio
ri...@gmail.com <ri...@gmail.com> #26
hi
ow...@gmail.com <ow...@gmail.com> #27
se...@gmail.com <se...@gmail.com> #28
T
Description
1. Make sure you have a single account in Google Play app - Menu - Accounts.
2. Buy an in-app product. You can do this with any app supporting managed in-app products. I tested it with Setting Extended app available on Google Play.
3. Uninstall the app and install the app again
4. The app will "restore purchases" successfully and your extension is active. Everything is fune.
Adding another account:
5. Add one more account via Google Play app - Menu - Accounts - Add account - Ok.
6. Uninstall and re-install the app again
What is wrong:
7. IAB is not able to restore purchases any longer. You product stays inactive.
If you try to buy this product again, last added use account is always used for purchase and any changes in Google Play - Menu - Accounts do not adjust this behavior.
Expected behavior:
When uses chooses an account from the list of available accounts in Google Play - Menu - Accounts dialog, this chosen account becomes active. Now if you start an application it must be able to restore purchases successfully. Alternatively, user must be able to choose which account to use while buying an in-app products.
It is very high prio issue as our apps will be blamed for this behavior and we (developers) have to chance to fix it! This issue is reproducible with the both IAB V2 and IAB V3.
Work-around:
After second account gets removed, everything is working again as expected.