Repro
mkdir /tmp/valdi_repro && cd /tmp/valdi_repro
valdi bootstrap # UI Application
valdi install android
Bootstrap succeeds. valdi install android fails immediately:
ERROR: no such package '@@[unknown repo 'android_mvn' requested from @@]//':
No repository visible as '@android_mvn' from main repository
Cause:
The generated root BUILD.bazel (valdi_application(...)) expands to targets referencing @android_mvn, @rules_kotlin, @AndroidSDK. But the generated MODULE.bazel declares none of them — it ends at the version-pin block, with no android_mvn maven extension, no rules_kotlin, no hermetic SDK/NDK, no rules_android* bazel_deps. Bootstrap's own output is internally inconsistent: its BUILD.bazel can't build against its MODULE.bazel.
Environment:
@snap/valdi 1.1.5, framework beta-0.1.0, Bazel 7.2.1
Ubuntu (WSL2), x86_64, physical arm64 device
valdi doctor: 10 passed, 2 warnings (JAVA_HOME, editor ext)
Expected:
valdi bootstrap should generate a MODULE.bazel that builds for Android out of the box.
Note:
Hand-adding the missing wiring (mirroring Valdi's own MODULE.bazel: android_mvn, rules_kotlin, hermetic SDK/NDK, rules_android* deps) advances the error one repo at a time, then dead-ends in a bazel crash:
java.lang.ClassCastException: StarlarkInfoWithSchema cannot be cast to
com.google.devtools.build.lib.rules.android.AndroidSdkProvider
at AndroidSdkProvider.fromRuleContext(AndroidSdkProvider.java:188)
at AndroidToolsDefaultsJar.create(AndroidToolsDefaultsJar.java:48)
— a native-vs-Starlark Android SDK provider mismatch. Also: the registry's rules_kotlin/1.9.0/source.json applies only rules_kotlin.patch; the rules_kotlin_android_sdk.patch in the same dir isn't listed and never applies.
Is there a consumer-side Android wiring step I'm missing for Linux/beta-0.1.0? Full logs + edited MODULE.bazel on request.
Repro
mkdir /tmp/valdi_repro && cd /tmp/valdi_repro
valdi bootstrap # UI Application
valdi install android
Bootstrap succeeds. valdi install android fails immediately:
ERROR: no such package '@@[unknown repo 'android_mvn' requested from @@]//':
No repository visible as '@android_mvn' from main repository
Cause:
The generated root BUILD.bazel (valdi_application(...)) expands to targets referencing @android_mvn, @rules_kotlin, @AndroidSDK. But the generated MODULE.bazel declares none of them — it ends at the version-pin block, with no android_mvn maven extension, no rules_kotlin, no hermetic SDK/NDK, no rules_android* bazel_deps. Bootstrap's own output is internally inconsistent: its BUILD.bazel can't build against its MODULE.bazel.
Environment:
@snap/valdi 1.1.5, framework beta-0.1.0, Bazel 7.2.1
Ubuntu (WSL2), x86_64, physical arm64 device
valdi doctor: 10 passed, 2 warnings (JAVA_HOME, editor ext)
Expected:
valdi bootstrap should generate a MODULE.bazel that builds for Android out of the box.
Note:
Hand-adding the missing wiring (mirroring Valdi's own MODULE.bazel: android_mvn, rules_kotlin, hermetic SDK/NDK, rules_android* deps) advances the error one repo at a time, then dead-ends in a bazel crash:
java.lang.ClassCastException: StarlarkInfoWithSchema cannot be cast to
com.google.devtools.build.lib.rules.android.AndroidSdkProvider
at AndroidSdkProvider.fromRuleContext(AndroidSdkProvider.java:188)
at AndroidToolsDefaultsJar.create(AndroidToolsDefaultsJar.java:48)
— a native-vs-Starlark Android SDK provider mismatch. Also: the registry's rules_kotlin/1.9.0/source.json applies only rules_kotlin.patch; the rules_kotlin_android_sdk.patch in the same dir isn't listed and never applies.
Is there a consumer-side Android wiring step I'm missing for Linux/beta-0.1.0? Full logs + edited MODULE.bazel on request.