Bug Report: capture/upgrade in missions does not advance highlighted portal to next
Today I was test-walking an all-capture banner I've created, and the "cursor" (i.e. the highlighted portal) gets stuck on the first portal in the mission - it doesn't advance to the next once you've captured the portal.
The SFX correctly indicates "waypoint in range" and "objective met" once you've captured it, and the counter ("02 of 07") at the top continues, but the highlight/nav is stuck on the first portal
I had to open click the portal details to see which portal was next all the time.... which was.... not a very good experience at all
Example video of gameplay: http://youtube.com/watch?v=00YcQAfxodk - at roughly 1 minute I cap the portal, but the cursor stays on it, while the counter at the top increases.
Device: iPhone 7
OS: iOS 12
App verison: 2.32.2.2101f14c
Comments
I had this occur on a capture/upgrade mission that required the waypoints in a specific order. I had to switch to redacted (this happened over the weekend before S[R] retired) to complete the mission.
I also successfully completed in Prime a capture/upgrade mission that same day that did not require a specific order. It did not advance to each waypoint properly, but when I reached each successive portal, it did advance then.
Bottom line -- capture/upgrade missions are not working right.
Device Samsung Galaxy J3
Android 7.0
App v 2.32.2
It appears there's a fix in the upcoming release - let's hope it resolves it!
"Bugfix: Mission waypoints update after portal capture or upgrade."
Also, this was the description of this bug given in one of the IngressMosaik telegram chats: (NineBerry)
"It's the same bug related to the new checkmark. When the checkmark is not shown because you are not in the map view while your mission action is registered, the progress gets stuck. Capture/upgrade works when you are very quick to close the portal screen after deploying one resonator. If you aren't fast enough, you have to restart the app or get the next mission objective from the list manually"This issue has been fixed in 2.33. Didn't see it today playing missions on 2.33.