|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (4) » Build tools (5) » Carbide.c++ 1.1 (4) » Carbide.c++ 1.2 (8) » Carbide.c++ 1.3.x (9) » Carbide.c++ 2.0.x (12) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (25) » General (48) » Off-topic (5) » On-device debugging (13) » Performance Investigator (2) » Product features (18) » Product releases (16) » Screencast (14) » Support (36) » Tool setup (6) » UI Designer (8) » Usability (18) » Work in Progress (14) » Write-build-debug (4) |
|
» New Remote Connections View » Terminating Multiple Processes » Agile Tuning of the Austin Team » Introduction to the workspace screencast » Adding DLLs while Debugging |
|
Subscribe to RSS feed For email notification, please click here ยป |
« Symbian Expo notes, 1/2: Tool vendor roundup | Main | Google custom searches for Symbian C++ »
Here's an interesting one... http://www.whythefuckwontmysisfileinstall.com/
Yes, you read the URL right.
Agreed, platsec stuff really is a pain the rear, and the various SIS creation mechanisms make it even harder. We're trying to ease some of the steps here, by introducing the certificate manager and platform security scanner -- and hopefully also the basic build system features of auto-signing and auto-generation of SIS files help here.
I wonder what WTFWMSFI would say of Carbide.c++'s SIS creation features? Anything missing?
Anyway, I plugged in an autogenerated SIS file of our basic apps and it seemed to behave well enough, as did TRK and the Performance Investigator agent...
Comments
Well, I'm still adding tests to it. I'm afraid I didn't get them all written in time for the smartphone show :)
I'm sure I can find something for the tool to bitch about!
Posted by: Chris Davies | October 27, 2006 03:28 AMThe error messages on the phone leave a lot to be desired.
For example:
"Constrained by the certificate" - WTF
In English "Your IMEI is not valid for this certificate" - if you think this obvious in the last month 2 developers, one R&D Manager, 4 testing guys and 2 product managers have all escalated this to me becuase my claim to fame is that I know what the error messages mean.
Likewise, starting the application does nothing error - This is normally the result of the wrong filename in the _reg or _loc file. Why can't it just say "missing registration file" when you click on the application to start it?
Or my favourite - if there is a duplicate dll or exe with the same uid and you try to install you get a cryptic error like "Install error" or something like that - Why can't it say " already exists" or even better " already exists in "
Likewise when using the emulator the RLoader really needs output more useful information about why it failed to load a certain dll or exe.
For example report that a UID is wrong
Unfortunatly these are not carbide issues :(
Posted by: Paul Todd | October 28, 2006 04:55 AMPaul, I agree -- Symbian error messages are cryptic when it comes to platform security issues. This is why I've requested from Symbian that the messages displayed during platsec issues be more descriptive (i.e. no more "error codes"). Platsec errors are going to be visible only to developers since no app will be certified with them, so might as well have descriptive and useful platsec errors/warnings -- such as, "your application is using capability X, but the certificate doesn't allow it." Now THAT would be useful!
//markus
Posted by: Markus Ahonen | October 30, 2006 08:05 AMNow that would be useful!
In the meantime Symbian has opened the devkit doc on diagnosing sis install failures which is my little secret stash of useful stuff.
Download it here - http://www3.symbian.com/faq.nsf/0/20D1DE558D34430B002571FB002052CD?OpenDocument
Posted by: Paul Todd | October 30, 2006 04:21 PMMarkus,
There is very little point complaining to Symbian about the lack of useful error messages. The install server gives plenty of information (except in one or two edge cases), the real problem is the S60 UI (and the UIQ UI too...) decides to discard all the information and give bland, non-descriptive error notes.
I'd take it up with the S60 install UI team, if I were you.
Posted by: Chris Davies | October 31, 2006 05:43 AMChris,
I probably should have been more clear about my request -- it wasn't regarding installation messages per se; rather, the messages that the device shows when it tries to access a platsec capability during runtime. These seem to be the trickiest problems to resolve so better error messages would be useful.
Agreed -- I'm not aware of where the actual problem is, Symbian or S60. Let's see what the response from Symbian is on this...
Posted by: Markus Ahonen | October 31, 2006 07:16 AM