Fix #5143: Update Robolectric to 4.7

[sandy99405]

Explanation

According to issue #5143, there was an error unexpected element <queries> found in <manifest> during the Bazel build.
That issue has been resolved in this PR.

1. Robolectric version has been changed to 4.7 and espresso-core to 3.5.0-alpha03 in every build.gadle file

2. In scripts/assets folder, the maven_dependencies.textproto file has been changed due to an exception.

This is the Bazel output after updating the Robolectric to 4.7 and maven_install

Essential Checklist

• The PR title and explanation each start with "Fix #bugnum: " (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• Any changes to scripts/assets files have their rationale included in the PR explanation.
• The PR follows the style guide.
• The PR does not contain any unnecessary code changes from Android Studio (reference).
• The PR is made from a branch that's not called "develop" and is up-to-date with "develop".
• The PR is assigned to the appropriate reviewers (reference).

For UI-specific PRs only

If your PR includes UI-related changes, then:

• Add screenshots for portrait/landscape for both a tablet & phone of the before & after UI changes
• For the screenshots above, include both English and pseudo-localized (RTL) screenshots (see RTL guide)
• Add a video showing the full UX flow with a screen reader enabled (see accessibility guide)
• For PRs introducing new UI elements or color changes, both light and dark mode screenshots must be included
• Add a screenshot demonstrating that you ran affected Espresso tests locally & that they're passing

[github-actions]

Hi! @sandy99405 Welcome to Oppia! Could you please follow the instructions here and sign the CLA Sheet to get started? You'll need to do this before we can accept your PR. Thanks!

[sandy99405]

Hi @adhiamboperes, do you want me to create another PR or solve what's in this PR? Please confirm

[adhiamboperes]

Hi @adhiamboperes, do you want me to create another PR or solve what's in this PR? Please confirm

I'm still in the process of reviewing the PR. I will leave my full feedback and assign it back to you.

[sandy99405]

Sure, thank you :)

[adhiamboperes]

Thanks @sandy99405!

To address the comments that I have left, please create a new PR. Make sure your branch name is not called "develop", because it is prohibited. Read the PR essential checklist carefully.

We have a wiki page for reading the CI results to help you debug: https://github.com/oppia/oppia-android/wiki/Interpreting-CI-Results

And finally to run the bazel tests locally, follow the instructions here: https://github.com/oppia/oppia-android/wiki/Oppia-Bazel-Setup-Instructions. Please note the you can also run one test class at a time.

[adhiamboperes]

Please check the CI logs, you will see that building with gradle fails with:

Caused by: java.lang.RuntimeException: Failed to transform '/root/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.68/46a080368d38b428d237a59458f9bc915222894d/bcprov-jdk15on-1.68.jar' using Jetifier. Reason: Unsupported class file major version 59. (Run with --stacktrace for more details.)

Please refer to the following for an explanation and a fix: issue with gradle plugin, jetifier and robolectric, this comment and this other one.

[adhiamboperes]

In the bazel test failure logs, I could still see that it fails with the error mentioned in the issue.

Could I propose that you test this PR by running some tests in bazel and see if it is reproducible? If say the tests always pass on your machine, we could look into the platform.

From the bazel logs, I saw that the issue is similar to this one: bazelbuild/rules_android#39, and one of the test runs fails because of the DrawableBindingAdapters.kt. You will need to verify from the CI logs if this particular class is the cause of all the test failures, and figure out why.

[oppiabot]

Hi @sandy99405, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 7 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!