Comment by tadfisher

I am a member of the curious club of native Android app engineers working in fintech (banking in particular, but payments is a huge part of the banking business). So I can certainly sympathize with two groups of people:

1. The Vipps mobile team, who have been forced to update the app through some business requirement, most likely compliance-driven, as "politically-exposed person" is straight out of United States banking regulations; thus, the requirement to ask this single yes/no question bleeds through every payment system in the world that could potentially interact with a US bank account, whether or not their customers are subject to said regulations; of which the Vipps compliance team has most certainly, very recently, become acutely aware; hence the Android app's "Update" button, which cannot solve the underlying cache problem in which Google Play Services has not become aware of a pending update to the Vipps app, knowledge currently availed to only the Vipps backend and Google Play installations which have not attempted too many exponential-backoff-retries because they're on a fucking train.

2. Any and all customer service representatives involved, who have to untangle the above to separate requirement from implementation from quirk, find the right person on the mobile team who already knows it's a mess but can't do anything to solve it, and relay the single nonsensical instruction to the customer to resolve the issue: "Settings -> Apps -> See all -> Google Play Services -> Clear cache, reboot".