[BUG] Attack mails stopped after removal of GMAIL from Google account.

I've been trying to escalate this through Niantic support but they don't seem to get any further then having me de-activate and activate settings, reinstalling the app and getting a new phone in order to solve this issue that I believe can't possibly have anything to do with my hardware. So I'll just put this here.

I've got a private domain which I use to receive e-mail on and send e-mail from. I"ve had this for years. I used to have some kind of frankenstein's abortion in place to make this arrive at my random gmail account because Google doesn't actually allow for custom domains outside of their Google Apps space. This works, but has some disadvantages like a delay in mail traffic which is less then ideal when you're beeing sent two-factor codes.

So recently I moved it away from that sub optimal situation to a different provider and made that whole thing neat. This move generated said gmail redundant to I opted to remove the gmail service from my google account. From that point onward I stopped getting attack notifications.

I tried:

  • Reinstalled the app
  • Switched mail settings arround several times.
  • De-coupled and subsequently re-couple (the same) google account.
  • Logged in with my facebook account.

The attack notifications themselves I don't really care all that much about but the same mail system also sends out communication regarding portal approvals and whatnot and possibly also codes for bought anomaly kits so that's a bit of a thing.


  • NineBerryNineBerry ✭✭✭✭✭

    Where would they send the email if you are logged on using your Google account but don't use its email address?

  • Kevinsky86Kevinsky86 ✭✭✭
    edited September 2019

    My e-mail address is associated with the google account. Ingress also knows it as it is visible in the settings.

    You can have a Google account without Gmail, you just sign up with a different address and login to google (and thusly ingress) with that instead of Gmail.

  • I've just received feedback from support that this is a known issue with no timeline of a fix.


    I do have to say I like the in-app support access in Prime though.

Sign In or Register to comment.