Unable to submit a "Report an Abuse" form

Bug Reports should include the following and any additional information you feel is necessary to aid in the investigation of the bug.

  • Description of the issue
    When trying to submit a report, getting the following:
    image

  • Date first (or most recently) experienced
    2026-09-25

  • Device type, model, and operating system
    Mozilla/5.0 (X11; Linux x86_64; rv:156.0) Gecko/20100101 Firefox/156.0
    Linux 6.12.107+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.107-1 (2026-08-29)

  • Game & Game Version (if applicable)
    Reporting Abuse in Wayfarer — Wayfarer Help Center

Sometimes I get this error message when the Wayspot has already been removed, but the mapview map hasn’t updated. Did you check on the Submit map to see if it is still live?

This is the freeform … form…

oh now I see the link under game version. sorry.

that form worked for me this morning if this helps track down the issue

I was being overly pendantic? :->

And yeah, it worked for me a couple of days ago as well (I meant to include that in the initial report).

no, i just zoned out after
“Device type, model, and operating system”
since that stuff doesn’t mean anything to me. totally my bad.

Try the new form

wait the link they used didn’t redirect?

so theirs was
https://niantic.helpshift.com/hc/en/21-wayfarer/faq/2190-reporting-abuse-in-wayfarer/
and mine was
https://scopelyexplore.helpshift.com/hc/en/10-wayfarer/faq/1999-reporting-abuse-in-wayfarer/

i would never have seen that was the issue. ever.


The headers are different and since Scopely mentioned in the past they’d “keep the old forms open for now” I assume they are actually two entirely different forms, not that the old link would redirect to the new form. Might not actually fix anything, just worth a try. :slight_smile:

Interesting. Same issue with the new link.

FWIW, I had the same problem just a bit ago.

However, this time, I tried doing it in in Private Browsing window (FF’s equivalent of Chrome’s Incognito).

It worked.

I’m not sure why I did not try the usual “delete cookies and other local site data” or even a new profile, before reporting.

But definitely seems to be a local issue.

If I knew how to add the “not-a-bug” tag or whatever, I’d do that.

Cheers!