Drone jumps are broken

vikendvikend ✭✭✭
edited August 3 in Report a Bug

Drone doesn't seem to jump at the first try.

This behaviour occurs like 80% of my jump attempts. It has been like this for at least 3 weeks now, definitely before Munich, maybe since mid July patch.


Steps to reproduce:

Imagine jumping from portal A to portal B

1) Be on main screen

2) Open drone view

3) Jump with drone to portal B, cooldown goes to 60:00

4) Initiate hack on portal B

4a) Get "Portal not in range" error, even though I am allowed to hack - hack button is on

5) Return to the main screen

6) Go to drone view again

6a) Drone is still at portal A, cooldown at 00:00 (Ready to move)

7) Jump with drone to portal B, cooldown goes to 60:00

8) Initiate hack on portal B

8a) Hack successful



Clearing cache and/or reinstalling Ingress didn't help.

Example:


Ingress v2.96.2, Android 11

Motorola Moto G 5G Plus

Post edited by vikend on
Tagged:
2
2 votes

New Report · Last Updated

Comments

  • QaGuyQaGuy ✭✭
    edited August 4

    I experience it too. I think it's a dirty writing in the DB and it remembers 2 locations of my drone.

    It was in July. I was in the location with spotty WiFi and cellular. I moved my drone and tried to hack a portal. It took too long time to bring command line and I restarted the app and moved to the place with better WiFi. My drone was on the same place and I moved it again and hacked the portal. I was busy and next time I moved my drone after a few hours. I experienced this issue. I found a workaround to move the main drone and do not get the ghost drone.

    1. Move drone.

    2. Close/restart the app

    3. Hack the portal where is you main drone.


    If you try to hack the drone right after it was moved then it will compare the main drone location with the ghost drone location and it will show you the message with error (something related to location). It means there are 2 rows in DB with my drone because it remembers both locations. It's my guess.

    Post edited by QaGuy on
  • QaGuyQaGuy ✭✭

    Ingress 2.96.2.

    Google Pixel 5a 5g

    Android 11

  • vikendvikend ✭✭✭

    Will try this when my cooldown hits 0.


    But it's still a bug innit?

  • KarM3LKarM3L ✭✭✭✭

    This was happening on and off for a few users while back seemed to require support intervention

  • elfobcnelfobcn ✭✭✭
    edited August 4

    I now have similar issue with two dron instances, with two remembered differents locations on two different cities.

    Sometimes I can move the main drone, and sometimes the ghost one on another city, its some random wich one of them appears when the countdowm arrived to 0 for move, and sometimes appears the location error that you commented.


    Ingress v2.96.2, Android 12

    Google Pixel 4 XL

  • Same issue for me. It's been at least 3 months now, maybe longer. I put in a support ticket and they responded with it's been fixed. But nothing. I have two instances with the drone and I have to move and hack twice to get it to work once. I haven't found a way to get it to work right yet.

  • EvilSuperHerosEvilSuperHeros ✭✭✭✭✭

    I've seen this a few times. But most of the time the first time I open drone to move it, portals don't even load and I have to close and reopen the drone button a few times to get portals to even load.

  • QaGuyQaGuy ✭✭

    These 2 drones are both mine

  • Jo0LzJo0Lz ✭✭✭✭✭

    I've had issues with the drone for some time now. I try to move it, nothing happens, then I try to move it again, 'Scanner communication error'. Try to move to the portal again: 'Drone already at target portal'.

    I can then hack the portal, and whilst I'm glyphing another 'Scanner communication error' will show.

    Happens 1 in every 5 drone moves approximately.

Sign In or Register to comment.