"Component 'Fallback' not resolved" Error with Custom Components

General
1

Hi everyone,

I’m encountering a strange issue with Custom Components in Qodly. Here’s what happens:

  1. I install a Custom Component and initialize it correctly.
  2. Everything works perfectly: the component displays and functions as expected.
  3. However, at some point, without making any particular changes, the pages where the component is used stop recognizing it.
  4. Instead, I get an error: “Component ‘Fallback’ not resolved”.

I’ve checked a few things:

  • The initial setup was correct.
  • The component was working fine before the error appeared.
  • No significant changes were made to the project or the component just before the issue occurred.

Has anyone else encountered this issue or has any idea what might be causing it? Are there specific checks or solutions I could try in this case?

Thanks in advance for your help!

2

Hello Romain!

Does this error persist even after clearing your browser cache and refreshing the page?

3

Hello Fadwa,
I cleared the browser cache and refreshed the page as you recommended, but the issue still persists. To illustrate the problem, I’ve attached a screenshot:

  • The top part shows the broken component displaying the “Component ‘Fallback’ not resolved” error.
  • The bottom part shows the same component working correctly
4

error fallback
error fallback1242×404 30 KB

5

I’d like to add that the solution you suggested does work when the error specifies the name of the component instead of ‘Fallback’.

For example: when I encounter an error like “Component ‘pdfViewer’ not resolved”, clearing the browser cache and refreshing the page usually solves the issue.

However, in this case, since the error only mentions ‘Fallback’, the suggested fix doesn’t seem to apply.

6

Could you provide the version of the components you’re using, or alternatively, share the manifest.json file for the custom components?

7

The version of the FileManager component I’m using is v0.1.0. It includes two small modifications I made, as shown in the attached screenshots, which are limited to style changes.

After making these changes, I used the npm run build command to generate the .zip file for the component.

css1
css12728×114 38.4 KB

css2
css21572×112 29.2 KB

I encountered the same error with the pdfViewer v0.2.1 , to which I made no modifications.

8

You’re probably using an old version of the qodly cli. Could you try running the command npm i @qodly/cli@latest in your component’s code? After that, regenerate the build using npm run build, reimport it into your Qodly application, and see if the issue persists?

9

After running the command npm i @qodly/cli@latest , the @qodly/cli package was updated to the latest version. I then recreated the .zip , reimported it into Qodly, cleared my cache, and reloaded the page. Unfortunately, I’m still seeing the same issue as shown in the “error fallback” screenshot I shared earlier in this post.

10

Can you reload the page where the component is located?

image
image259×302 14.4 KB

11

Yes, I also tried refreshing as you suggested, but it didn’t work.

12

Does the error persist even after manually re-dragging the component and resetting it from scratch?

13

No, the ‘error fallback’ screenshot from 4 days ago shows that the same component was added without errors after manually dragging the component again.