-
Notifications
You must be signed in to change notification settings - Fork 883
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 P3A #7016
Android P3A #7016
Conversation
c3b6b24
to
3051388
Compare
Current state: Works initialization
Works upload
Works lots of metrics:
At least doesn't work |
3051388
to
fdd2c76
Compare
Here is a table of all metrics to keep understand what works and what doesn't For items left blank I don't know the answer yet.
|
600f6bf
to
24b0e13
Compare
a1f827f
to
27e54cc
Compare
@jamesmudgett @bradleyrichter could you please review the UI changes? (mostly standard controls) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
++
android/java/org/chromium/chrome/browser/preferences/BravePrefServiceBridge.java
Show resolved
Hide resolved
Looks great |
components/p3a/buildflags.gni
Outdated
@@ -1,5 +1,5 @@ | |||
import("//build/config/features.gni") | |||
|
|||
declare_args() { | |||
brave_p3a_enabled = !is_ios && !is_android | |||
brave_p3a_enabled = !is_ios |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIU, is_ios
is redundant, because we don't build p3a on ios anyway. So I suggest to drop the whole buildflag
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't know that, I know that a lot of brave-core code is used on iOS, especially for rewards and sync now.
if we drop !is_ios
, I would like to put the comment that p3a is not used for iOS, like
# for iOS P3A is not used
brave_p3a_enabled = true
so to keep the existing for me seems good because it is self-described line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIK generally we don't use is_ios
since it wouldn't work anyway, only selected components you mention support that. So I think we should be safe to drop the flag - @bsclifton could you help us?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
iOS guys told it should be safe. I will remove that guard and run CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI for iOS succeeded with that change 95553fa
27e54cc
to
ad8ab49
Compare
macOS build failed by reason
hard to believe it is caused by this PR |
macOS CI failed for test-install
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving to unblock the merge, but would like to have P3A buildflag removed
95553fa
to
cfb2f36
Compare
Windows CI comleted with status UNSTABLE. One browser-test failed and one timed-out
both are not related to the PR |
Resolves brave/brave-browser#6176
Submitter Checklist:
npm run lint
,npm run gn_check
)git rebase master
(if needed).git rebase -i
to squash commits (if needed).QA/Yes
orQA/No
) to the associated issuerelease-notes/include
orrelease-notes/exclude
) to the associated issueTest Plan:
I. Clean install
Automatically send completely private product analytics to Brave
is uncheckedAutomatically send completely private product analytics to Brave
is still uncheckedAutomatically send completely...
checkbox,Automatically send completely...
is still checkedII. Update install
Advanced test to ensure PR is ready for onboarding changes, requires code change between runs, is not possible to perform by QA team
=====
comment out
and uncomment
at
src/brave/android/java/org/chromium/chrome/browser/app/BraveActivity.java
III. Ready for onboarding, clean install
Automatically send completely private...
is checked(P3A should be disabled or kept enabled by onboarding wizard, follow up issue)
IV. Ready for onboarding, update install
5.1 press
Learn More
ensure pagehttps://brave.com/P3A
is opened5.2 repeat 5.1-5.4, press cross, ensure
Automatically send completely private...
is checked5.3 repeat 5.1-5.4, press
Disable
, ensureAutomatically send completely private...
is unchecked5.4 repeat 5.1-5.4, press
Got it
, ensureAutomatically send completely private...
is checkedReviewer Checklist:
After-merge Checklist:
changes has landed on.