Can't access SignalR logging on Android

[lepicekmichal]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Logger is not preffered solution for android and even if we use it somehow internally, then we cannot turn it on. That's because it uses HubConnection class itself for tag. And that gets proguarded/obfuscated.
ADB does not allow tag of asterisk or dots - eg: "..*.a$HubConnection".

Please allow us to set up logging from java/kotlin side on Android.

Expected Behavior

Logging into Logcat and possible override.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

[rafikiassumani-msft]

@lepicekmichal Are you running an obfuscator on the SignalR library? In case this is the issue, and you would like to hardcode the tag name, then we will welcome a PR.

Hi @lepicekmichal. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[lepicekmichal]

I don't run obfuscator, I guess I looked wrong. Nevertheless LoggerFactory.getLogger(Class<*> class) does return malformed tag and on top of that, it's not extendable like the other platforms.
Why is HubConnectionBuilder missing configureLogging method?

[BrennanConroy]

There is no configureLogging method because Java configures logging globally for your app. We use slf4j and you bring your own logging system that plugs into slf4j
https://docs.microsoft.com/aspnet/core/signalr/java-client?view=aspnetcore-6.0#add-logging

[lepicekmichal]

I saw these docs, unfortunately it doesn't print anything, at all. I still think it's a bug, but if someone can elaborate on how to make it work, extend the documentation chapter, that would be greatly appreciated.

[BrennanConroy]

What are you trying that isn't working?

[lepicekmichal]

Well I added dependencies, either of these:

implementation "org.slf4j:slf4j-jdk14:1.7.36"
implementation 'org.slf4j:slf4j-android:1.7.36'

And that's pretty much it, there is no extensibility.

I printed out the name of logger which is provided inside HubConnection class like this LoggerFactory.getLogger(HubConnection.class);; and the name it printed out was something like *.*.a$HubConnection.
So there was no way I could turn on that tag via adb shell prop.

I could also try other 3rd party dependencies which have docs about how to add configuration file making it possible to print inside logcat, but that would not help with extensibility. Can't show them on screen, can't upload them to our log servers.

[BrennanConroy]

I printed out the name of logger which is provided inside HubConnection class like this LoggerFactory.getLogger(HubConnection.class);; and the name it printed out was something like ..a$HubConnection.

If you manually create a logger with "HubConnection" as the name does that work in your scenario?

That's what we were considering in #40392 (comment)

[lepicekmichal]

Yeah, if it got replaced inside library with such string, it would help with not seeing any logs at all.
Would not help with processing the logs ourselves though.