[Xamarin.Android.Tools.Bytecode] Fix for finding public setters with Kotlin unsigned types. #1156
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.
In #1151, we updated the logic that matches a Kotlin public property getter/setter to a generated Java getter/setter that follows this pattern:
However, this caused our unit tests in XA to fail that use Kotlin unsigned types:
This is because properties that use Kotlin unsigned types append a
-<type-hash>
suffix to their getter/setter names:Update our logic to handle this case.