As promised, we wanted to share a brief post mortem after a lot of our Android users experienced problems with the bunq app yesterday evening 18:22 - 22:19. Let's delve right into what went wrong.
What went wrong and how are we fixing it?
Our process of launching a new app version is mostly automated, but also includes some manual steps. In one of these manual steps, we hit a problem caused by local cache. As we are now moving to continuous deployment for all our platforms, it's not possible for this particular step to fail in the future.
Unfortunately this particular problem also only became visible on the live app version, any build that was used to test was not affected by the problem.
Releasing the fix
Only a few minutes after we found out about the crash, we submitted a fix to the Play Store. This process is fairly straightforward, except that Google needs between 3 and 48 hours to process the release. At 22:19 we got the good news that the fixed release was live.
