Closed Bug 1595926 Opened 3 months ago Closed 3 months ago

Android studio fails to run gradle and warns of distributionSha256Sum in wrapper

Categories

(Firefox Build System :: Android Studio and Gradle Integration, defect)

defect
Not set

Tracking

(firefox72 fixed)

RESOLVED FIXED
mozilla72
Tracking Status
firefox72 --- fixed

People

(Reporter: bryce, Assigned: Agi)

Details

Attachments

(1 file)

I'm encountering an issue with setting up my GeckoView dev env. When opening my mozilla-unified dir I receive the following error:

WARNING: It is not fully supported to define distributionSha256Sum in gradle-wrapper.properties.
Using an incorrect value may freeze or crash Android Studio.
Please manually verify or remove this property from all of included projects if applicable.
For more details, see https://github.com/gradle/gradle/issues/9361.

If I remove this line then Android studio seems to no longer have issue.

Further details:

  • Linux host
  • Mozilla unified at central commit d609eb2a8fe2, from 2019-11-11
  • Android Studio 3.5.2
    • pointed at the sdk in my ~/.mozbuild dir
  • I use the following mozconfig:
ac_add_options --enable-application=mobile/android
ac_add_options --target=i686
ac_add_options --with-java-bin-path=/usr/lib/jvm/java-8-openjdk-amd64/bin/
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../mozilla-builds/obj-droid-i686-opt

It's not clear to me if Android Studio mutated my SDK in some way that may have led to this or not, but it did appear to do some downloading when I pointed it at the existing mozbuild Android SDK.

Yes, this is a known issue. It's an Android Studio error. The work-around is to delete the offending line.

agi: can you land this work-around?

Flags: needinfo?(agi)

Yeah, let's do this.

Flags: needinfo?(agi)
Pushed by asferro@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/27db9b37efbe
Don't use distribution256Sum until Android Studio is fixed. r=snorp
Status: NEW → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.