Details
-
Bug
-
Resolution: Invalid
-
Not Evaluated
-
None
-
4.7.3
-
None
Description
0. Have a version of your project build already installed on a Symbian 3 device
1. Configure your project so that signed smart installer is generated
2. Connect device to PC and hit Run. It starts building, packaging, signing, transfer to the device and:
Expected
3. Smart Installer is installed
4. Smart Installer installs the new build of your app
5. Your app is started and you can e.g. debug it (if you hit Debug and not just Run at step 2)
Actual
3. Smart installer is installed
4A. Smart installer starts installing the new build of your app
4B. But in parallel QtCreator thinks all installation was completed and starts what it believes is a correct version of a correct binary. In fact it is the old build of your app that wasn't replaced with a new binary yet
Not that critical, but annoying at the stages of development when you start working with the builds wrapped with SmartInstaller often. Also it is quite confusing the first time you see that. If you don't stare at the mobile display all the time, it's easy to miss the fact you are running the old code.
Not sure if this bug is relevant for Maemo and Harmattan. I guess it is true for all the platforms that utilize Smart Installer in this or that way.