[09:21:54] <phuedx>	 o/
[17:53:40] <niedzielski>	 dbrant: i'm still seeing a similar error after running the tests locally. not sure if it's the same issue or something different: https://phabricator.wikimedia.org/P4232
[17:54:02] <niedzielski>	 dbrant: i'm looking into it but if you spot the problem, let me know!
[17:54:11] <dbrant>	 niedzielski: checking...
[17:56:37] <niedzielski>	 dbrant: hm, actually, i'm wondering if this is a proguard issue now that i'm looking at the raw logcat. sorry, that paste was taken from a logcat regex i normally use and wasn't complete. i'll update it
[17:58:03] <niedzielski>	 dbrant: there are some VFY complaints i'd like to check against a couple releases ago
[17:58:10] <niedzielski>	 (on API 16)
[20:11:29] <niedzielski>	 dbrant: i've seen the issue happen just by launching the app but it's very sporadic. it seems to be independent of proguard after all as i had it happen once on a dev build
[20:11:59] <dbrant>	 niedzielski: well shoot.
[20:12:25] <niedzielski>	 devdebug that is
[20:12:52] <dbrant>	 niedzielski: "don't keep activities" enabled or no?
[20:13:20] <niedzielski>	 dbrant: ah, looks like i have that on
[20:13:58] <dbrant>	 niedzielski: i'll try thrashing the app to reproduce, hopefully.
[20:14:54] <niedzielski>	 dbrant: i can't seem to repro it regularly. the couple times it has happened, i haven't been able to introduce any debugging
[20:15:54] <dbrant>	 niedzielski: :/ what can possibly lead to the Client being initialized before app.onCreate()??
[20:16:47] <niedzielski>	 dbrant: not sure. maybe initalization at declaration / static members or possibly a service occurring at the same time as onCreate?
[20:17:03] <niedzielski>	 dbrant: i was wondering if it had something to do with the cookie manager
[20:17:47] <niedzielski>	 dbrant: the npe is on "cookieHeaders = cookieHandler.get(url.uri(), headers);" in JavaNetCookieJar
[20:18:21] <dbrant>	 right, meaning that a null cookieManager was passed into it upon initialization
[20:19:02] <dbrant>	 android lifecycles (╯°□°）╯︵ ┻━┻
[20:56:20] <niedzielski>	 dbrant: so we can merge that new patch in but i don't have a great way to verify it. i've been trying to repro under different network conditions here but it's just not happening
[21:28:08] <dbrant>	 niedzielski: if you're up for it, let's do a beta with that patch
[21:30:13] <niedzielski>	 dbrant: okey dokey
[22:21:54] <niedzielski>	 dbrant: according to the google console pre-launch testing results are currently delayed. i don't think they're worth blocking for but thought i'd ask for a second opinion
[23:02:20] <niedzielski>	 i guess no that delayed. results are good
[23:04:04] <niedzielski>	 ok 160 is out