I have recently synced the android-t-beta-3 branch.
However, it appears to be missing APIs which were introduced long before even Beta2.
One example is LineBreakConfig, which was introduced in DP1
Another one is Context.revokeSelfPermissionOnKill, which is not available at
I would like to get a better understanding of the semantics of Beta branches.
My expectation, based on the sentence "It is not a full platform update and only for reference." would be that either:
- a Beta3 tag does not exist for a repo (because, as stated in the posts in this thread, "It is not a full platform update")
or, if a tag does exist,
- it contains the Beta3 code.
I am struggling to appreciate the intention behind tagging, a Beta3 branch (android-t-beta-3) which does not
actually contain Beta3 code for that specific repo.
Could anyone clarify intention and semantics of Beta branches?
How can they be used "for reference" if they do not actually contain code from Beta releases?
CONFIDENTIALITY NOTICE: The information contained in this message may be privileged and/or confidential. It is the property of CrowdStrike. If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please notify the sender immediately, and delete it and all attachments from your computer and network.