@matigo Nope. There was an actual mistake in the test code in one case. That wasn’t a problem for Android Studio, though. The other issue was just weird undefined behavior in the JVM of the build server. Solved that by removing that problematic test. The code works correctly on real devices, the problematic cases are covered by tests.
@matigo Indeed. The frustrating part of these ”problems” is that they are caused by backend services that are rigid and have been designed with a totally different communication process in mind. Furthermore, we need to work around bugs that we encounter just because these services have a very high risk of breaking things elsewhere™ if they would get fixed (with a very high cost too, obviously).
Ho hum. A user is having a huge pile of inspected tickets that are not verified by the sales backend. Of course the question is how the app has fucked up. Turns out, as I originally expected, that there was a user-to-device mapping missing from the sales backend. That caused the backend to ignore all those inspection reports. ?
Today I learned that there is a TV series called The Tunnel [imdb.com] where the first episode starts with a body found split in half in the Eurotunnel exactly at the border of the UK and France. That sound eerily familiar from some other TV series…
That leads to question does the French people involved in the investigation speak French while their British counterparts speak English and they understand each other perfectly. ?
@streakmachine Yep. This morning there was a problem of one train station not showing up in the app. Turned out that the problem was that the station data (location, name and its localizations) was not published in a CMS, causing the server the app talks with to filter it out. Once it got published, it just magically appeared there. And this was the app's fault, right?