For Android, one might expect to use some deprecated methods on older API levels, and use some newly introduced methods on newer API levels. These newly introduced methods will not be found at runtime on older Android versions.
Maybe {Type}API can store IDs in Options, so that None values can be mapped to MethodNotFound and FieldNotFound errors. There can be another generated function of checking the availability of all fields and methods, or simply an option in bind_java_type for this issue.
For Android, one might expect to use some deprecated methods on older API levels, and use some newly introduced methods on newer API levels. These newly introduced methods will not be found at runtime on older Android versions.
Maybe
{Type}APIcan store IDs inOptions, so thatNonevalues can be mapped toMethodNotFoundandFieldNotFounderrors. There can be another generated function of checking the availability of all fields and methods, or simply an option inbind_java_typefor this issue.