Sometimes, the currently selected party is detected incorrectly

[Azzurous]

Preparation

• [X] No one has asked for this feature before in other issues (even the closed ones)

Describe the feature

I formatted this as a feature request because as far as I can tell this is an issue that has nothing to do with FGA since it occurs I repeat the scripts actions manually. The problem is with the party screen where the 'start quest' button gets locked this happens when Party X is already selected and I or FGA selects Party X again using the top bar. The workaround I want to suggest for this issue is to add a setting which will make FGA always select a different first and then select the desired party. I don't know how hard this stuff is on the back-end but the simplest example I could think of is select Party X+1 then Party X but then idk what to do with Party 10.

[reconman]

But that's what should currently happen. How did you produce that bug?

[Azzurous]

https://mega.nz/folder/PrpRGY6T#pFz7RMOM46AXjRTo_q_W_Q I bad at explaining so here are some, images to help explain what I meant in the first post, videos to show the problem and this note about another issue occurring:

I encountered another problem when looking into the first issue in more detail. The party selection just doesn't do anything unless the desired party is the one that loads automatically after the support selection. I didn't have this problem before I updated the app today(Build:1567) I don't know the build number that I was using before but I know it was installed on the 21st of Nov

Issue1.mp4 - The issue I talked about before, preformed by the script at first. Then I took control manually to unblock the 'start quest' button while the script was running. Issue1Manual.mp4 - This is a completely manual reproduction of the issue and my solution of it. Issue2.mp4 - party selection not working

[reconman]

The weird thing is, on my device it works flawlessly. I also measured a screenshot from your video and the pixel values align perfectly.

What the app does:

1. If the wanted party is already selected, click Start Quest
2. If the wanted party is not selected, select the party and click Start Quest
3. If the currently selected party cannot be detected, switch to another party and then back to the wanted party.

On my device, 1. is triggered, even when choosing party 10. I see 2. in your video, but can't explain why it's happening.