-
-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No log is printed with Slf4j 2.x.x #249
Comments
We have the same problem in our app, just after upgrading to Android target sdk 33 and setting both source- and targetCompatibility to JDK 11. After a bit of deep diving we noticed the following:
Same thing happens when trying to use the original logback dependencies without the logback-android one like this:
This makes me believe that there is a general incompatibility wiith either Android 13 or Java 11 in the core libraries. I will research further and if necessary create a ticket for ch.qos.logback. If so, i will link it here. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
We're also affected by this issue. I noticed the major release linked above has no specific date, would you be open to cutting that release sooner than later? |
Fix is released in v3.0.0. It may take a while before it's indexed in Maven Central. |
Thank you! |
Thank you so much. |
Description
I apply the slf4j version 2.0.3 in android project.
I tried to print log with debug, error level but nothing is printed. I check via logcat.
If I rollback to version 1.7.36, it works.
Steps to reproduce
implementation("org.slf4j:slf4j-api:2.0.3")
implementation("com.github.tony19:logback-android:2.0.0")
Environment
Android version : 9
Device : Huawei Nova 3i
The text was updated successfully, but these errors were encountered: