-
Hello,
I'm packaging an app and I think I found a little bug on the Location UI UDP Port.
I'm testing on Cloudron 9.2Observed behavior :
I'm exposing a port custom UDP that is activated by default but the UI checkbox is not checked.
The actual port is activated as expected on the container and exposed by cloudron.
In addition if you enable the checkbox in this state and apply the configuration, it actually behave as expected, but if you refresh the page the checkbox is unchecked again.Expected behavior :
The checkbox should reflect the actual state of the port.Hope it helps to fix this.
-
oh that does sound like a UI bug indeed. So you are installing your custom app with the cli tool but the UI does not reflect that state on a fresh load is what you are seeing? What is the exact cli command if you use that? If the app (and/or package) is public, let us know so we can more easily reproduce and fix it.
-
I test on an empty cloudron vm, only this app.
I install with cloudron cli yes.cloudron install
The UI never reflect the UDP port state, the checkbox is always uncheked if you refresh the page.
The app is not public.
Maybe I can reproduce this behavior with an example. -
Sorry for my late reply, I didn't had time to work on the subject again.
The VM is with cloudron 9.2.0 Ubuntu 24.04.4 LTS Linux 6.8.0-117-genericIn the documentation there is no infos about "enabledByDefault" property for updPorts https://docs.cloudron.io/packaging/manifest/#udpports
In the manifest I declared the udp port like this, is it ok ?"udpPorts": {
"HS_MY_CUSTOM_PORT": {
"title": "My custom port",
"description": "My custom port description.",
"containerPort": 13478,
"defaultValue": 13478,
"enabledByDefault": true
}
}, -
Just see another clue in the javascript console when opening the Location settgins page of the app :
TypeError: Cannot read properties of undefined (reading 'HS_MY_CUSTOM_PORT')Seems related to the first line of this code :
for (const p in props.app.portBindings) if (tcpPorts.value[p]) {
tcpPorts.value[p].value = props.app.portBindings[p].hostPort;
tcpPorts.value[p].enabled = true;
} else if (udpPorts.value[p]) {
udpPorts.value[p].value = props.app.portBindings[p].hostPort;
udpPorts.value[p].enabled = true;
} else console.error(Portbinding ${p} not known in manifest!);tcpPorts seems undefined.
Maybe this bug appear when there is only udpPorts in the manifest, I have no tcp ports declared on the manifest.
-
J joseph moved this topic from App Packaging & Development
-
J joseph marked this topic as a question
-
J joseph has marked this topic as solved
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login