Hi ​@Mathias_B, thanks for reporting this and sharing your test details!

To help us better understand what’s happening and potentially escalate this to the right team, could you please provide a few more details?

1. Are you using an external mouse or trackpad, or are you switching between the built-in trackpad and an external device?

2. Does the misdetection happen at a specific time (e.g. on app launch, after sleep mode, after switching inputs)?

3. Is this happening on another board as well?

4. Do you notice the same issue when using Miro in a browser like Chrome or Safari?

5. Did this start happening after a macOS or app update?

6. If you’re able to, could you share a short video showing how the app misinterprets the input device? That would really help us see what you're seeing.

Once you’ve shared those, we can look into possible patterns or known issues and pass everything along to the Miro team if needed.

Thanks again for your patience and detailed report so far!

Sure, here you go:

1. When at my desk: external mouse connected via Logitech Unifying USB or directly via bluetooth. (both misdetected)
   When mobile: built-in trackpad
2. No specific event identified, seems to happen all the time
3. All board
4. Both, in the mac desktop app and in Chrome browser
5. Don’t know, I can’t remember when it worked correctly. If any, many months or even some years ago.
6. You can find the video recording here: 

    

HI ​@Mathias_B, 

Thanks so much for the detailed follow-up— and for sharing the video, that’s incredibly helpful. Based on the information you've provided, I’ll go ahead and escalate this to the Miro Support team so they can investigate more deeply. I’ll include all your notes and the recording to help the team better understand the issue.

You should receive an update via email soon, and I’ll follow the thread to make sure everything is moving along.

Thanks again for your thorough reporting!

Hi, thanks for checking in. I tested the solutions proposed by ​@Eca. Unfortunately, the auto-detection is still not working correctly. 

Thank you for the update, ​@Mathias_B! Is this meant to be your reply to the ticket? If so, kindly send your message in that thread - #849861 - instead.