FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We will start the migration process in one hour.
The community will be then in READ ONLY mode.
Read more: Important
information on the platform change.
01-24-2024 11:59 AM - edited 01-24-2024 12:34 PM
I have build an snap app of architecture amd64 for ctrlx works virtual it works fine. but when I build arm64 for real hardware it doesnot works on real device.
Note: one possible issue is in tasks.json file in .vscode directory.
IP of virtual device is assigned here in this file.
I tried to run app on real device by using its IP for example real device ip is 111.11.15.2:3005 (not real) still application is not running. but when i run it on virtual envoriment it works.
01-24-2024 01:51 PM - edited 01-24-2024 01:51 PM
Hello,
What is your codebase? Can be that you are cross compiling something that cannot be cross compiled 🙂
01-24-2024 04:03 PM
Hi @jawad
The task you are refering to builds the snap and uploads it afterwards directly to a ctrlX CORE. Can you first try to just build it for arm architecture?
Does this work? If not, what is the error message?
01-25-2024 05:49 AM
Hi @nickH,
I have build the snap for arm64 successfully. and installed on ctrlX core but it doesnot works. before it, I have build amd64 for ctrlx Core virtual and that works.
project is in nodejs
01-25-2024 07:44 AM
Can you give some more information? What your snap does, what is not working? Do you get some error messages?
01-25-2024 08:55 AM
I've had problems with certain npm packages that doesnt work on arm. For instance the nodejs better-sqlite only has x86 binaries. So it might be a depencency that doesnt work.
01-25-2024 08:58 AM
Exactly, that is why i was asking! Possibility are 2:
- you built with the node plugin which doesn't support cross compiling (see our examples)
- you used some modules wich cannot be used on arm64
01-25-2024 10:35 AM
Moved to corresponding sub forum SDK.
01-25-2024 11:55 AM - edited 01-25-2024 12:03 PM
Hi @MauroRiboniMX @AndreasL @nickH
Upon initiating my Snap application, an interface featuring a login page is displayed during startup. The application relies on various dependencies such as sqlite3, sockets.io, etc.
List of dependencies are as under:-
All these dependencies are JavaScript libraries installed with npm. I don't anticipate any incompatibility issues with the arm64 architecture. If there were, errors should have been evident during the arm64 build creation. However, the build proceeds without issues.
I've previously worked on CtrlX Core Virtual, building multiple snaps (amd64) that run seamlessly on the CtrlX Core Virtual environment. Nevertheless, when I attempt to use the same snap (arm64) on CtrlX Core (hardware) without altering any configurations, the snap builds successfully and installs on the real device. However, upon attempting to open it from the sidebar of CtrlX Core, a new tab is launched with no interface. Please refer to the screenshot below for more details.
01-25-2024 11:58 AM
Hello,
You don't anticipate because you're getting them for AMD64.
Please attach the log of the app 😁.
01-26-2024 05:36 AM
Hi @MauroRiboniMX
In logs i am getting this error.
/snap//x1/bin/node: 1: ELF: not found
snap.service
01/25/2024 2:18:39 PM.946ddresss: 111.11.1.150 - address 111.11.1.150: missing port in addresserror on resolving tcp addresss: 111.11.1.150 - address 111.11.1.150: missing port in addresserror on resolving tcp addresss: 111.11.1.150 -
Note: I have shared a screenshot in which I have hidden the name of the application, and the real IP has not been mentioned.
01-26-2024 08:28 AM - edited 01-26-2024 08:31 AM
Hello,
This is a classical problem with architecture incompatibility:
https://stackoverflow.com/questions/57446579/executable-says-line-1-elf-not-found-when-starts
Probably if you make a remote-build for arm64 can be tha the same code is working.
https://snapcraft.io/docs/remote-build
Because you are not cross compiling but just compiling.
Are you using the node plugin?
01-26-2024 11:35 AM
Hi @MauroRiboniMX
i am using npm plugin
09-06-2024 09:30 AM
Are there any news? Could this issue been solved?