Bug with completing missions
There appears to be many issues when you are doing missions and doing any actions outside of a quick hack / tap hack (when the mission is hack only)
i was doing a banner today and had to force restart the app when it didn’t register my hack doing the following actions before or outside a tap hack:
- Glyph hack the portal about 50% of the time I had to restart the app.
- Fully deploy the portal then quick hack
- linking and fielding and then hacking
- modding the portal
Please look into this as some agents like myself like to glyph to get gear while doing missions.
i also had an agent tell me the same issues and they have done over 4000 missions. This is a very annoying bug.
6
Comments
It's a new bug introduced in the newest update and really annoying.
You don't have to restart the game. Look for what is the next portal in the mission and hack that and the mission progress will correctly update, but it's still annoying.
I think this bug is probably related to the newly introduced checkmark signaling the completion of a mission objective, which in itself is a huge annoyance.
thats time consuming as well. Really hope they fix this before the next set of mission days from 13 Oct.
Just an update on the mission bug I really really really hope Niantic fixes this issue soon. I did a 78 part banner on the weekend where the whole mission was capture or upgrade. I used prime for the first 2 missions but as the action was not just a quick hack once I captured / upgraded the portal the action would not register unless I restarted the app meaning I would of had to restart the AP over 460 times clearly this isn’t an option . I unfortunately had to use redacted to do the whole mission I was so disappointed as I’ve converted to prime a long time ago. Please at Niantic look into this problem soon as it will affect what missions to do 🙏😭
I noticed this problem before (also reported it), biggest problem is that, prime also sometimes forgets that mission is sequential and when you start the mission it shows the nearest portal, instead of first portal...
So you are doing portals in sort of random order... and if distance to next portal is very far (over 150m) you don't even see where the next portal is located (unless you move nearer to that portal)... If you know where portal are supposed to be that is good, but I mostly just followed the instruction from Redacted.... I can't do that with Prime, since Prime doesn't show where I need to go...