1246055 - GeckoLoader couldn't load mozglue while launching from Android Studio 1.5

Status: RESOLVED FIXED

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

Description

[SUN Haitao]

Steps to reproduce:

0. Build and install Fennec with `./mach build && ./mach package && ./mach install`.

1. Tap the shortcut on the device screen. Fennec launches and runs normally.

2. Open the project in "Android Studio 1.5".

3. Click the "Run 'app'" button. Fennec launches and crashes with the following error log:
 A/GeckoLoader: Couldn't load mozglue. Trying native library dir.
 A/GeckoLoader: Library doesn't exist when it should.

Comment 1

[Nick Alexander :nalexander [he/him]]

Thanks for the report!

<snip>

> 3. Click the "Run 'app'" button. Fennec launches and crashes with the
> following error log:
>  A/GeckoLoader: Couldn't load mozglue. Trying native library dir.
>  A/GeckoLoader: Library doesn't exist when it should.

I think you are building the "automation" product flavor, rather than "local" or "localOld".  I've updated the documentation at https://developer.mozilla.org/en-US/docs/Simple_Firefox_for_Android_build#Setting_the_RunDebug_Configuration_and_Build_Variant to clarify this.  You can also see the mailing list post at https://mail.mozilla.org/pipermail/mobile-firefox-dev/2016-January/001698.html.

Can you verify that you've got "app" and "localOld" (or "local", if you're testing on a new device)?  If you still do, then we have a different problem.

Comment 2

[SUN Haitao]

I tested the solution on a Samsung SM-G5500 (API 22, both "local" and "localOld") and a HUAWEI Che1-CL10 (API 19, "localOld"). As far as I can tell, it works quite fine.

Comment 3

[Nick Alexander :nalexander [he/him]]

(In reply to SUN Haitao from comment #2)
> I tested the solution on a Samsung SM-G5500 (API 22, both "local" and
> "localOld") and a HUAWEI Che1-CL10 (API 19, "localOld"). As far as I can
> tell, it works quite fine.

Excellent.  I'm going to close this as "works for me".

Sorry for the confusion!

Comment 4

[SUN Haitao]

Wait a minute. Could gradle issue a warning until "automation" flavor is done?

Comment 5

[Nick Alexander :nalexander [he/him]]

(In reply to SUN Haitao from comment #4)
> Wait a minute. Could gradle issue a warning until "automation" flavor is
> done?

Well, yes and no.  I think I'll just remove that target entirely from local builds.  But an "automation" flavor is needed for use in automation, and the different is that automation builds don't include libraries!  Those are packed in later by |mach package|.  There's a *lot* of history here.

So we can make the situation better, but not by warning or removing the "automation" flavor.