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

why would I need to use instrumentAndroidPackage = true #160

Closed
humazed opened this issue Apr 4, 2022 · 1 comment
Closed

why would I need to use instrumentAndroidPackage = true #160

humazed opened this issue Apr 4, 2022 · 1 comment
Labels
Question Support request issue type

Comments

@humazed
Copy link

humazed commented Apr 4, 2022

As the title says, why would I need to use instrumentAndroidPackage = true?

it's not clear from the docs what's the advantage of using this flag.

setting it to true causes #89 to happen.

so could you clarify if there is any use case for setting it to true, or it is expected to be always false?

@shanshin shanshin added the Question Support request issue type label Apr 4, 2022
@shanshin
Copy link
Collaborator

shanshin commented Apr 4, 2022

Hi,
in most cases, this flag should be false.
In very rare cases, it may be necessary to instrument classes from packages named android.* and com.android.*. For example, if the project has a class with the full name android.my.foo.Bar.

This flag is temporary and will be removed in upcoming releases when the instrumentation agent is improved.

@shanshin shanshin closed this as completed Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Support request issue type
Projects
None yet
Development

No branches or pull requests

2 participants