You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 27, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 27, 2026. It is now read-only.
While updating AndroidX to XA 17.2, we found that the previous Kotlin issues around unsigned types have been fixed. However, there are some new issues that have been exposed:
#### Type Changed: Kotlin.UIntArray
Removed methods:
public bool Contains (uint element);
public static bool Contains (int[] arg0, int element);
Added methods:
public bool Contains (int element);
public static bool Contains (int[] arg0, uint element);
This regression should be investigated. Perhaps it is related to method overloads?
The mangled part seems to be a hash of the Kotlin parameter types of the method. Because they "match", Kotlin does not write its metadata for each method, it only writes one copy which is correct-ish for both methods:
(Note that the JvmSignature is ([II)Z even though there is only one ValueParameter.
Thus, when more than one Java method matches the JvmName and the JvmName is "mangled" (contains a hyphen), we should apply the parameter fixups to all matching methods, even though the JvmSignature doesn't match.
Context: #946
Context: dotnet/android-libraries#547
While updating AndroidX to XA 17.2, we found that the previous Kotlin issues around unsigned types have been fixed. However, there are some new issues that have been exposed:
This regression should be investigated. Perhaps it is related to method overloads?