Database instrumented even if disabled

[stefanosiano]

Description

A user reported the addition of db.sql.room and db.sql.query spans, even if database instrumentation is removed.
Gradle plugin version: 5.5.0 with android sdk 8.13.2

Reported config:

// AndroidManifest.xml
<application>
...
        <meta-data
            android:name="io.sentry.traces.activity.enable"
            android:value="false" />
</application>

 
// app/build.gradle
sentry {
...
tracingInstrumentation {
        enabled.set(true)
        features.set(EnumSet.allOf(InstrumentationFeature::class.java) - InstrumentationFeature.DATABASE)
        logcat {
            enabled.set(true)
            minLevel.set(LogcatLevel.INFO)
        }
    }
}

The plugin is applied only to the app level (and set in root with apply false)
What was tried:

• run ./gradlew clean at the root level
• Click on Clean Project in android studio

We should try to reproduce the issue

[ishanzuaim]

Any updates on this? This is my current workaround, but would be keen on a proper solution

            options.setBeforeSendTransaction { transaction, hint ->
                transaction.spans.removeIf {
                    listOf("db.sql.room", "db.sql.query").contains(it.op)
                }
                transaction
            }

[romtsn]

no update, we'll take a look at it soon!