Long 20-40 seconds stuck when deploying resonators
HopeaKotka
✭✭✭✭
in Report a Bug
There is often 20-40 seconds stuck when deploying resonator.
It feels like server is somehow not responding to deploys. Ingress UI is responsible but you cannot do any server operations.
This is not a Phone or Operator data connection issue: Can switch to other App and use data connection at the same time.
Samsung S8 Android 9 2.65.1
37
Comments
Yeah i got this today, there is suddenly a lag and u cant deploy not sure if server sync glitch or something maybe ?
sometimes it feels i deploy too fast and must wait ahaah xd
I get that issue as well, it also often happens when firing XMPs. It will charge up, then the do animation will circle the player image, but sometimes the attack will never actually happen. Force closing and reopening the app has sometimes been the only way I can complete an attack.
Pixel 4a (5g)
Android version 11
ingress 2.65.1-5b23df20
It feels like this is now happening more frequently since releases 2.72.1 and 2.73.1.
Very often long stuck occurs after deploying first 2-3 resonators. You can even use Powercubes during stuck.
still a problem long lag on deploy resonators...
Yes, having this problem very often when playing.
Also when recharging a portal.
I have this very frequently as well, even more so in the past month. Usually hacking a portal makes it go back to work.
Apple 7 plus
Happens here too often to be just a network glitch. After delay, a short error message "Invalid resonator" is displayed sometimes - not in all cases but quite often. The game itself is not stuck, only deployment is - other actions works just fine (for example, it's possible to put a mod into or hack any accessible portal).
Here is a log when resonator deploy stuck happened.
Not sure if the log contains any useful data or hints why stuck happens.
There are errors like:
Duplicate rows replaced with ":"
Was able to repeat this today with latest version 2.76.1 and after all server updates and maintenance.
This time it was possible to deploy two mods to portal while resonator deploy was stuck:
Suffering the same, since months ago.
Playing ingress is a painfull experience sometimes...
I'm 'glad' it's not just me. Happens constantly while i play. It started happening around 2 or 3 updates ago. Deploying resonators, recharging, glyphing/hacking, etc. It all can get stuck but you can do certain other actions while the freeze is happening. for example if deploying resonators becomes stuck, you can still use power cubes and recharge. If recharge get's stuck you can still hack, etc.. the freeze can last between 3 seconds or 30 seconds, so if you wait it will get unstuck after a while but it's a real pain to enjoy the game this way.
Bitter irony this is the first time i log in and comment on this website and im getting error messages in my browser that the webpage is stuck.
still getting this more or less daily extreme lag when deploy resonators..
Three more stucks today with latest version 2.77.1:
All cases have web error in log:
Web request failed with HTTP error.
HTTP/1.1 500 Internal Server Error
1. Recharge portal:
2. Deploy Resonator:
3. 3rd case, do not remember anymore what I did (maybe it was deploy resonators):
Duplicate lines of "Parent of RectTransform..." removed.
Long Token string id replaced with "TOKEN_STRING".
@NianticBrian
Is nobody going to aknowledge these problems we been having for months now? Its becoming really frustrating to deal with.
Thia posted update on this today,
https://community.ingress.com/en/discussion/16756/game-latency#latest
I have the same problem and not only with deploying - it is sometimes extreme with "recharging".
While Recharging for 30 minutes it can happen 5 times and more that recharging is stuck for 10s to 1minute.
That is really annoying if You try to defend some portals and You can only watch how they die. Frustrating. Really.
So please, Niantic - solving this issue must become absolute priority.
Thanks.
Same, I usually only notice when recharging.
It's also usually faster for me to restart the Scanner app than to wait for the interface to become responsive again. Not so much fun on these virtual First Saturdays, when I'm "competing" against other local-ish agents for the most XM spent.
This looks promising, haven't noticed any stuck so far with version 2.88.1.
Earlier the stuck was guaranteed to happen every 30 minutes, so the frequency is definitely reduced.
----------------------------------------
Ingress 2.88.1 Release Notes - Bug Fixes:
• Fixed: We have a speculative fix for the intermittent lag that occurs when recharging Portals. We're still investigating; however, this speculative fix may help reduce the frequency of this occurring.
----------------------------------------
Stuck is still there, seeing it lately more often.
There is now lots of "SideChannel" errors in logs files.
My quess is that sideChannel gets somehow temporary stuck and no actions using it works for during 30-50 secs.
Some operations are still working even the deploying is stuck.
So successful operations are using Main Channel?
Assuming that there is one Main channel and one Side channel for commands.
Maybe NIA could tell what operations are using sideChannel (that gets stuck) and what operations are using Main channel?
So other players can also verify if only sideChannel operations gets stuck.
------
Here are 4 different logs, log 4 being the latest and log 1 the oldest.
Duplicate "Parent of RectTransform" trace replaced with ":"
Event not found id looks like unique id, replaced it with X chars.
---------------
Log taken every time after stuck happened. Seems that there is not much new traces after Log 3:
Log 4 taken at: Wednesday, July 19, 2023 4:26 PM
Log 3 taken at: Wednesday, July 19, 2023 4:14 PM
Log 2 taken at: Wednesday, July 19, 2023 3:24 PM
Log 1 taken at: Monday, July 17, 2023 5:47 PM
---------------
Here is my analysis of the resonator lag problem:
It is different from the general lag problem, often occurs together with it but sometime also occurs on its own.
Deploying resonators is subject to the ubiquitous lag problem. When this hits the resonator gets stuck together with all other operations that need a server response (so e.g. hacking the portal get stuck, mod deployment get stuck). After some time the lag gets resolved but the resonator is still stuck. At this time it is possible to deploy mods or hack the portal, but it is still not possible to deploy resonators. After some additional time there is an error message like "invalid resonator" and only then it is possible to continue deploying resonators. The error message is displayed regardless of whether the resonator has successfully been deployed in the meantime or deployment has actually failed.
Sometimes the resonator lag problem just occurs on its own. Then it is immediately possible to do other actions like hacking the portal, deploying mods, etc., but the agent still has to wait for the resonator deployment to finish.
Based on my experience, I suspect the following as the cause of the problem: In the response handler of the resonator deploy action there is an unhandled error and it is exited unexpectedly. The deploy action still waits for a server response which will never come as it already has been received. After some fixed time the deploy action will then run into a timeout, cancelling the response handler and issuing the error message. This would also explain why there is an error message even if the resonator is successfully deployed: The success message from the server is just not handled correctly by the client.
In the previous post I can find further confirmation of my theory: There is a function called from a response handler (Promise<T>.Then). And it fails with an error: System.NullReferenceException, a generic programming error.
If my suspicion is correct the solution would be first to fix the programming error and second to guard the response handler so that actions do not get stuck when they fail unexpectedly. (And of course finally fix the infamous ubiquitous lag problem, but this is a different bug)