Location

.github/workflows/build-android-demos.yml

Context

Demo documentation can reference files from other demos, but the Android build workflow copies files located inside the demo being built. This mismatch can produce a successful build containing the default template instead of the documented sample.

For example, MASTG-DEMO-0088 reuses the code sample from MASTG-DEMO-0087:

  {{ ../MASTG-DEMO-0087/MastgTest.kt }}

However, its directory contains neither MastgTest.kt nor AndroidManifest.xml. The workflow does not resolve the shared files, retains the base app files, and publishes the resulting APK as MASTG-DEMO-0088.apk.

The CI job logs confirm this:

  No MastgTest.kt found for demos/android/MASVS-RESILIENCE/MASTG-DEMO-0088
  No AndroidManifest.xml found for demos/android/MASVS-RESILIENCE/MASTG-DEMO-0088
  > Task :app:compileDebugKotlin UP-TO-DATE
  BUILD SUCCESSFUL

Steps to Reproduce

1. Download MASTG-DEMO-0088.apk from the linked workflow run.
2. Install and launch the app.
3. Run the sample using the Start button.

The app displays the default template results instead of running the root detection checks documented in MASTG-DEMO-0088.

Other Demos with the Same Build-Input Gap

Repository inspection at dd8bc103ed054daa37f37e861ed9f36d63bbea40 identified 26 additional demos whose documented sample references build inputs outside the demo directory. Those inputs are absent locally, and the current APK/IPA workflows do not copy them from the referenced location.

This concerns APK/IPA builds, not Markdown rendering. These additional artifacts have not been individually downloaded or executed. The findings below are based on source-file and workflow inspection; the CI-log evidence above concerns MASTG-DEMO-0088.

The table lists explicitly referenced build inputs missing from each demo directory. It is not a complete inventory of every file needed to build each sample.