voiceflow extension works in chat widget but not in iframe

The extensions you define in your main page (with window.ChatWidgetConfig) only affect the chat widget loaded directly into your page, not the content inside the iframe.
Why?
The iframe loads a completely separate web app (from <my domain>), which has its own JavaScript context and cannot "see" or use the window.ChatWidgetConfig or any extensions you define in your parent page.
Any extensions (like file upload) must be registered and enabled within the codebase or configuration of the app running inside the iframe.
What can you do?
1. If you control the iframe source (<my domain>):
You need to define the extensions (like file upload) in the code/config of that app, just as you do in your main page.
This means duplicating the extension registration code inside the app that is served at <my domain>/iframe/<project id>.
2. If you do NOT control the iframe source:
You cannot inject or register extensions from your parent page.
You must ask the provider (or configure in the ChatDash/Voiceflow admin) to enable the file upload extension for your project on the whitelabel domain.
3. Testing Locally
If you want to test the widget with extensions, use the direct widget (not the iframe) on your page, where you have full control.
Summary Table
| Where to define extensions? | Where they take effect? |
|----------------------------|---------------------------------|
| In parent page | Only in parent chat widget |
| In iframe source code | Only in iframe widget |
What to do next?
If you have access to the code/config of the iframe app:
Add the same extension registration code (for file upload) there.
If not:
Contact your ChatDash/Voiceflow admin/support to enable the file upload extension for your whitelabel project.