Bug Report: No Linkable Portals Error
During the Didact Field Challenge I had to restart Ingress repeatedly because the scanner would report "No Linkable Portals" before all possible links were actually made. This was already a long and gear-intensive challenge, so having to **** and restart the app well over a dozen times was not a welcome addition to the challenge! It would be nice if future challenges were designed around game mechanics that are less buggy in Prime.
I am attaching pictures of just one example: The first is of a portal ("T.E.U.C.L.A.," Richard Serra, 2006) to which I am attempting to link showing that it is fully deployed and that I have keys to it. The second picture is of the portal (Bound Goat) from which I am attempting to link showing that it is fully deployed and has SBULAs installed to increase outbound links. The third is receiving the "No Linkable Portals" message when attempting to link to ""T.E.U.C.L.A.," Richard Serra, 2006". The fourth, taken after restarting Prime, shows that the link is now miraculously available to throw.
Device: Google Pixel 2XL
OS: Android 10 (Build QQ1A.200205.002)
App Version: 2.40.1-8f435e49




Comments
Same. Portals that are capped are showing as uncapped.
Pixel 2 XL
OS: Android 10 (Build QQ1A.200205.002)
App Version: 2.40.1-8f435e49
It seems the scanner can sometimes "forget" one or more links that can be made from a portal. Restarting the app fixes it. This often happens if some sort of error happens while trying to make that link, e.g., when you try to link and run out of XM, or there are no more outgoing links on the portal; and when you gain more XM or add a SBUL to the outgoing portal it has forgotten that the link used to be possible.
Same issue last night trying to do the Didact challenge. I farmed over 800 keys and had over 200 left over because Ingress failed to link to them. Even after multiple restarts. This error cost me 200-300 fields. Screenshots showing portals that should be linkable not appearing (despite having over 30 keys for each portal and having linked the entire spine initially too).
Device: Samsung Galaxy S10
OS: Android 10 (Build QP1A.190711.020)
App Version: 2.40.1-8f435e49
Snap with 2.40.1 on an S10+. Have had the scanner report no linkables when there are clearly valid links available on a number of occasions. Restarting sorts it.
Restarting the app doesn't "fix" it, though, because it just "forgets" another portal. At best, restarting shuffles the deck so I could throw the previously attempted link only to immediately fail at another. The bug needs an actual fix on Niantic's end, not a poor workaround that requires restarting the app 10 times in an hour.
Moreover, in my recent experience there were no other triggering errors involved. Portals had SBULA pre-installed, I had enough xm and keys, etc. Upon clicking the link button, some portals would just fail to register as linkable.
@cococorey workaround: pack the excessive keys to capsules. In my case Scanner for iOS seems to truncate the possible link combination to a limited number of portals.
The only keys in open inventory were the keys for the portals I was linking to (24 in total), all other keys were already in capsules. If you mean I should be keeping the duplicates of the keys for the portals I am throwing to in capsules, that seems unnecessarily tedious and I wouldn't consider that an acceptable workaround.
Did you pick up some of those keys after flipping the previous anchor?
Generally, no, I was not picking up keys as I flipped. I may have picked up keys once or twice when they were out of range of the other player in the field, but not enough to account for the 20+ times this happened over two evenings.