> ...Reinstalled app, had
> to sign out post reinstall (not sure how/why it kept login credentials after removal)
That's surprising! I wonder if it's a clue. As far as I know, uninstalling should cause it to forget who you are and make you sign on again. If it didn't do that, I wonder if something funky is going on. But, I don't know what it might be either. MrBean wrote:
> @bill did you change something? I just got the first notification in forever via
> a pm, but it was 48 minutes behind from when the message was originally received.
I don't think I changed something for that. I did fix the lack of notifications for a mention, that's all.
48 minute delay is also strange and may be a clue. From my experience, notifications are usually immediate. It may indicate your network connection is bad or something. I don't think notifications vary much if you're on wifi vs. cell. The amount of data sent for one if very small.
I'm not sure what I can do to debug this. I can tell you how it works roughly. When you sign on to the app, my server records the device ID of your phone. Then, when an event happens on my server (like someone sends you a pm, offer, or mentions you), it checks if it has a phone device ID. If it does, it sends a notification message to the Google Cloud Messaging service (Google's servers). Google then send the message to your phone (I don't know much about this or have much control over it -- but it usually works well and fast from what I've experienced -- I'm usually on wifi, though).
There can be cases where my server loses your device ID. For example, if you sign off from the app or if I get an error back from Google, I will delete it, assuming the person uninstalled the app or stopped using that phone. I think there's something similar if I just don't get activity from that device for a month or more. But, signing in, should refresh that and put the device ID back. You can also have multiple devices and mix iOS/Android.
The version of Android you're using may matter too. Both of my test devices are Android 6.0.1. Other version may handle notifications differently (but should work as far as I know).
It surprises me that it was already logged in. I did put in stuff that would try very hard to remember login info, but I didn't think it would work this well. I'm fairly sure it's tied to the browser, likely Chrome on Android. So, it's possible that Chrome carried over the saved login info somehow.
You might want to log off and log back in again to see if that gets notifications working.
Notifications are per-device. I keep a table of them on the server. Then, if something happens (like a new pm), it will send the notification to each device that person has.
I just checked and it's showing you have 1 android device registered for notifications at the moment. The last time registration happened was 9:05pm last night. So, that seems different from what you're telling me. If you have 2 phones signed on with the GTZ app, I'd expect 2 registrations. Signing off the app or uninstalling it, should remove the notification registration. Signing on, should add it--but, perhaps the odd way that happened automatically on your new phone caused it not to happen. So, I'd suggest signing off then on again to reset it.