Obsolete API warning should indicate how to figure out what is calling the API. [116247924]

Fixed

Bug

Status Update

No update yet.

Description

xa...@google.com

created issue #1

Sep 20, 2018 08:29PM

Obsolete API calls only show the text related to the API, and not what is calling the API. This makes it difficult to troubleshoot the caller, especially if it's a third party plugin.

We have a boolean option to make it an error which will throw an exception. The stacktrace then allows to figure out where it's coming from. We need to document it.
For reference, the option is android.debug.obsoleteApi

We should also document this on d.a.c as well.

Comments

hu...@google.com <hu...@google.com> #2Sep 20, 2018 09:43PM

I wonder if we can get the stack trace using Thread.getAllStackTraces()[Thread.currentThread()] and show that to users together with the current warning instead of asking them to enable the debug flag.

To be less overwhelming, the stack trace can be first collapsed behind a link where the user can then click and see the details.

xa...@google.com <xa...@google.com> #3Sep 20, 2018 10:36PM

We could. We can't really collapse in the command line though. We'd have to store it in tmp file and just display a path to the file.

xa...@google.com <xa...@google.com> #4Sep 20, 2018 11:54PM

well I guess the issue of the file is that we don't want to do IO during configuration.

hu...@google.com <hu...@google.com> #5Sep 21, 2018 12:52AM

I see, so it doesn't work on the command line, I'm not sure if it's still worth it to try in the IDE.

xa...@google.com <xa...@google.com> Sep 24, 2018 11:25PM

Marked as fixed.

Issue 116247924