Always throws ADB error

[SomeSpaceNerd]

Every time I attempt to connect to my Quest 3 headset running V68 the "Another app is attempting to access your device" error appears, even after running adb kill-server and taskkill /IM adb.exe /F. This may be an issue with the website because even on a different computer which has never even seen sidequest or another ADB app (but has android studio installed), the exact same error occurs and cannot be fixed.

[Lauriethefish]

Can you please share a screenshot of the browser console after the issue occurs? (the ADB library logs some info there)
Can you confirm also which browser you are using?

[SomeSpaceNerd]

So after attempting to get a log and screenshot, the site just does not do anything after pressing connect. There is no console output, it just does not do anything, and if I try to connect again, a interface error occurs with the output Failed to connect: InvalidStateError: Failed to execute 'claimInterface' on 'USBDevice': An operation that changes interface state is in progress.

[Lauriethefish]

This suggests some kind of underlying issue with the ADB library, perhaps causing a deadlock during the handshake that establishes the connection.

I'll add more logging to verify exactly which call is causing MBF to get stuck.

[kuuriii]

Is there anyway to fix this issue currently? Just hoping there's been progress on this over the last 7 months. Sorry to bother you lol.

[Lauriethefish]

There has been some effort from other members of the community, specifically #53, allowing use of a bridge to use the native ADB implementation, which avoids WebADB bugs that currently plague MBF.

Unfortunately, I'm in full time education at the moment, so I haven't got much time to make significant progress!

[Lauriethefish]

@kuuriii Are you still experiencing this issue? Working on it now, finally found myself some free time.

[ryoto9846-svg]

@kuuriii Are you still experiencing this issue? Working on it now, finally found myself some free time.
Hey ive been modding with this website for a while but all of a sudden i have got the same error have you found a fix yet or is it non fixable thank you

[kuuriii]

@kuuriii Are you still experiencing this issue? Working on it now, finally found myself some free time.

@Lauriethefish sorry I hardly ever look at my GitHub notifications, yeah I still get this issue. however, I have noticed that it is only an issue on PC. I've been using my phone and it's never been an issue there.