-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
[talker_bloc_logger] Since upgrading to versions 4.x.x, not seeing any logs anymore (Flutter 3.19.3) #200
Comments
Hello @WieFel ! |
Sure! Android Studio version info
Flutter doctor
|
Same behavior with talker_dio_logger. I think it's not related to the Flutter SDK version because I'm having the exact problem with Flutter 3.7.x |
same here, no logs any more I just installed this package with version talker 4.1.0 and I am on flutter 3.19.4, I followed the instructions given in package but not seeing any logs |
Hello everyone! Now it seems that this is related to the output method in talker_logger lib |
As workaround, you can replace the output callback: |
This also happens in talker_dio_logger. Having: _dio.interceptors.add(
TalkerDioLogger(
settings: const TalkerDioLoggerSettings(
printRequestHeaders: true,
),
),
); |
any update? |
still not resolved? |
Hello everyone! You can use the following code for the TalkerDioLogger: final talker = TalkerFlutter.init();
_dio = Dio();
_dio.interceptors.add(
TalkerDioLogger(
talker: talker,
),
); Why is this happening? |
And now I move back default Talker output method for mobile platforms. talker_flutter: ^4.1.4
talker_dio_logger: ^4.1.4
talker_bloc_logger: ^4.1.4 |
Describe the bug
I just upgraded the
talker_bloc_logger
package from version2.4.0
to latest4.0.3
, and noticed that suddenly I don't see any bloc logs anymore. I also recently upgraded to latest Flutter version3.19.3
, so it could be related.To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect the logs to just show normally
Smartphone (please complete the following information):
The text was updated successfully, but these errors were encountered: