also seen in StackOverflow: Util API 32 the method could return
null
but since API 33 it's marked as
@NonNull
. There are possible workarounds for this:
• A Java wrapper which doesn't enforces the nullability to keep it
@Nullable
• Remove
override
and suppress the warning
None of them seems ideal, what do you use in your projects? I remember an Android blog post about the topic of migration but when previous versions could pass