Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 2604 [details]
Screenshot of error.
I noticed this when upgrading to 4.2.5 - I didn't see this issue when using the previous version.
I have busybox installed onto my Android System (which is using used in an Embedded Product - not as a phone) and if the busybox `ps` was in the PATH before the Android /system/bin/ps I could get an error while deploying. I worked out that it was caused by the 'incorrect' ps being called.
I was hoping you could change the call to `ps` to include the path /system/bin/ps so people with a modified Android system won't have problems if they choose to modify their Android system?
I have changed the PATH back to the default so Mono4Android finds the Android ps first instead of the busybox one.
FWIW, we already added parsing for that particular busybox output format (there are several!) but it didn't make it into 4.2.5.
It would make sense to use the system ps, thought it might break in ROMs where packagers have removed "unnecessary" files after installing busybox. So we'd need some kind of check and fallback.
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.