Jerry Morrison

The problem is _not repeating_ today for any district events that I checked: Week 1 Auburn MV, West Valley; Week 2 Ann Arbor, Mount Olive, Hafia; Week 3 Boston, Mount...

The symptom is back today for the Mount Vernon district event. *Also* in the list of Week 3 events, Mount Vernon is listed under "District Events" rather than "Pacific Northwest...

The debug build is not currently exhibiting the symptom. It's listing Mount Vernon under PNW District Events and not showing the "not part of a district" sub-banner. Stetho's view of...

How about adding some logging for that to the release build? What would it take in the code for an event to appear under generic "District Events"?

Happily, running a debug build of the code in master does not have this bug. But is that because it started afresh fetching data, because of the code changes, both,...

That sounds good: Uninstall the debug build, then run at a suitable old commit, then build and run at the current 3.0.0 beta commit, reproduce the bug, then update to...

I tried to verify the fix by running at 3939fbe^ and a few preceding commits, and then at 3939fbe, but the code throws NPE while fetching the initial data. The...

This bug is still present on an Android tablet. Perhaps the app still needs to delete duplicate rows or use `SELECT DISTINCT` to cope.

I just remembered "glanceable info" #88 . For people who favorited multiple teams, the "glanceable info" home page could show all their rankings and the combined schedule.

The fix is to call `builder.setGroupAlertBehavior(NotificationCompat.GROUP_ALERT_SUMMARY)` before building a notification that will immediately become part of a group summary. But this new method is in supportLibVersion 26.1.0 and compileSdkVersion 26,...