-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Android] Resolve billing client issues #40078
Closed
3 of 6 tasks
Labels
dev-concern
OS/Android
Fixes related to Android browser functionality
QA Pass - Android ARM
QA/Yes
release-notes/include
Milestone
Comments
deeppandya
added
QA/Yes
release-notes/include
OS/Android
Fixes related to Android browser functionality
labels
Jul 29, 2024
24 tasks
This was referenced Jul 30, 2024
Verification PASSED on
|
Example |
Example |
Example |
Example |
Example |
Example |
Example |
---|---|---|---|---|---|---|
Test Case #2
- Using previous/older account (has subscribed to Premium before)
- download/installed
1.68.128 Chromium 127.0.6533.73
which @deeppandya providedQuick Note:
this APK was signed with a different key to allow IAP using anAPK
- upgraded from
1.68.128 Chromium 127.0.6533.73
-->1.68.133 Chromium: 127.0.6533.73
via the internal test channel - tapped on the
Hamburger Menu
->VPN
->7 Day Free Trial
- ensured that the purchase card was being displayed without any issues
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
dev-concern
OS/Android
Fixes related to Android browser functionality
QA Pass - Android ARM
QA/Yes
release-notes/include
Description
With new gmail account, we are getting the error shown below in the screenshot,
Steps to reproduce
Actual result
Expected result
No error
Reproduces how often
Easily reproduced
Brave version
1.68.x and newer
Device
Channel information
Reproducibility
Miscellaneous information
For QA: billing library was affected, so we should double check nothing regressed in this regard (like subscribing to VPN, Leo and so on).
The text was updated successfully, but these errors were encountered: