Error logged in API 33 and 34

I get this error:
2024-03-09 13:24:15.448 8756-8780 EGL_emulation com.example.abschlussaufgabe E tid 8780: eglGetConfigAttrib(1268): error 0x3005 (EGL_BAD_CONFIG)
2024-03-09 13:24:15.448 8756-8780 EGL_emulation com.example.abschlussaufgabe E tid 8780: eglGetConfigAttrib(1268): error 0x3005 (EGL_BAD_CONFIG)
2024-03-09 13:24:15.448 8756-8780 libEGL com.example.abschlussaufgabe E call to OpenGL ES API with no current context (logged once per thread)
2024-03-09 13:24:15.448 8756-8780 libEGL com.example.abschlussaufgabe E call to OpenGL ES API with no current context (logged once per thread)
2024-03-09 13:24:15.462 8756-8776 OpenGLRenderer com.example.abschlussaufgabe W Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without...
2024-03-09 13:24:15.462 8756-8776 OpenGLRenderer com.example.abschlussaufgabe W Failed to initialize 101010-2 format, error = EGL_SUCCESS
2024-03-09 13:24:15.469 8756-8776 Gralloc4 com.example.abschlussaufgabe I mapper 4.x is not supported
2024-03-09 13:24:15.476 8756-8776 OpenGLRenderer com.example.abschlussaufgabe E Unable to match the desired swap behavior.

It doesn't break down the app. The app works absolutely fine. Just the error is being logged which is problematic for me.

I used Pixel 7 Pro with API 33 and 34.

Does anyone know a solution for this bug? It's a graduation project where I had to use Kotlin and XML (yes, I would have also preferred Jetpack Compose).

The report names no source files, tests, or entry points; begin by reproducing the EGL log on a Pixel 7 Pro running API 33 or 34 and determine whether it is produced by the Rive Android runtime or the app's rendering setup. Done means identifying the source and documenting or implementing a fix that removes the problematic logging without affecting the app's behavior.