Revision history [back]

Hi sailors!

Lately I've been working on with Sailfish apps and SDK was working great just before updating to version 3.0. So my issue is that unfortunately now after adding my Xperia XA2 Dual-Sim to QtCreator as a device, deploying a rpm package faces an error:

Fatal: No key for user 'nemo' on 'Sailfish OS Emulator 3.2.1.20' given in devices.xml (rsync '/etc/mersdk/share//nemo')
13:30:55: The process "C:\SailfishOS\settings\SailfishSDK\libsfdk\build-target-tools\Sailfish OS Build Engine\SailfishOS-3.2.1.20-i486\deploy.cmd" exited with code 1.

After this has occurred I'm not even able to deploy rpm for the emulator since it returns the same error code. Not even deleting the device, as it states that something is wrong in devices.xml, is helping. I'm not sure what key for nemo it's trying to find or what it's trying to do. I've tried to generate some new keys and adding the device again etc. I know rsync is not available as stated in test connection but it wasn't a problem until now.

Nevertheless, what I have found out is that this issue could be related to MerSDK not mounting some files correctly or the same issue with not being able to connect Sailfish Emulator/Build Engine since they refuse to connect (take a look at this https://together.jolla.com/question/220616/connect-to-emulator-on-windows-10-fails-with-permission-denied/). I have also noted that re-installing SDK and VirtualBox will let me to deploy rpm for emulator again but right after adding a new device this issue occurs both on emulator and the device.

I have to admit that I'm really newbie when it comes to Sailfish app development so this issue might be just very trivial but please feel free to help me with it. I'm just confused why it started to happen right after updating to SDK 3.0 and not before that.

To add some details, so I'm running on the latest SDK 3.0 and VirtualBox 6.1 on Windows 10 Home 64-bit. My XA2 (H4113) is running on Sailfish 3.2.1.20 Nuuksio.

Cheers!

Hi sailors!

Lately I've been working on with Sailfish apps and SDK was working great just before updating to version 3.0. So my issue is that unfortunately now after adding my Xperia XA2 Dual-Sim to QtCreator as a device, deploying a rpm package faces an error:

Fatal: No key for user 'nemo' on 'Sailfish OS Emulator 3.2.1.20' given in devices.xml (rsync '/etc/mersdk/share//nemo')
13:30:55: The process "C:\SailfishOS\settings\SailfishSDK\libsfdk\build-target-tools\Sailfish OS Build Engine\SailfishOS-3.2.1.20-i486\deploy.cmd" exited with code 1.

After this has occurred I'm not even able to deploy rpm for the emulator since it returns the same error code. Not even deleting the device, as it states that something is wrong in devices.xml, is helping. I'm not sure what key for nemo it's trying to find or what it's trying to do. I've tried to generate some new keys and adding the device again etc. I know rsync is not available as stated in test connection but it wasn't a problem until now.

Nevertheless, what I have found out is that this issue could be related to MerSDK not mounting some files correctly or the same issue with not being able to connect Sailfish Emulator/Build Engine since they refuse to connect (take a look at this https://together.jolla.com/question/220616/connect-to-emulator-on-windows-10-fails-with-permission-denied/). I have also noted that re-installing SDK and VirtualBox will let me to deploy rpm for emulator again but right after adding a new device this issue occurs both on emulator and the device.

I have to admit that I'm really newbie when it comes to Sailfish app development so this issue might be just very trivial but please feel free to help me with it. I'm just confused why it started to happen right after updating to SDK 3.0 and not before that.

To add some details, so I'm running on the latest SDK 3.0 and VirtualBox 6.1 on Windows 10 Home 64-bit. My XA2 (H4113) is running on Sailfish 3.2.1.20 Nuuksio. And to add I can reproduce this on my desktop and laptop both running under the same specs.

Cheers!