When importing and using Figma prototypes, you might run into certain issues. Follow our advice to ensure your prototype works as expected in Maze.
Our team has been continuously working to make our Figma integration as smooth as possible. If you have any feedback about the current limitations, or are running into issues that you believe go beyond them, please reach out to our team — we'll be happy to help!
Security and privacy
- Why do I see a "Your prototype needs at least two frames" error when importing my Figma prototype?
- Why isn't my Figma prototype loading in the prototype preview in Safari?
- When importing a Figma prototype, you'll see hotspot hints in the Build mode preview. Despite that, hotspot hinting doesn't work in the maze preview or in the live maze — even if you have hotspot hinting enabled in your Figma prototype. The goal is to avoid introducing bias when testers complete the task.
- Why can't I find all screens from my prototype in Maze?
- Why is the fixed footer not displaying correctly in my maze test?
- Maze doesn't formally support variables. Testing prototypes with variables may lead to unexpected behavior, especially when viewing results.
- Why is my maze not loading after importing a Figma prototype?
- Why do testers see a “This maze cannot be explored right now” error?
Known limitations when using interactive components
- Why am I getting an "Invalid mission path" error when I try to launch my maze live?
- Why are my testers getting stuck on my prototype with interactive components?
- Why are my interactive components with overrides displaying the default version of the component in the results and report?
- Why are the results for certain missions not being recorded?
To take advantage of the fast and efficient testing provided by Maze, we recommend creating a dedicated file for testing. This ensures shorter loading times and decreased payload for testers.
Still need help?
If you have any questions or concerns, please let our Support team know — we'll be happy to help!