Sailfish SDK 3.1.7 problems

asked 2020-05-08 13:49:21 +0200

Spam Hunter

11677 ●187 ●289 ●324

updated 2020-05-13 09:50:24 +0200

jovirkku

23703 ●213 ●311 ●247

moderator

Where to start?, I know we should only post one question per problem, so I'll make this my first post of many to come.

Clearly, things have changed in the latest SDK, my main problem is this, I have to build my apps 3 or more times before they appear in the emulator, generally, I get the error "could not deploy", so i build again (Kit: i486.rpm; Debug; Deploy as RPM), in most cases, LiveBench fails to start, needs to be closed and opened again, other times, the entire SDK window flashes around 7 times before the "Start LiveBench" dialog shows, then it opens but LiveBench stays offline, so I close it again and 3rd time is the charm, just like having to rebuild the app 3 times or more, why is this happening?,

ADDED: Here's a link to a video of the problem; https://youtu.be/m36BXHkX4bg

Windows 7 64bit ultimate; SDK 3.1.7

Rokua 3.3.0.16 on Jolla1 (not tested yet with SDK)

Please shed some light on this for me, it's driving me up the wall!

ADDITIONAL: @martyone, it's my fault that my harbour-nationalrail app would not build, somehow I had removed the app icons from icons/86x86 folder, I reinstated them and the app now builds, even though it takes 3 times to build this/any app.

answered 2020-05-11 10:22:40 +0200

martyone
1843 ●16 ●39 ●43

moderator

updated 2020-05-12 09:45:31 +0200

The emulator takes long time to fully start up, which is the most likely direct reason for the first deployment failure. The second deployment failure may be additionally caused by the first failure ended in some intermediate state, waiting for timeout on the emulator side.

I believe starting the emulator manually well in advance will fix it.

An improvement to emulator startup synchronization has been integrated recently and will be included in the next SDK release.

edit flag offensive delete publish link

Comments

you've said as much before, my machine is not short of resources so I refute your comment. I have 16GB RAM and Intel i7 - 2.2ghz CPU.

I had none of these problems with the previous SDK, so I don;t believe my pc is at fault here.

Spam Hunter ( 2020-05-11 10:25:53 +0200 )edit

According to your video it takes about 45 seconds until the lock screen appears. On my machine it takes less than 30 seconds. This is enough to explain why you reproduce it while I don't. It is an issue on the SDK side that it does not synchronize with emulator startup well, and as I wrote this issue has been already addressed and a fix will be included in next release. Please try starting the emulator manually in advance as I suggested.

martyone ( 2020-05-12 10:06:56 +0200 )edit

Thanks @martyone, you are correct, starting the emulator early means all/any of my projects build the first go.

Please excuse my tone, I did not fully digest your original reply regarding improvement of emulator start up in the next SDK release. I didn't realise how frustrated I've become with being on lockdown for the last 2 months, Spain (yesterday, May 11th) has only just started relaxing rules on going outside.

Spam Hunter ( 2020-05-12 10:42:09 +0200 )edit

Sailfish SDK 3.1.7 problems

1 Answer

Comments

Question tools

Stats

Related questions

Sailfish SDK 3.1.7 problems

1 Answer

Comments

Question tools

Public thread

Stats

Related questions