warning: [options] bootstrap class path not set in conjunction with -source 1.6

[highwater]

Hi Sam, did you get this error when running your test on Intellij?

Warning: Activity com.whatsapp.ViewProfilePhoto$SavePhoto Typeref <Application,Lcom/whatsapp/ViewProfilePhoto$SavePhoto> IClass <Application,Lcom/whatsapp/ViewProfilePhoto$SavePhoto> declared in manifest, but is not in framework-created types map
Computing instrumentation to do took 144.814
Performing bytecode instrumentation
Lcom/whatsapp/EmojiPicker$EmojiAdapter$1; -- Landroid/widget/LinearLayout;
Lcom/whatsapp/EmojiPicker$EmojiAdapter$1; -- L?;
Lcom/whatsapp/EmojiPicker$EmojiAdapter$1; -- L?;
Lcom/whatsapp/EmojiPicker$EmojiAdapter$1; -- L?;
.
.
.
Performing bytecode instrumentation took 15.41
Generating harness
warning: [options] bootstrap class path not set in conjunction with -source 1.6
/home/ncc/apkcompare_out/com.whatsapp/bin/droidel_classes/generatedharness/GeneratedAndroidHarness.java:13867: error: code too large for try statement
    catch (Exception e) {
    ^
/home/ncc/apkcompare_out/com.whatsapp/bin/droidel_classes/generatedharness/GeneratedAndroidHarness.java:1110: error: code too large
    public static void androidMain() {
                       ^
Note: /home/ncc/apkcompare_out/com.whatsapp/bin/droidel_classes/generatedharness/GeneratedAndroidHarness.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

This happens both on Eclipse and Intellij but not on terminal. I've been figuring out this error for 2 days without luck.

Thanks.

[sblackshear]

Hi Coraline, This output looks like it's coming from the old version of the tool before I made all of the improvements last week. Are IntelliJ and Eclipse using the classes from the newest version of Droidel? I might grab a fresh Droidel copy from GitHub and create a new project in IntelliJ just to be sure.

[highwater]

Yes, I already grabbed the latest like 5 times today just to make sure. No luck.

[sblackshear]

The one other thing to try is to make sure you're not using the -frameworklessHarness flag (or passing true for the generateFrameworkIndependentHarness s flag of AndroidAppTransformer. This flag gives you behavior more like the old version of the tool.

[highwater]

That looks like the problem, it's working now​.