"interaction Window" doesn't appear at the right place

[xDARKxDEVILx]

Type

Error at runtime

Bug description

This issue is only related to the tablet version, which only happened like a week ago by its own (without any update to the app or patches) and it is that this window appear at the wrong place, some examples are provided below but it happens with all " : " buttons

Steps to reproduce

Click on any " : " button and you will find that the window apears at top left regardless of where it should appear

Relevant log output

No log

Screenshots or videos

Solution

No response

Additional context

This bug is extremely annoying so please try to fix it asap, it only happens in ReVanced btw

Acknowledgements

• I have searched the existing issues and this is a new and no duplicate or related to another open issue.
• I have written a short but informative title.
• I filled out all of the requested information in this issue properly.

[Masamune3210]

I really wish people would stop putting asap in their reports. The devs owe you nothing and do it as a side-project usually. Insisting on a time schedule isn't going to end well

[xDARKxDEVILx]

I really wish people would stop putting asap in their reports. The devs owe you nothing and do it as a side-project usually. Insisting on a time schedule isn't going to end well

Well, this bug is really annoying so i just asked them to prioritize it , and i think i asked kindly i am really appreciative of their work and i don't think i requested it like if "they owe me something" and at the end it won't change that they can reglect or delay the fix

[oSumAtrIX]

Check the stock unpatched app (same version).

[xDARKxDEVILx]

Check the stock unpatched app (same version).

Doesn't happen to stock app for any version only revanced

[xDARKxDEVILx]

I checked version 18.05.40 and 18.08.37 and it is fine for both of them

[oSumAtrIX]

Exclude patches from the patching process until the error is gone, and report back which one causes it.

[xDARKxDEVILx]

Exclude patches from the patching process until the error is gone, and report back which one causes it.

Any suggestions for what patches may cause it? as trying excluding every single patch will take me three weeks lol

[oSumAtrIX]

You can do a binary search that would find the problematic patch in log(patchesCount) time in the fastest way possible.

[xDARKxDEVILx]

You can do a binary search that would find the problematic patch in log(patchesCount) time in the fastest way possible.

I don't know why you thought i would understand that, can you please explain what you mean better? If it is difficult then don't explain 🙂

[oSumAtrIX]

I don't know why you thought I would understand that

CS students should be aware of binary search:

Say you have a list of patches. Exclude half of them; if the issue persists, the problematic patch is in the other half. Proceed to do the same to that half.

[xDARKxDEVILx]

I don't know why you thought I would understand that

CS students should be aware of binary search:

Say you have a list of patches. Exclude half of them; if the issue persists, the problematic patch is in the other half. Proceed to do the same to that half.

Nope they haven't taught as that yet lol, but i was actually doing that now without understanding it , i narrowed the patches to 8 and will continue testing

[xDARKxDEVILx]

It is one of these since the apk patched with them still have the issue

[oSumAtrIX]

Please reupload the image.

[xDARKxDEVILx]

[oSumAtrIX]

Narrow down even more.

[xDARKxDEVILx]

Narrow down even more.

Still exists with these 4

[xDARKxDEVILx]

It is probably the spoof one then, i will try again only it and microG

[xDARKxDEVILx]

Somehow it still exists with only microg patch

[oSumAtrIX]

In that case it is a stock issue.

[xDARKxDEVILx]

In that case it is a stock issue.

But i tested stock and it is fine🥲

[xDARKxDEVILx]

Will test it again

[xDARKxDEVILx]

Yeah stock is perfectly fine, i am not an idiot nor am i lying, the stock version has no issue and the patched one with only MicroG patch has the issue

[xDARKxDEVILx]

I said before that this issue happened without any change in anything, slept with ReVanced fine and woke up without updating anything and the issue apeared , but it can't be from YouTube side as stock is perfectly fine, i have no idea what it could be then

[xDARKxDEVILx]

Sorry for too many comments but i can confirm that stock is fine , can you test it yourself or ask someone with any tablet and see if you can figure out the issue? Appreciate your help

[oSumAtrIX]

Did you install the same apk you are patching without patching it and did you check if it happens there?

[xDARKxDEVILx]

Did you install the same apk you are patching without patching it and did you check if it happens there?

You mean patch without even MicroG support patch or what exactly?

[xDARKxDEVILx]

The apps i have are Stock V 18.08.37 downloaded from apkmirror and the patched V 18.08.37 one with only MicroG support patch, do you want anything different?

[xDARKxDEVILx]

The stock actually rarly have the same issue i have no idea how this happens i am starting to lose my mind , five times i open it and it is fine and one time it has the issue

[xDARKxDEVILx]

Now it always has the issue,so maybe stock doesn't have it for the first few times you open it and then it starts to have the issue , but the patched one always has it ( this may be wrong but that is what i understood)

[xDARKxDEVILx]

I tried updating to the latest google play version and the issue exists, so does that mean it is YouTube thing? At least reply to this last comment

[oSumAtrIX]

If it happens in the unpatched app, as originally assumed, yes.

[xDARKxDEVILx]

If it happens in the unpatched app, as originally assumed, yes.

I am really sorry for wasting your time and it is a YouTube issue , but i really didn't know since it only happened after like the fifth time i open it , i feel like a dummy now lol

[oSumAtrIX]

All good, happens.

[xDARKxDEVILx]

All good, happens.

Sorry to bother you, but this issue has not been solved to this day, i have tried sending YouTube this issue but i got no reply and i couldn't provide screenshots anyway, do you know a good way to ask YouTube to fix their damn app?

[oSumAtrIX]

No, it is an upstream issue and unrelated to ReVanced.

[xDARKxDEVILx]

No, it is an upstream issue and unrelated to ReVanced.

I know i was asking you if you know a way to contact google to fix it , not you guys

Was the "no" for you don't know how to ask yt?

[oSumAtrIX]

[xDARKxDEVILx]

This bug has finally been fixed after more than 3 months F U YouTube,
i mean Thank you 🙂