Iniciar sesión

[vicfdz94]

⚠️ Before posting ⚠️

• This is a bug, not a question or an enhancement.
• I've searched for similar issues and didn't find a duplicate.
• I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
• I agree to follow Nextcloud's Code of Conduct.

Steps to reproduce

Cause of error

Exception in thread "FinalizerWatchdogDaemon" java.util.concurrent.TimeoutException: ReferenceQueueDaemon timed out while targeting android.graphics.HardwareRenderer$DestroyContextRunnable@372389c
    at java.lang.Daemons$FinalizerWatchdogDaemon.refQueueTimeoutException(Daemons.java:690)
    at java.lang.Daemons$FinalizerWatchdogDaemon.waitForProgress(Daemons.java:650)
    at java.lang.Daemons$FinalizerWatchdogDaemon.runInternal(Daemons.java:467)
    at java.lang.Daemons$Daemon.run(Daemons.java:135)
    at java.lang.Thread.run(Thread.java:1564)

App information

• ID: com.nextcloud.client
• Version: 30350290
• Build flavor: generic

Device information

• Brand: google
• Device: blazer
• Model: Pixel 10 Pro
• Id: BP4A.260205.001.A1
• Product: blazer

Firmware

• SDK: 36
• Release: 16
• Incremental: 14624672

Expected behaviour

.

Actual behaviour

.

Android version

16

Device brand and model

Pixel 10 pro

Stock or custom OS?

Stock

Nextcloud android app version

3.35.2

Nextcloud server version

32.0.1

Using a reverse proxy?

I don't know

Android logs

No response

Server error logs

Additional information

No response

[joshtrichards]

This doesn't reference any Nextcloud code. Given the type of error, it may be outside the scope of the Nextcloud app entirely.

Are you able to reproduce it? And if so, how?