Unable to deploy to phone: 'Xperia XA2 WIFI - Dual SIM (ARM)' is not a known device

Platform Development
#21

I’m not using Docker, I’m using Virtual box. The key name and location were just the default. I didn’t choose anything other than to create one ~/.ssh/qtc_id

#22

Just give a different name for the new key: in the SSK Key Configuration dialog (the one which opens after clicking “Create New Key Pair”), click “Browse”, and write a different name there.

#23

I have purged the keys from my computer and my device, created new keys and deployed them successfully, and even the connection test works fine (as does ssh from command line), but I still can’t deploy any apps to my bloody device :face_with_symbols_over_mouth:

What did I miss? It used to work at least a few SDK releases back…

#24

That does make a new key.
tldr: didn’t help, waiting to see if the next release works…

Some notes: The upload key button is not ungreyed after making the new key like it should be.
Note that upload only works if I have manually ssh’d in first - The dialog should say this, and tell you how

ssh nemo@192.168.1.74

The new key file tests OK

ssh -i .ssh/xa_id nemo@192.168.1.74

I then rename the new device configuration from “Xperia XA2 WIFI - Dual SIM (ARM)2” to “Xperia XA2 - WIFI”
and finish the new device.

I go to projects and select the RUN configuration, and change the run configuration to add the new device. Except it is showing the before-edited device name “Xperia XA2 WIFI - Dual SIM (ARM)2” , so I select that.

I try to run. Then I see in compile log window, that deploy.cmd was called with the previous device “Xperia XA2 WIFI - Dual SIM (ARM)” which I have already deleted.

I have to go back a forth a couple of times until everything is showing the new name correctly.

1 Like
#25

Thanks for digging that much out. I’ll test the behavior, too.

#26

This is old, but here is a possible explanation - this happens to me just now.

  1. My env was OK and my testing app was OK. Then I renamed my testing app by adding prefix “harbour-” everywhere, because I want it to be publishable. After this step, the app deployed, but no icon on the device and not able to start it without IDE.
  2. Looking through documentation I found sfdk check command to validate packaging.
  3. I do not know how to start this from IDE, thus I turned to terminal and try to locate command sfdk on the disk.
  4. I found the command and wrote “sfdk --version” to test. BUT, I forget that I was root in the terminal (because I am used to do locate as root). This was the source of the problem. sdfk did not simple report version but did much more, I see some error lines about not-existing configs and one of the side effect was that file vmshare/devices.xml was recreated and CHANGED owner to root.
  5. IDE was not able to write to vmshare/devices.xml anymore, so recreating device in IDE was unsuccessfull. After change owner of vmshare/devices.xml back to normal user, recreating device in IDE is OK and I am back into my work. Stil with intitial problem of bad rpm deployment :frowning:

EDIT:

My initial problem solved. Using sfdk check -s harbour myapp.rpm (as correct user) I found out that I forget to add prefix “harbour-” to the Icon and Exec settings in .desktop file.

1 Like