Skip to content
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

android_device osx support #4679

Closed
codesuki opened this issue Feb 22, 2018 · 8 comments
Closed

android_device osx support #4679

codesuki opened this issue Feb 22, 2018 · 8 comments
Labels
P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team type: feature request

Comments

@codesuki
Copy link

After playing around with this rule it seems only linux is supported.
Is there a timeline for osx support?

@jin
Copy link
Member

jin commented Feb 22, 2018

There isn't a timeline for macOS support. The Linux constraint, AFAIK, is due to a dependency of android_device called unified launcher, which is hosted in android-testing-support-library. I have opened android/android-test#39 for this feature request.

@codesuki
Copy link
Author

Thanks for the info and opening an issue in the right place!
I didn't confirm yet but at least it seems to work with manually started emulators, too.
Looking forward to the android_instrumentation_test rule to run unit tests on the device.

@ahumesky ahumesky added the P2 We'll consider working on this in future. (Assignee optional) label Feb 27, 2018
@jin jin added team-Android Issues for Android team and removed category: rules > android labels Aug 11, 2018
@jin jin added P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) and removed P2 We'll consider working on this in future. (Assignee optional) labels Nov 28, 2018
@jin
Copy link
Member

jin commented Nov 28, 2018

Downgrading to P4 as there's a rewrite of the android_device rule happening, and the launcher will also be rewritten with multiplatform support as a goal.

@cgruber
Copy link
Contributor

cgruber commented Dec 19, 2018

Is there a github issue for the android rules rewrites that can be referenced here, for tracking? (and more generally we can subscribe to)

@jin
Copy link
Member

jin commented Dec 19, 2018

#5354 (cc @ahumesky)

@jgavris
Copy link
Contributor

jgavris commented Dec 19, 2018

cc @larryng

@github-actions
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 3 years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Feb 28, 2023
@github-actions
Copy link

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team type: feature request
Projects
None yet
Development

No branches or pull requests

5 participants