[17:30:07] <matanya>	 bearND: did you have a chance to see my comment regarding my login problem into the app
[17:34:05] <matanya>	 https://phabricator.wikimedia.org/T150529
[17:54:21] <bearND>	 matanya: I just responded on the ticket. BTW, niedzielski is current Android tech lead. We rotate this responsibility around every  6 months.
[17:54:59] <matanya>	 aha, cool,  thankd bearND 
[18:48:39] <kaartic>	 hello all, I am noticing something weird with the explore in the bottom navigation bar in the wikipedia alpha app.
[18:48:56] <kaartic>	 It doesn't seem to be displaying correctly all the time
[18:49:13] <kaartic>	 Sometimes the Wikipedia logo shown in the top bar in the explore feed also doesn't seem to be displaying correctly (i.e.) sometimes some letters are missing
[18:49:33] <kaartic>	 Is this a known issue?
[19:04:21] <olliv>	 dr0ptp4kt: product planning?
[19:04:44] <kaartic>	 correction: explore in the first message refers to the "explore icon"
[19:04:45] <dr0ptp4kt>	 olliv: there shortly
[19:14:40] <niedzielski>	 kaartic: i don't think so. if you can repro, would you mind reporting a bug here? https://phabricator.wikimedia.org/tag/wikipedia-android-app-backlog/
[19:14:59] <niedzielski>	 (there's a link in the sidebar for reporting bugs)
[19:19:49] <jdlrobson>	 hey niedzielski 
[19:20:01] <jdlrobson>	 do you have to test on a local instance? Or could you point to a parsoid/beta labs instance?
[19:20:17] <jdlrobson>	 importing templates is always a bit of a pain
[19:20:59] <niedzielski>	 jdlrobson: hm, i was just assuming that most devs use local instances and had some secret sauce i didn't :]
[19:21:39] <niedzielski>	 jdlrobson: for a parsoid / beta labs instance, are you mirroring a wikipedia or how would that be different?
[19:22:06] <kaartic>	 niedzielski: I am able to see this at random intervals. Not sure if this is reproducible all the time. What I have for proof is a couple of screenshots showing the problem ? Is it the  worth creating a bug if it's not reproducible at random intervals?
[19:22:39] <kaartic>	 *sorry about that ? after the third sentence
[19:23:02] <niedzielski>	 kaartic: screen shots would be perfect! repro steps are ideal but at least a clear demonstration of the bug is really helpful
[19:23:14] <niedzielski>	 kaartic: so i say make the bug :]
[19:23:19] <niedzielski>	 er, phab ticket
[19:23:24] <jdlrobson>	 niedzielski: oh you want to test on mobilefrontend?
[19:23:44] <kaartic>	 niedzielski: ok :)
[19:24:11] <jdlrobson>	 niedzielski: you can cherrypick https://gerrit.wikimedia.org/r/313611 and use MCS :)
[19:25:37] <niedzielski>	 jdlrobson: well, i have changes in mobileapp and mobilefrontend. that looks like it would be good first test for the mobilefrontend changes!
[19:34:06] <maxbinder>	 nataliaharateh: FYI you should join #wikimedia-ios if you have not
[20:09:02] <coreyfloyd>	 dbrant: i just noticed that the set-cookie header isn’t on requests the first time on a fresh install. Is there a particular API that causes this header to start getting set?
[20:09:43] <dbrant>	 coreyfloyd: hmm, that shouldn't be the case.
[20:10:18] <coreyfloyd>	 definitely seeing it… 
[20:10:33] <coreyfloyd>	 i have to close and reopen the app to get it to start working
[20:13:09] <dbrant>	 i'm getting it on the very first response (in our case from RestBase, but you should get it from api.php as well).
[20:18:44] <coreyfloyd>	 dbrant: weird
[20:19:51] <coreyfloyd>	 dbrant: the first call yo make to the announcements end pint or the first call you make to any rest base api?
[20:20:27] <coreyfloyd>	 and also… are you making any other calls in the app first before calling the announcements endpoint?
[20:21:12] <dbrant>	 coreyfloyd: our first call is to the aggregated feed endpoint. I'm just about to wire up the call to the announcement endpoint, which will become first. I'll let you know if I get the cookie then.
[20:24:37] <coreyfloyd>	 dbrant: ok - actually the issue is different than i suspected… sometimes the cookie just isn’t there
[20:24:56] <coreyfloyd>	 dbrant: not sure how to repro yet
[20:25:52] <dbrant>	 coreyfloyd: i'm pretty sure the server will always send back the cookie, as long as you don't include it in your request.
[20:26:40] <coreyfloyd>	 dbrant: oh… so we don’t manually control the cookies in the app really… so basically we need to guarantee that cookies aren’t sent with this request
[20:29:01] <dbrant>	 coreyfloyd: when the app is first installed and launched, it should always receive the cookie because it doesn't have it yet. That's really all we're looking for.
[20:31:35] <coreyfloyd>	 dbrant: ok - I was checking on every request
[20:31:43] <coreyfloyd>	 looking now and confirming that behavior
[20:31:52] <coreyfloyd>	 we are sending the cookie back
[20:32:48] <dbrant>	 coreyfloyd: yeah, that's kind of a "limitation" -- you won't be able to "update" the user's location unless you clear the cookie manually.
[20:39:51] <coreyfloyd>	 dbrant: got it… just checking the cookie and the header now
[21:58:02] <jdlrobson>	 Volker_E: can you be in the office tomorrow?
[22:09:08] <maxbinder>	 nzr: you coming to meeting?
[22:17:35] <nzr>	 maxbinder: coming
[23:15:08] <Volker_E>	 jdlrobson: tomorrow is my bday and I'm def not in the office :P
[23:15:16] <jdlrobson>	 booooooo to getting old!
[23:25:55] <Volker_E>	 jdlrobson: true dat