-
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
Brave Ads fail to migrate confirmations.json if upgrading from builds prior to 1.12.2 if ads were switched off #12260
Comments
Verified passed with
Verified STR from #12260 (comment) Confirmed re-enabling ads from 2 ways: 1. Re-enable Ads via brave://rewards pageInstalled 1.14.19, enabled Rewards. Disabled Ads via brave://rewards.
Confirmed that after updating to 1.17.x, ads were being displayed as per the following:
2. Re-enable Ads via NTP widgetInstalled 1.14.19, enabled Rewards. Disabled Ads via brave://rewards.
Confirmed that after updating to 1.17.x, ads were being displayed as per the following:
Verification passed on
Verified STR from #12260 (comment) Confirmed re-enabling ads from 2 ways: 1. Re-enable Ads via brave://rewards pageInstalled 1.14.19, enabled Rewards. Disabled Ads via brave://rewards.
Confirmed that after updating to 1.17.x, ads were being displayed as per the following:
2. Re-enable Ads via NTP widgetInstalled 1.14.19, enabled Rewards. Disabled Ads via brave://rewards.
Confirmed that after updating to 1.17.x, ads were being displayed as per the following:
|
Description
Steps to Reproduce
Actual result:
Brave Ads should successfully initialize and show ads
Expected result:
Brave Ads fails to initialize due to the migration path and does not show ads. Toggling ads on/off does not resolve the issue. There is no workaround. However, once the user upgrades to a version with this fix their confirmations will be migrated.
Reproduces how often:
Easily reproduced
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: