-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device always invalid on Ubuntu #42
Comments
I take it back, this might not quite be the issue. Let me investigate some more. |
So I am not understanding how this fixes it... it currently splits on |
ok, now, i see your new message. |
Yeah I'm apparently very wrong lol. It is having an error at the parsing stage (most likely when it splits) for some reason, but I'm not sure why yet (checking the regex shows that it does match the |
can you put the error that you are seeing in this issue |
If it was splitting correctly, then the |
There's an outside possibility that something different is being returned from |
can you post the value that is coming in in |
Lemme see. I'm running it through a test adapter so I'll have to create a new project to call it directly. |
It doesn't look like I can debug that code from the package. I can pull down the code locally and try that. I don't know if it will build though since it isn't .NET Core. |
Yeah I can't build it outside of a .NET Core project. So there's no way for me to tell really. Is there any way you could push up a NuGet with some logging? |
Hello. Did you get a chance to look at this? I don't have any way of figuring out what the input was. |
Hey. Just following up. Any chance to look into this? |
no permissions This is due to adb not being started with elevated permissions. I don't know if ManagedAdb automatiaclly runs the But if not, starting adb with sudo privileges at boot-time would resolve this issue. If so, the library should at least throw a warning that it tried to start adb in elevated mode but a password was requested.
You can make an entry in the Other approach is to add yourself to plugdev group and put adb executable under non-root owner.
|
Weird. It works fine when I run adb myself. I don't think adb is being run under my account. I'll sort through the code and figure out what it's running under. |
if you run adb yourself with the devices you have at work attached, i expect some will return 'no permission' looks like there are 5 references to either what's curious is Assuming it does issue the kill server command, the best option is probably a simple python script running in the background which constantly checks for devices with 'no permissions' and restarts the server with sudo priviledges if this ever happens. You can put the python script in your startup commands on Ubuntu. |
Initially I thought it might be best to fix this issue in the library itself under a new fork, but you're right, it's probably best to just put a nice little script on the Linux box. |
I'm getting this error again now on Windows. Even though the list comes up fine in cmd |
that's because no one has pushed a commit to this repo in 3 years. Anyone who would use it for Android 9 is a fool make your own wrapper and you will be thankful |
Lmao sup Shane. Didn't know it was that out of date. Seems too buggy to keep using |
it's also possible no commits have been pushed because it is already perfect. you should ask the maker directly what's up @camalot |
Here is the problem line.
Splitting on
Environment.NewLine
, or including"\r"
would fix the issue. Ubuntu (and Linux in general) uses"\r"
for newlines. Otherwise t gets one long string and fails to match the RegEx.The text was updated successfully, but these errors were encountered: