kuri/api/android/kuri.api is a committed binary-compatibility-validator snapshot, but nothing in the current Gradle setup regenerates or validates it: apiDump/apiCheck only run the jvm and klib (merged native) variants — there's no android*Api* task. It looks like it stopped being wired up around PR #54 and has been silently drifting from the real commonMain public API ever since (most recently, it's missing the ValidationError.INVALID_CREDENTIALS entry added in a recent fix).
Since nothing enforces it, this file currently just sits there as a misleading artifact for anyone who reads it expecting it to reflect the Android target's actual API surface.
Two options, either is fine:
- Delete it, since nothing maintains it and a stale snapshot is worse than no snapshot.
- Wire the Android target into
apiDump/apiCheck so it's regenerated and validated like jvm/klib are.
kuri/api/android/kuri.apiis a committed binary-compatibility-validator snapshot, but nothing in the current Gradle setup regenerates or validates it:apiDump/apiCheckonly run thejvmandklib(merged native) variants — there's noandroid*Api*task. It looks like it stopped being wired up around PR #54 and has been silently drifting from the realcommonMainpublic API ever since (most recently, it's missing theValidationError.INVALID_CREDENTIALSentry added in a recent fix).Since nothing enforces it, this file currently just sits there as a misleading artifact for anyone who reads it expecting it to reflect the Android target's actual API surface.
Two options, either is fine:
apiDump/apiCheckso it's regenerated and validated likejvm/klibare.