Bugs with resonator slots
edited October 2019 in App Feedback (Archive)
- Pre-requisite: have grey portal on a map, no matter in range or outside. Steps to reproduce: Tap on the portal to open portal menu. Tap on an empty resonator slot right from portal menu. Actual behavior: With probability of ~30% for a given portal (to reset you have to make some ingame actions - I couldn't find which exactly), the resonator slot you tapped will be highlighted - for a moment - but the selection will go to a slot that is neighboring to the slot you tapped. So the slot selected will be wrong. Expected behavior: the slot selected is always the slot which you actually tapped. This same thing can happen on a remote recharging screen, and I have a video of that.
- Pre-requisite: have a portal in range with empty resonator slots. Steps to reproduce: Select an empty slot. Tap "deploy" button. Right away, without waiting for reso to be deployed, select some other slot. Actual behavior: as the previous reso gets deployed ("deploy" button becomes active), the slot you selected gets reset to automatic selection, discarding your slot choice. You have to tap on the slot again. Expected behavior: the slot you selected stays selected after successful reso deploy on previous slot.
Device: Samsung Galaxy J7 2016; Android 8.1
Ingress Prime v2.33.1
Post edited by 1valdis on
When I select a slot for the next (and sometime first) resonator, Prime is constantly changing the selected slot. I understand advancing to the next slot, but when the user selects one, DO NOT OVERRIDE the user's choice!
IOW, if the user selected the current slot since the last deploy action, do not advance!
At the moment of v2.35 these issues are still standing.
Still here in v2.36.
It's been that way since launch. I am not expecting them to fix it any time soon.
Yet the first one is a plain bug, and the second is a parity thing. I want this to be addressed, as it affects speed of manual deploy.
It's not just the speed. When upgrading resonators, it will replace the wrong resonator sometimes resulting in a different level portal than the user was intending (necessary for getting certain level resonators).
As of now (v2.40)
Issue #2 (resonator slot reset) appears to be resolved. A manually selected slot stays selected after the previous reso gets deployed.
Issue #1 has not been appearing for a long time, so probably is resolved too.
Thank you very much, Niantic! :)
Hope @NianticBrian @NianticCasey fix it and update Ingress Prime to 2.40.2