binder: Mention Android 11 package visibility in docs. #9189
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Android 11 package visibility is a common reason for a binding to fail during development, so mention this in the docs.
markb74
changed the title
jdcormie
requested changes
May 20, 2022
There was a problem hiding this comment.
Thanks! This updates the "Detailed Discussion" section. Could you also add this case to the main "Status Code Mapping" table? (Here's the internal version: https://docs.google.com/document/d/1LOw_OXOpfJvWZpKRvJBf08zGTq-wHduE-RqaarCcyOw/edit#bookmark=id.y0ftetnau75m)
|
Do we still want to do this? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Android 11 package visibility is a common reason for a binding to fail during development, so mention this in the docs.