zood / george Goto Github PK

Scenario:
While the pijun api is down, location updates will get backed up on the user's device, and then when the api server actually comes back up, those old updates will needlessly be pushed to everyone's device, causing unnecessary network traffic and processing.

It's always requesting updates, because it's operating on data from the database instead of waiting for what the latest data is from the PackageWatcher.

It already dismisses the info panel; it should also remove the friend's error circle

Only available in iOS 12

https://firebase.google.com/docs/crash/android

It doesn't use utf-8 by default. Similarly, use the overloaded String constructor that takes a Charset as well.

Otherwise, the app will behave like it recently performed an update, even though it may have been using old/cached data.

You may have to add the recipient to a list of people that want the ok.

If the hash fails during registration, then we should fall back to a hashing function with a lower memory limit. If the hash fails during sign in, then we need to let the user know they have to log in from a device with more available memory.

So you know when the server is down

So we can easily add unit tests around it

https://plus.codes/developers

Implement it as a native feature because of memory limitations with libsodium running in (w)asm.js

To reproduce:

1. Create account and log in
2. Set profile photo
3. Log out
4. Create a 2nd account and log in
5. Go to edit profile photo

Expected:
There should not already be a profile photo there

Actual:
There is a profile photo there already. It's not actually associated with your account, but it's loaded in the view

Something is not being deleted

So it doesn't flicker so much

Currently, it updates everywhere, except the marker on the map

That should be done after the account was created on the server