Creator looks into a phantom shadow build directory when trying to launch a .sis file.
That happens under the following conditions.

• Open a project which has Desktop and Symbian target and where the Desktop target was active last time before closing the project
• Immediately switch to Symbian target and build

In the following example, I have a project Solitaire.pro in the directory K:/MyProjects/Solitaire. The output looks like this:

Processing Solitaire_release-armv6.pkg...
Created Solitaire_unsigned.sis.
Successfully created signed package Solitaire.sis for release-armv6 using certificate: Self Signed!
make[1]: Leaving directory `K:/MyProjects/Solitaire'
The process "K:\epoc32\tools\make.exe" exited normally.
Failed to find package 'K:/MyProjects/Solitaire-build-desktop/Solitaire.sis': Package file not found

Creator looks into K:/MyProjects/Solitaire-build-desktop for the .sis file, which is wrong. First of all, Symbian does not support shadow builds anyways, and second Symbian is not "desktop"

It also happens thie other way around. Although the desktop binary is shadow built, Creator tries to run it from the source directory.

I believe this is timing related. When switching and quickly launching the app, this is reproducable.