Badge number doesn't update when logging in with new account

[krugerk]

Desiderata

Beta Give feedback

1. Is this too corner-casey to care? Answer: yes, no one has or should have multiple accounts
2. Decide whether to fix it for hygienic reasons

Replicata

1. Log in with an account that will have beemergencies soon (UserA)
2. Log out
3. Log in with some other account (UserB)
4. Note the badge shows 0 to reflect the 0 beemergencies of UserB
5. Wait for a zeno reminder (from UserA)
6. Note the badge number now shows the UserA's number of beemergencies
7. Open the app. App fetches goals and updates the badge (again setting it to UserB's 0 beemergencies)

Expectata

That it show the number of beemergencies for UserB and only for UserB.

Resultata

It shows the number of beemergencies for UserA when Zenos are sent. (And then back to those for UserB when one opens the app.)

Circumventata

Open the app.

Nota Nebulosa

• App version: 6.7 (46) from TestFlight
• App/Device receives push/remote notifications only for the currently logged in account.
• Krugerk sees in registering for remote notifications that there is a matching call to unregisterForRemoteNotifications that might be missing (upon logout). Or could it be a backend issue?

Cognata

• Get badge update when emergency day status changes on backend #376
• update badge when signing out #149

Verbata: accuracy of beemergency count,

[dreeves]

This strikes me as too corner-casey to care. It has a fine workaround and no one logs in with different accounts on the same device anyway. But if there's an easy fix, or it's good hygiene to clean things up here, sure.

[DukeCephalopod]

@krugerk as written, expectata and resultata are not actually in conflict: the badge showing stale data is not (necessarily) indicative of any remote notifications being received for the wrong account — reword?

[krugerk]

The badge not being updated upon signing out was also an issue and was fixed with #149.
With this issue, even after logging (userA) and after logging in (userB), the badge is being updated to reflect the beemergencies of userA. I am not sure at which point this stops but it seems to carry on for a day or two.

[dreeves]

expectata and resultata are not actually in conflict

I fixed that just now.