I’m guessing that others have also noticed this but I wanted to explicitly bring this issue to the forefront so that it can hopefully be fixed or at least it won’t waste lots of time troubleshooting.
When pressing the deploy button in the SDK the application is launched in a way that never brings up the SailJail dialog, if the application is being run for the first time ever in the emulator it won’t have permissions and thus if there are file read/write actions during startup it will stall.
The solution seems to be to start the application from the menu which will result in a SailJail prompt after which subsequent starts from CLI/SDK will be fine.
@martyone
1 Like
Are you sure it is really jailed and devoid of permissions?
Apps launched this way used to be completely unjailed.
What do you have for Exec in your .desktop file?
From my side no jail has been defined yet.
Exec=sailfish-qml harbour-org.gpodder.sailfish
The error based on the console output involves writing config files and resolved after starting the app once “the normal way” so that was my explanation for it, I don’t rule out that I am missing some part of the puzzle here as to what is happening but it also seems to me that the very fact that the way the app launches when pressing the “play” button in the SDK and “true” user experience are different is also a red flag.
1 Like
Same when deploying to a device. But I’m not sure I want to change this.