Pre-launch report strict mode warnings

from the CommonsWare Community archives

At May 13, 2020, 2:19am, Jan asked:

Per the screen shot, google play console pre-launch report shows warnings for unsupported APIs.
But I can’t find any problem with some of them. For example, the stack trace will trace a call back to my activity’s call to setContentView(layout ID). The documentation does not show that specific API to be “greylisted”. So I assume there’s something in the java code being invoked that has a problem.

And for many of the warnings, the stack trace only shows java code and never traces back to my app’s code at all.

So should I worry about these warnings? How should I go about resolving them - especially the ones in the java code where I don’t even know where my app invokes the code (not in the stack trace).

Thanks in advance for any enlightenment you can give.

strict_mode
strict_mode987×763 67.7 KB

At May 13, 2020, 10:36am, mmurphy replied:

Roughly speaking, for any such API, there are two possibilities:

  1. You are calling it directly (in this case, apparently not, based on your question). If you were, find some alternative way of accomplishing your objective, or try to redesign the app to not need that API.

  2. A library is calling it. Make sure that you stay on the most recent version of the library. If it if a Google library (e.g., an androidx class), and the most recent version of the library appears to be calling it, file a bug report with a reproducible sample project, to ensure that the Google engineers are aware of the problem. If it is a third-party library (e.g., something other than android, androidx, or your package is calling it), see if the library is being maintained. If it is, file a bug report. If it is not, find a replacement (alternative library, rewriting it yourself, or jettisoning the feature).

At May 13, 2020, 2:15pm, Jan replied:

I’m going to try to see if I can get this to work:
https://commonsware.com/blog/2018/06/12/strictmode-api-greylist-monitoring.html