IssueTracker

I don't think #1 makes a lot of sense. There are already potentially libraries out there without that metadata.

#2 makes the most sense to me, but in case we cannot be 100% reliable we should allow blacklisting libraries as described in #3. This should probably be handled globally for a project (in gradle.properpies rather than in the DSL)

As I have mentioned I don't think there is a silver bullet. #2 does not work on 100% and #1 will take time before devs will provide the metadata. #3 is in my opinion very important to introduce asap, as the developers have no way how to workaround it at this stage. Also in the future there can be any other issue and there is nothing wrong in doing #3 until we figure out something robust (or for instance finally migrate work manager and navigation to androidx that would make #2 a feasible solution).

Yes, I'm working on #3 right now to unblock users. We can continue thinking about #2.

Starting with AGP 3.3.0-rc01 and 3.4.0-alpha04, to blacklist libraries that should not be jetified, users can add a comma-separated list of regular expressions to the following property in the gradle.properties file:
    android.jetifier.blacklist = ...

If a library's absolute path contains a substring that matches one of the regular expressions, the library won't be jetified.

For example, if the property is
    android.jetifier.blacklist = doNot.*\\.jar, foo
then "/path/to/doNotJetify.jar" won't be jetified.

Change-Id: I6531fe0faafa45dc2811c5223ba199ccce5fee53


Note that this is only a temporary workaround while we work on a proper solution.