contrib/android/Readme.md: mention build cache
What changed, and why it matters
This commit only updates a documentation file (Readme.md) for Android build instructions. It adds advice about clearing build caches when developers don't see their changes take effect or encounter confusing build failures. There is no code change and no security relevance.
No security action needed. This is a documentation-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies contrib/android/Readme.md, adding two lines of guidance about clearing .buildozer_qml/, packages/, and contrib/android/.cache/ directories, plus a note that stale build caches can cause confusing build failures. No executable code, build scripts, dependencies, or cryptographic logic is changed.
Changed components
contrib/android/Readme.mdInspect captured patch +5 / −0
diff --git a/contrib/android/Readme.md b/contrib/android/Readme.md
index 6e348ef..04f92d0 100644
--- a/contrib/android/Readme.md
+++ b/contrib/android/Readme.md
@@ -62,6 +62,11 @@ repository.
### I changed something but I don't see any differences on the phone. What did I do wrong?
You probably need to clear the cache: `rm -rf .buildozer/android/platform/build-*/{build,dists}`
+Or more extreme, to nuke all build-related dirs: `rm -rf .buildozer_qml/ packages/ contrib/android/.cache/`
+
+Having a several months old build cache might also cause confusing build failures,
+in such a case, worth a try clearing it.
+
### How do I deploy on connected phone for quick testing?
Assuming `adb` is installed:
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.