We’re launching our Election Night Tracker a week early, to get input from the community. Give it a try on the link below and send us your feedback — Do you like it? Would you use it on #GeneralElection#ElectionNight? #ElectionNightTracker
https://t.co/vZr3MFQc3r
Our amazing Lead Front End Developer, Alex, recently co-created the @onewayroad2beer as a countdown to lockdown freedom. There are only 12 days and 10 hours to go until we can have a beer (or coffee) in the park with five friends! Cheers to that 🍻
https://t.co/MjOXjfAa7e
I've done a little website to help us navigate the various stages on the road to (beer) freedom.
Give it a share if you like 🍺
https://t.co/DKhw28UwYI
Code: @apamphilon
Colours: @KatieBaxie
@BryanRahn@_inside So did you launch without a fix? It's hard to know when the cache invalidates itself. Did your app users eventually get the new launch screen?
@BryanRahn@_inside Thanks for getting back. Does this fix work in production? Seems like it could be a bad idea to delete the cache on every app load. Is it an iOS bug?
@_inside Thanks for the tip 😀. I am seeing this issue on a TestFlight build. Do you know if this will also cause a caching issue in the production app if launched?