(Portal scan) notifications, notation bugs
Me: Pixel 4 Android 11 , Ingress Prime ver 2.59.2
Friend: Pixel 4a Android 11, Ingress Prime ver 2.59.2
Please refer to the attached image
I (@fumiso) scanned a portal that no one was scanning and increased the Scout Controller count by 1 (1)
I haven't received a Displaced notification for 36 days
On the 36th day my friend scanned and uploaded it on the spot. (2)
The scout controller before uploading is me (count 1)
My scanner received a Displaced notification when my friend uploaded it. (4)
However, the Scout Controller display is displayed under the name of another Agent who is not a friend, and the friend's Scout Controller does not increase. (3)
Of course I haven't been alerted until then
Consider it unlikely that someone else uploaded the data while your friend was scanning.
Unfortunately This kind of phenomenon occurs several times in "other portals and other areas."
Is this behavior normal?
Loading the portal before scanning does not rename the Scout Controller
Or is the Comm notification wrong?
Display the scout controller correctly.
I want to be notified correctly when the scan data is overwritten.
I believe this is intentional. Your Scout controller automatically expires after 30 days, but the display is only updated after someone uploads a new scan. I assume someone else uploaded a scan within your 30 days, so after your Scout Controller expired, they automatically became Controller with one scan. After your friend uploaded their scan, the display is finally refreshed, showing that the other agent is controller, and as both agents only uploaded one scan, the person that uploaded the scan earlier gets the controller display.
X-0 days: You upload the scan, you are controller
X-7 to 30 days: Agent Y uploads one scan
X-30 days: Your controller expires, Agent Y is automatically new controller, display not updated
X-36 days: Your friend uploads one scan, Display updated, both Agent Y and your friend tie for controller as the scan from Agent Y is still not 30 days old, so older Controller keeps their status
Even if its intentional, the status should be updated automatically.
Furthermore, i will ask to add some kind of marker when i have already scanned a portal
If your friend scanned this Portal and displaced your Scout Controller status with 1 Scout Point, then Portal Details should show their codename and not a random Agent's codename.
@fumiso can you share what is your friend's codename, and approximately what date/time they scanned the Portal?
What @InvestigateXM describes is also possible, but I want to confirm based on upload timestamps.
Friend's agent name: @yukachi
Date and time when I (@fumiso) first scanned + uploaded.
Date and time @ yukachi scanned + uploaded.
All dates and times are JST (UTC + 9)
@fumiso this is working as designed, but we're going to explore options to make Scout Controller status more clear. What happened was this sequence of events:
In order for Player 3 to claim Scout Controller, they will need to do 1 more Portal Scan of this Portal to overtake Player 2. Trying to automatically update Scout Controller status on every Portal every day is not an ideal solution; however, if we provide more information (like the date when the Portal Scan was submitted) then that may make scenarios like this slightly more clear.
Trying to automatically update Scout Controller status on every Portal every day is not an ideal solution
Y'all are clearly capable of implementing something along the lines of:
We all know this is as Portal Decay:
Scout Controller status is just another form of decay:
There is no need to update every portal every day. What am I missing? (Aside from knowledge of the resources available for implementing this, if it is actually correct.)
Thanks for the survey and answers
>> but we're going to explore options to make Scout Controller status more clear.
I think more people will scan if it improves in the future.
Thank you for implementing the portal history function. I think this will make it easier for many people to perform portal scans.
Capable, yes, is the cost of doing so worth it to Niantic, when so few are actually scannjng? not likely...... perhaps once a significant agents take up the subscription, new threads can be added to the automation...
Are there any changes in portal scan in newer versions?
In version 2.63.1 there is no work for me. The enable portal scanning option was not available in the setting.
Version 2.63.2. works, portal scan was enable in setting.
But the last versions 2.65.1 and 2.66. portal scan not working for me. The enable portal scanning option was not available in the setting.
Where is the problem? Newer version not supported the older version Google services for AR?
I have honor 20 pro, Google services for AR 1.12.
Have you tried reinstalling the Google services for AR, it might help.
I try it just now. Still nothing. It's stupid, because in the Pokemon Go it's work good with the last version. I think, that PoGo and Ingress have the same engine.
Still the enable portal scanning option was not available in the setting...but only in Ingress. 😡
Edit: in version 2.66.2. still not available in the setting.