-
Notifications
You must be signed in to change notification settings - Fork 1.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
Move WordPress Analytics from GravatarApi to WPAndroid #19948
Move WordPress Analytics from GravatarApi to WPAndroid #19948
Conversation
Generated by 🚫 Danger |
@@ -689,7 +690,6 @@ class MeFragment : Fragment(R.layout.me_fragment), OnScrollToTopListener { | |||
fun onEventMainThread(event: GravatarUploadFinished) { | |||
binding?.showGravatarProgressBar(false) | |||
if (event.success) { | |||
AnalyticsTracker.track(ME_GRAVATAR_UPLOADED) |
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.
Just a note here, I removed this one because ME_GRAVATAR_UPLOADED
is already tracked on line 676
AppLog.i(T.NUX, "Google avatar download and Gravatar upload failed."); | ||
// FIXME: Don't track exceptions caused by poor internet connectivity |
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.
Previously some exceptions were ignored. I wasn't sure what to do, this could actually hide some underlying problems like a too short default timeout, so I decided to drop the filter.
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.
It looks better this way. We don't want to hide any exceptions, at least in the app.
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!
This goes with the branch
gravatar/8-change-onerror-signature
To Test:
Try to upload a new gravatar, use network throttler to generate timeout errors or proxy to generate other network issues.
Regression Notes
Potential unintended areas of impact
ME_GRAVATAR_UPLOAD_EXCEPTION
properties have changed, but looking at the existing analytics, I think the changes are actually good, this will help to differentiate the different kinds of error. For details, the Gravatar backend is actually logging those.ME_GRAVATAR_UPLOAD_xxx
are used in the Signup screen, I haven't changed that but the event name doesn't make sense there, we should maybe rename these events:GRAVATAR_UPLOAD_ERROR
andGRAVATAR_UPLOAD_SUCCESS
, this will have an impact on the history and if we do this change, we want to make sure WPiOS does the same.What I did to test those areas of impact (or what existing automated tests I relied on)
What automated tests I added (or what prevented me from doing so)
PR Submission Checklist:
RELEASE-NOTES.txt
if necessary.UI Changes Testing Checklist: