FGA sometimes chooses the wrong support due to unintended support refresh

[Gray-Aeon]

Preparation

• I tested the latest release
• I looked at other issues (even the closed ones)
• I read the Troubleshooting Guide

FGO server

NA

FGA build number

3014

Describe the bug

FGA randomly decides to refresh the support immedeatly after entering the support screen, without doing any swipes or checking for the target Servant first. This sometimes results in the Servant below the refresh confirmation being chosen as a support when FGA tries to refresh too fast.

My support is getting chosen by the friends name and the CE btw, in case this is related. I remember there being issues in the past with friend names.
Until yesterday I was farming with a standart Servant+Teatime script, this was running for a few days straight without any problems. (And it's still working fine now)
I was also running the Friend+CE script for a few years occasionally (The last time being a few months ago), today is the first time in years this didn't work.

I set both swipes and refreshes to 0 at first, which resulted in FGA just stopping, even with the target in full view.
I already tried turning down the similarity (10% less), same problem.
I also restarted FGA and reset the settings to default, now it's back to the random refresh at the beginning.

Video

Video: https://imgur.com/a/PUBWybO (Skip to final 10s, when it enters the support screen again)
In that video, FGA was supposed to swipe down and choose Jalter. Instead it refreshes asap. (Notice how the confirmation tap is right on the area of Douman)
In another run, which I wasn't recording of course, I happened to catch it choosing the wrong support while trying to do the refresh.
https://i.imgur.com/ZZPuD0A.png
In that image you can see that it has indeed chosen Douman.
In previous attempts I had the support list sorted differently, with Skadi being in the middle of the screen and her getting chosen as the wrong support instead. (In that case, Jalter was at the top and completely ignored as well)
So something is triggering a support refresh, even when it's not possible to do a refresh yet, which can result in wrong supports due to FGA trying to tap a non-existing "yes" button.

Device model

Bluestacks 5.22.100.10024

Android version

11

Screen size

960x540

RAM

4GB