Sis deployment failure shows no useful error message

One of the most common errors developers are experiencing when developing with Symbian devices is:
"Could not install from package C:\xxx.sis on device: General OS-related error"
This error message is shown when deploying to the Symbian-device through the TRK agent on the phone. The message doesn't tell anything about the problem and provides no starting point on where to look for solutions, causing confusion.

Instead, Qt Creator should show the error message from the installer, as also explained here:
http://blogs.forum.nokia.com/blog/lucian-tomutas-forum-nokia-blog/2009/09/29/the-ultimate-software-installer-debug-guide

If none of these common and easy-to-detect failures described below are the case, a link to pages like this:
http://developer.symbian.org/wiki/index.php/Troubleshoot_install_errors
Would be helpful. Should also be integrated into Qt Creator help if possible.

The following common problems can cause this deployment error; plus suggestions on what can be done to help the developer / prevent the error beforehand :

• Invalid certificate: check which capabilities are required by the app. Inform the user if a self-signed certificate is not enough for the capabilities he declared and suggest using a developer certificate.

• Wrong date / time of device or certificate: check if device date & time is within validity period of the certificate. Inform user to correct time on PC and device if a mismatch is detected and make sure certificate is re-created for next deployment.

• Check if Qt is installed on the device in the correct version. If not and deployment fails, instruct to install or offer to install.

• Check if Qt Mobility is installed on the device if required by the project. If not and deployment fails, instruct to install or offer to install.

• If app with same UID is already installed and upgrade failure: suggest to remove old app first. Can happen if certificate type of app changed, if other app on the device uses same UID or if the UID of the app was changed (e.g., before deployment when switching from developer 0xE... UID to release 0x2... UID).

• Is app UID in the correct range? Should usually be 0xE... or 0x2...