Extend some of the existing Troubleshooting Guide entries which can also occur when ProGuard or R8 is not correctly configured.
Also slightly improves the wording of some of the other points.
Checklist
[ ] New code follows the Google Java Style Guide\
This is automatically checked by mvn verify, but can also be checked on its own using mvn spotless:check.\
Style violations can be fixed using mvn spotless:apply; this can be done in a separate commit to verify that it did not cause undesired changes.
[ ] If necessary, new public API validates arguments, for example rejects null
[ ] New public API has Javadoc
[ ] Javadoc uses @since $next-version$
($next-version$ is a special placeholder which is automatically replaced during release)
[ ] If necessary, new unit tests have been added
[ ] Assertions in unit tests use Truth, see existing tests
[ ] No JUnit 3 features are used (such as extending class TestCase)
[ ] If this pull request fixes a bug, a new test was added for a situation which failed previously and is now fixed
[ ] mvn clean verify javadoc:jar passes without errors
Purpose
Extend some of the existing Troubleshooting Guide entries which can also occur when ProGuard or R8 is not correctly configured.
Also slightly improves the wording of some of the other points.
Checklist
mvn verify, but can also be checked on its own usingmvn spotless:check.\ Style violations can be fixed usingmvn spotless:apply; this can be done in a separate commit to verify that it did not cause undesired changes.null@since $next-version$(
$next-version$is a special placeholder which is automatically replaced during release)TestCase)mvn clean verify javadoc:jarpasses without errors