[DO NOT MERGE] Adroid O API stable support for d15-3 #720
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.
This is actually meant to be in separate branch. This PR is to trigger build sanity check.
Fixes: https://bugzilla.xamarin.com/show_bug.cgi?id=30909
Fixes: https://bugzilla.xamarin.com/show_bug.cgi?id=51293
Fixes: https://bugzilla.xamarin.com/show_bug.cgi?id=55473
Bump to xamarin-android-api-compatibility/master/6fe9b17f.
Add
Documentation/HowToAddNewApiLevel.md
, to describe the processfor binding new API levels, including enumification.
Enumify API-26.
Update
build-tools/enumification-helpers
to support the latestdroiddoc
packages.html
format.API-26 changed
Activity.findViewById(int)
to be a generic method.Remove the
<typeParameters/>
element and "fix" the return type sothat we don't break API compatibility, as
generator
doesn'tcurrently do anything sane here. (Specifically, all generic
paramaters are currently bound as
Java.Lang.Object
, even if thetype parameter has a constraint which provides a more specific type!)
Fix binding of
Java.Nio.FileChannel
so it can be actually bound,related
SeekableByteChannel
support fixes.Remove
//implements[@name='AutoCloseable']
and//implements[@name='Destryable']
, as they add Javadefault
interface methods which can't be sanely supported at this time.
Update
api-merge
to changedefault
interface methods tonon-
default
methods when merging with an older API level whichcontained the non-
default
interface method. This preserves backwardcompatibility with existing assemblies and source code. Remove the
associated workarounds.
Bump xamarin-android-api-compatibility to check against the
latest-and-greatest API-26 binding.