APERVEIL / DOCS / FRAMER
Troubleshooting — Framer
Fixes for Aperveil shaders and blocks in Framer: an identifier already declared, a picture instead of the shader, a form that does not send, or a slow canvas.
06
Troubleshooting
- “Identifier 'addPropertyControls' has already been declared.”
- Framer's sample code is still in the file. Select everything in it, delete it, paste your copy again and save.
- A picture instead of the shader.
- This browser has no WebGPU, so the component shows the Look's poster. Chrome, Edge and Safari 26 draw the shader.
- Nothing appears.
- The component needs a size: set its width and height to Fill inside a sized frame, or give it fixed values.
- A block's form fields are disabled.
- The form is a preview until it has somewhere to send: paste a Formspree or webhook URL into Form endpoint in the property panel.
- The canvas feels slow.
- Turn Animate in editor off on the shaders you are not working on; they still move in preview and on the published site.
- The component does not load in the editor.
- A network filter or content blocker is stopping the Aperveil CDN (cdn.aperveil.com). Allow it and reload the project.
Color Looks, browser support, performance and access are the same on every platform: see the overview.