Linking several portals doesn't work correctly
In portal's link screen, if there is one key option to link the action works fine. If there is more than an option and the link order match with the order in which are showed the keys (from closer to further) the action also works fine. The problem appears if there is multiple options to link and I select a different key instead the first showed (i.e. when I want to build a multifield linking the closer portal last), in that case the link button execute the first link but doesn't let me link with other keys, even the key disappear from the list in link screen (but the key is still in my inventory).
In some cases, like mine, a workaround is exit the link screen and enter again. But in other cases, once this bug appears the only way to resolve is to restart the app.
Comments
For me I am forced to wait for each link animation to start, if I do not and spam the link button, it actually cancels the next links in line instead of doing them. As a result, it is still slower than Redacted linking and using the back button to escape animations.
Also, why was cancel link even added to the game? In the past you simply pocketed keys you didn't want to accidentally link to, or you threw it anyway, if it throws it goes.
So technically, this feature of cancelling a link has caused more issues than improving gameplay itself; especially as the window of time to hit the cancel button and cancel a link, is hidden anyway. If we had a timer to show us we can cancel a link, it would make sense. As it is right now it makes no sense.
The REAL truth behind all of it is this: we all want to skip the link and field animations so we can build faster. Since that is the actual case, either remove the animations or give us what we have been asking for, for years: add a checkbox option to disable such animations so we can go back to enjoying gameplay and actually playing the game.
I have had the same issue, also had it where I couldn’t link to a portal inside my multilayer fields (from the anchor) the portal had enough available links, was high enough level and both were fully deployed. The issue was not fixed by multiple restarts but the next day I could throw the link.
I face the same issue. I am using a Xiaomi Pocophone F1 for reference. This bug is costing me links, fields and AP.
In my opinion Prime is too slow, just that. It needs those animation to have time to process everything in the background. Same goes with having to close key after recharging twice (and wait between each X press) - if done too quick, Prime crashes.
Nah, it's not Prime being slow. Linking multiple portals worked great for me in Prime up until about 2.27.whatever. I'd do 15 layers in under 10 seconds by just tapping on the link key repeatedly. They all threw, I checked. This is something that was re-introduced relatively recently.
If you’re firing out multiple links, wait for the animation to start, then tap the screen and go for the next link. Sometimes there’s server lag.
It feels like Ingress does indeed ignore certain links to be fired, when what we really want to do is have all of those links go off in the order that they were submitted.
bugged since 2.229, they have manage to break the best part of prime.
https://community.ingress.com/en/discussion/3350/prime-2-29-2-linking-behaviour
I was throwing a field and noticed that if I link too fast, it flashes an error that the "Link already exists". In reality, it's wrong, no link exists, it's a bug. If I just wait through the animation, this bug doesn't happen, but you are sitting through the animation when you could be powering through links. Any work going into fixing this bug in 2.35?
I had this problem the other night. Two portals were both within range of each other on the scanner, I had keys, and there were only a few outgoing links so it wasn't close to maxing those out. It was like there was an invisible link between the two portals. I check Intel. No links. I went to the other portal to throw back and the same issue. I rebooted my phone and restarted Ingress. Same problem.
In the picture below I was trying to make the purple link, 350m. If offered me the yellow link, though, which was much further away at 1.8km.
I hope next uptade 2.35 fix it. Niantic working on link issues.
2.35 wasn't ready for deployment
Confirmed that a fix is coming in 2.35 for quick linking