Requests from Transistor SDK are not been automatically intercepted

[danielgomezrico]

[REQUIRED] Step 2: Describe your environment

• Android Studio version: Im using flutter 3.16.4 on Intellij
• Firebase Component: Performance Monitor
• Component version: firebase_performance: 0.9.4+4

[REQUIRED] Step 3: Describe the problem

Hi

I'm using a library to monitor GPS locations called transistor. This library has a native implementation on Android and iOS from which does HTTP requests on the native side every x time.

I'm reporting this because the transistor SDK requests are not been caught by Firebase performance:

• I spoke with the library owner, and he says he is using Ok HTTP: https://github.com/transistorsoft/flutter_background_geolocation/issues/1243
• The network debugger on android studio does see the requests. I can see they are being done on the native side of android.

The only way I found is listening to the HTTP request events done by the transistor SDK, but| I lose the request time and payload size with that.

I already spoke with Firebase Support with someone named Amuel, and told me that its better to open an issue so that this issue is been taken this way and not via support, not sure why.

I don't understand what is happening since the Firebase performance is already listening to other requests I do on the flutter side but not those done by the transistor SDK.

I'm creating this issue here because the flutter team says their library is only a jump between this one and flutter in: https://github.com/firebase/flutterfire/issues/12655#issuecomment-2060840004

Steps to reproduce:

I made a sample: https://github.com/danielgomezrico/transistor-sdk-and-firebase-performance-error-example

It uses:

• transistor SDK
• firebase performance monitoring
  • It is able to track the requests been done in the native android side, I wrote an activity that does requests, but the ones done by the transistor SDK are not.

[lehcar09]

Hi @danielgomezrico, thank you for reaching out. I was able to reproduce the issue. Per checking, I can confirm that the requests are using OkHttp.

You mentioned that you have other requests done on the flutter side, do you mean that you have other network request on the flutter and they are traced? or do you mean the automatically collected data by Firebase Performance?

I'm thinking, if it's possible that there is a missing configuration in OkHttpClient so the request are not being traced by Firebase Performance. I'll notify our engineers about this and see what we can do here.

[danielgomezrico]

These requests are being tracked fine:

1. Requests done from the flutter side
2. OkHTTP Requests I do from the native android side directly in the activity of the sample I shared.

These are not:

3. All requests done by this library, that are done in the native android side and also using OkHTTP

This seems confusing to me because requests on 2. are being tracked automatically but 3. are not, and in theory they use the same thing 🤔

Does that answer your question? @lehcar09

[visumickey]

Can we confirm if this automatic tracking of network requests fail even with minification/proguarding disabled?

[danielgomezrico]

Thansk for the question, they advise you to put this configuration:

https://github.com/danielgomezrico/transistor-sdk-and-firebase-performance-error-example/blob/b51eb1cf5da0bc45edc29e815bc2ef2b1554d535/android/app/build.gradle#L69-L73

And this is the content: https://github.com/transistorsoft/flutter_background_geolocation/blob/master/android/proguard-rules.pro

[danielgomezrico]

@visumickey in theory, all the transistor SDK is being kept but not all the OkHTTP classes

I have some questions:

• What is the proguard configuration so OkHttp Requests get caught fine?
• Why the native requests get done fine even with the same proguard configuration? I mean the example has an activity that does a request, and that one gets caught fine but those from inside the transistor library does not (and it lives in the same example)

[danielgomezrico]

@visumickey ping 👀

[danielgomezrico]

@visumickey ping 👀 👀

[visumickey]

I think the issue might not be with how the app is configured. Based on my analysis, looks like some of the transitive dependencies are not instrumented. I'm trying to find the root cause and apply a fix when found.

[danielgomezrico]

@visumickey that's cool, do you have any updates?