Same with me!

Hi @sv_n @TGM1 ,

Thanks for flagging! We’re investigating this behavior, so could you let me know your working environment?

• OS


• Version


• If you use Desktop app, does this happen in browser too?

Could you try the troubleshooting below for basic troubleshooting?

• Close any Figma tabs you’re not using


• Browser : Force-quit and open Figma in a new browser window.


• Desktop App: Force-quit the Figma Desktop app and restart it. If the issue persists, try clearing the cache.

Please let us know how that works!

Thanks for your understanding.

Toku

Hi @y_toku,

thank you very much for your answer. I can of course provide you with more information. We work with macOS 14.5 and use the Figma app to create the prototypes. The behavior occurs both in the app when you present the prototype there, as well as in the browser itself (here I noticed it in the Safari browser). However, it also occurs when you open the prototype on your cell phone (iPhone 14 Pro, iOS 17.5.1, Safari).

Currently, the error does not always occur and cannot be intentionally reconstructed. If the error occurs and the prototype is reloaded, it often no longer occurs.

We have already opened the prototype on several computers to see if it is a local problem, but it occurs regardless of the end device.

It is annoying that the error has already occurred in user tests and has led to them having to be aborted.

Thanks @sv_n for the details!

It looks like we’ve received some reports from users about this issue before. In those cases, their app version was earlier than 24.13. Could you check if your iOS Figma app is version 24.14 or higher?

Regarding Safari, it seems that I can’t replicate it on my end. If the issue persists, could you submit a bug report detailing the steps that led to this issue? You can do so by following the link:

Please let me know how that works!

Thanks,

Toku

Thanks @y_toku, I used the latest app version on my iPhone 24.15.0 and still had the problems

And as far as the issue of reproducibility is concerned, we ourselves also have the problem that we can’t create the bug. Sometimes it is there in prototypes and sometimes not. What we can provide is a video from a user test in which you can see that users were unable to complete the test due to the hotspots being moved.

@y_toku here is a video of the bug in a current prototype, where you can clearly see that the interaction hotspots have slipped over the actual buttons. In the past, the hotspots were sometimes very far away from the actual buttons.

and the problem has also reappeared on the smartphone. And here the hotspots are much further away from the actual buttons at the end.

Thanks for sharing these video! Very helpful for us to understand the issue. Please let me share these internally and I will get back to you once I have any updates.

Thanks for your patience.

Toku

Hi there,

I have got the exact same problem with a prototype that I want to test.

Sometimes, it works perfectly fine and then out of the blue, the interaction area move from its original spot.

However, this bug only appears on mobile (Android and iOS, in-app and browser). I don’t have this problem when previewing it on desktop.

Really appreciate it if you can find a solution.

Thank you for the info! I just added your information with our bug report. I will get back to you once I have any update.

Thanks for the patience.

@sv_n @Jeannet @TGM1

Hi there,

Thank for waiting! It seems the fix is out. Could you check if it’s back to normal after reloading the tabs or restarting Figma app?

Please let us know if the issue is still there!

Thanks,

Toku

Hey Toku,

thank you for your notification 😊 After the bug fix everything looks and works normally.

Thanks!

Great! Glad to know it’s working normally:) Thanks for flagging this bug!!