Hi Chris,
You are trying to host a webserver on port 8080 from your custom snap? If you could provide some more information on this point (error messages, build logs etc.) I could better help troubleshoot.
How are you writing log messages in your snap? There are a number of ways to do this. In C++, standard library control output (std::cout) will write a system message that can be toggled in the ctrlX diagnostic logbook (settings->show system messages).
See this example on more configurable logbook output using the sd-journal library: CPP Diagnostic Logbook
If messages are not being written to the ctrlX diagnostic logbook, you will need an SSH connection to debug. On a virtual CORE, this is enabled by default. If you'd like SSH on a physical CORE, you'll need to request a system user assertion file. (See topic "SSH to the core disabled")
Some useful debug/log tools:
- snap logs snap-name
- systemctl status snap-service
- journactl
It's also useful to build a snap for amd and run it in your app build environment before building for arm. This way you can debug all non-architecture specific issues prior to testing on the physical device.
