IssueTracker

This is not the same issue. 116170625 is a missing R class. This is just a warning that is shown in both cases.

Note this seems to be related to Fabric. Removing `apply plugin: 'io.fabric'` (using v1.25.4) makes the warning go away.

Will Fabric work without the plugin? We're using Crashalytics and perf-mon in our app.

... no, and (if you don't remove all Fabric references) your app will crash
on open!

(nearly avoided sending that to prod)

On Wed, Jan 16, 2019 at 11:26 AM <buganizer-system@google.com> wrote:

Funny, it doesn't, apart from the fact I had to disable D8 because of alot  of missing classes at runtime (maybe linked to this issue?)

be sure to compile on release (with proguard and everything) and test, mine was working fine on debug too.
also, while trying to get a new version to compile i also disabled D8, so maybe that's related

Look likes nobody at Google uses Firebase…

So who's supposed to fix this? Do we have to release without Firebase, or is there some kind of other workaround?

I have to put out a release in the next few days... maybe just downgrading something would work?

It's just a warning, it will be fixed at the end of 2019 once these deprecated methods are actually removed.

The warning level is "Error", instead of "Warning". It causes annotation processors stopped working. So you will notice that no class is generated under build directory, e.g. R.java

Have anyone released project with this warning? Does fabric working? Any problems?
hope assigned je...@google.com will tell us something

Not sure what is the difference, but R.java is generated properly for our project and I pushed an update yesterday, Crashlytics is working fine. No any issues with annotation processors. The only issue is the annoying warning about the method being deprecated. So I guess there is another issue which doesn't affect our project.

The same problem here...

Just try using 'com.android.tools.build:gradle:3.2.1' instead of the latest one. It seems to be working fine for me but I haven't tested it on a production (ProGuard) build yet.

My app seemed to build without any issue but the versionName wasn't getting updated from the productFlavours in the build.gradle file. I ended up downgrading to Android Studio 3.2.1. I think I'll stay there until this gets resolved.

So we got at least 2 guys saying commenting out "apply plugin: 'io.fabric'" is fine, and one guy saying it breaks production apps. Which is it? I removed it and the app seems to be compiling but I need someone that knows what they are talking about to confirm this :)

If you want Fabric to work, do not comment out the `apply plugin: 'io.fabric'`. You'll get a Gradle warning but you can just ignore it. It won't cause your build to fail or your app to break.

Hi all,

Can any of you provide me with a full stack trace and/or a toy project where this bug happens?

It would help me fix this issue ASAP.

To get a stack trace run 'gradlew' with '--warning-mode all --stacktrace'

attached is a full stacktrace as requested, obtained by running:

 ./gradlew --warning-mode all --stacktrace -Pandroid.debug.obsoleteApi=true clean > crashlyticsStackTrace.txt

The same problem here... For time being removing Fabric :(

Not sure if this is still needed, but I've attached a toy project that reproduces the issue (try `./gradlew assembleDebug`).

Hi all,

Thank you for your patience.

It looks like the bug in all cases is coming from crashlytics and I've filed a bug with them.

I will keep you updated on the status.

thanks!

For me also same issue

WARNING: API 'variant.getExternalNativeBuildTasks()' is obsolete and has been replaced with 'variant.getExternalNativeBuildProviders()'.
It will be removed at the end of 2019.

I'm closing this as the bug is on crashlytics and has been filed with them.

Does Crashlytics / Fabric / Firebase / etc have a publicly accessible issue tracker that I can follow along with? Just so I can get notified when a fix gets rolled out?

There is a github thread on this issue:
https://github.com/firebase/firebase-android-sdk/issues/198#issuecomment-458756047

Please expedite this bug fix, since this is being pending from too long now.

The same on 3.4 beta 4

Hi all,

The issue is not in android studio. It is in crashlytics.
Updating to a newer version of AS will not solve it.

The crashlytics team are already working on it, but you should be able to safely ignore the warning.
If you are having compilation issues, they are most likely NOT being caused by this warning. Please take this into consideration when debugging.

To check the status of the issue, please check the github link I added in comment #28

Also, please refrain from commenting "me too" on the github thread as it only floods it with unhelpful messages.

And please read the entire thread before commenting, as it is likely that someone has already said the same thing and has already been answered.

In my case it is NOT just a warning, I am unable to make the build.
I had to revert the gradle plugin back to 3.2.1

okay

I have another issue with its I mean see the screenshot and solve these issues.

The same, I had to revert the gradle plugin back to 3.2.1

Same here. I too had to get back to 3.2.1

Same issue here. Not able to build after adding fabric dependencies.

pity fabric team doesnt test before releasing :(

This has been fixed in the 1.28.0 release of the gradle plugin, which went live today.
Users should have this in their top-level build.gradle:
 buildscript {
   // ... repositories, etc. ...
   
    dependencies {
        // ...other dependencies ...
        classpath 'io.fabric.tools:gradle:1.28.0'
    }
}

@39 Can't confirm. I use `classpath 'io.fabric.tools:gradle:1.28.1'` , and the first thing I see on the build window is this:

"WARNING: API 'variantOutput.getPackageApplication()' is obsolete and has been replaced with 'variant.getPackageApplicationProvider()'.
It will be removed at the end of 2019.
"

Are you sure this is coming from fabric and not some other plugin?

Since the gradle upgrade, several plugins have been issuing that warning.

Yes, this is definitely Fabric, it's not fixed in 1.28, same for 1.30 and 1.31

With the flag `-Pandroid.debug.obsoleteApi=true` this stack trace is reported:
https://gist.github.com/gildor/60b4dc330fee12b929baeae758df1ab5

You can see that it caused by FabricTaskBuilder.crashlyticsUploadDistribution task builder

I see that this issue closed as "Won't fix", I will report a new one

Reported to firebase-android-sdk issue tracker:
https://github.com/firebase/firebase-android-sdk/issues/711

It's quite confusing because neither issuetracker.google.com has a proper category for Crashlytics and Fabric Gradle Plugin nor firebase-android-sdk (which doesn't include code of Fabric Gradle Plugin)