Hi everyone,
I want to report an issue I’m having with a custom extension compiled with RUSH, which I suspect is related to a caching problem on Niotron’s servers/Companion, rather than an issue with the extension’s code.
Problem description:
I have an extension (PanelOperario) with several @SimpleProperty / @DesignerProperty correctly declared in the source code (for example ColorBordeUrgente, with its proper setter and getter). After recompiling with RUSH and testing in the Companion, as soon as the screen containing the component loads — without running any blocks, just by opening the screen — the following error appears:
Companion error: invoke: no method named `ColorBordeUrgente' in class com.rodaheva.paneloperario.PanelOperario
The method does exist in the source code and compiles without errors.
What I’ve already tried (without success):
- Completely removing the component/extension from the project.
- Re-importing the freshly generated
.aix. - Rebuilding from scratch (
rush clean+rush build). - Restarting the Companion (fully killing the process, not just minimizing it).
- Reconnecting the project from scratch (new QR code).
Despite deleting the extension and re-uploading the updated .aix, the system keeps behaving as if an older version of the component were still loaded, ignoring recently added methods/properties. This makes me think the issue lies in some kind of server-side cache (or in how the project identifies the extension internally, perhaps by package name/version), rather than in the Java code itself.
Question for the community:
Has anyone else experienced this behavior? Is there a way to force a full extension cache invalidation on Niotron’s server, beyond just removing the component from the project? Or is renaming the package/class recommended as a workaround while this gets fixed?
Thanks in advance, I’ll be watching for any suggestions or confirmation from a moderator on whether this is a known bug.