oppia/oppia-android

Describe the bug When the app is opened after a long period of inactivity, there is a blocking screen prompting the user to update the app. However, there is not a direct link provided to go to the Google App Store to update the app. Steps To Reproduce Ensure Oppia is installed Set the device's date to 1 year from today Open the app Expected Behavior There should be a direct link provided to update on Google Play. Screenshots/Videos There is no option provided to go directly to Google Play to get the update, as described in test documentation (see details below). What device/emulator are you using? Samsung Galaxy S21 Which Android version is your device/emulator running? Android 15 Which version of the Oppia Android app are you using? 0.19-rc03-alpha-9faec1d609 Additional Context In August we had identified #6393; in addressing that we have added the screen shown in the screenshot, just missing a direct link to Google Play.

Describe the bug Related to #6430 and #6431: After a list, there is no spacing between the last list item and the next item, whether a non-list item or an outer list item. Some sentences are have the appearance of missing spacing before/after, making them run into each other after a period(.) and look like links. For this specific bug #6432 fixed it in worked examples and it appears that some of the list tags were previously getting stripped. The same fix applied to worked examples should be applied to the broader lists. Steps To Reproduce Open a study guide with lists. See that subsequent lists have no spacing in between Also notice that some text have no spacing in between, showing up as links. Expected Behavior Lists should display corrcetly, with proper spacing, e.g.: Screenshots/Videos What device/emulator are you using? No response Which Android version is your device/emulator running? Android 10 Which version of the Oppia Android app are you using? 0.18-dev Additional Contex

Describe the bug The Code Coverage CI workflow (Evaluate Code Coverage Reports job) fails during the Generate Markdown Coverage Report step because scripts/src/java/org/oppia/android/scripts/lint/AndroidLintRunner.kt has a test line coverage of 67.32%, which is below the default required threshold of 70%. Error Log COVERAGE FAILURE REPORT: Covered File: scripts/src/java/org/oppia/android/scripts/lint/AndroidLintRunner.kt Coverage percentage: 67.32% covered Line coverage: 239 / 355 lines covered Minimum Required: 70% Exception in thread "main" java.lang.IllegalStateException: Coverage Analysis FAILED at org.oppia.android.scripts.coverage.reporter.CoverageReporterKt.main(CoverageReporter.kt:79) Context & Root Cause The default minimum test coverage threshold in CoverageReporter.kt is 70%. AndroidLintRunner.kt currently has 239 / 355 lines covered (67.32%). scripts/assets/test_file_exemptions.textproto does not currently have an exemption entry for AndroidLintRunner.kt to either o

Describe the bug The "Checks for Oppia Lesson Compatibility" workflow (lesson_checks.yml) calls //scripts:download_lesson_list with 5 arguments, but the script now requires a 6th argument so the path to a download config textproto that specifies allowed_classrooms, allowed_topic_ids, and allowed_interaction_ids. This 6th argument was introduced when pull_latest_lesson_versions.yml was added (which passes it correctly), but lesson_checks.yml was never updated to match. As a result, the "Download lesson version list" step fails with a usage/argument-count error on every scheduled Monday run, and no lesson compatibility data is being collected. Steps To Reproduce Navigate to Actions → "Checks for Oppia Lesson Compatibility" Open the most recent Monday cron run Expand the "Download lesson version list" step Observe the script exit with a usage error (argument count mismatch) Expected Behavior download_lesson_list should complete successfully, populate pinned_versions.textproto, and all

Now that minSdkVersion is 23, code that only supported Android 5.0/5.1 (API 21/22) is dead and the repo needs some cleanup. What to do 1. Freeze the final Lollipop builds, first scripts/src/java/org/oppia/android/scripts/release/FrozenReleaseConfig.kt lists only the KitKat build ("alpha" to setOf(16L)). The Play Developer API replaces a track's entire contents on each tracks.update, so the last Lollipop-supporting builds must be frozen before any minSdk-23 release ships. Otherwise they are silently deactivated and Lollipop users lose the app instead of seeing the OS-deprecation notice. The version codes are on upstream/target-sdk-36 (commit dba09933b) but not on develop: "alpha" to setOf(16L, 201L) and "beta" to setOf(196L). Add them, then update the "Currently frozen" KDoc list in the same file. 2. Drop the legacy multidex dependency Native multidex arrived in Lollipop, so androidx.multidex only does work below API 21. It survived #5630 because that PR removed the if (SDK_INT < LOLLIP