NewLC - CaptureKey security capability on S60 v3 - Comments

Re: CaptureKey security capability on S60 v3

bytes — Mon, 11 Feb 2008 13:24:47 +0100

Thaks from my side too...

Its solved my problem.

-bytes

Re: CaptureKey security capability on S60 v3

johnny — Fri, 06 Oct 2006 11:36:22 +0200

Thanks a lot,
I didn't know I also had to add the needed capabilities in the mmp file. I did it and now it works fine.
Thanks.

Re: CaptureKey security capability on S60 v3

NumptyAlert — Thu, 05 Oct 2006 19:39:28 +0200

Signing hasn't really got anything to do with what capabilites your program has - these are defined in its .mmp file/s.
Signing just allows you to be able to install the software.

It doesn't matter what capabilies your certificate has got, if your program doesn't have them in the first place.

If you need SWEvent then your code has to be built with that, i.e. SWEvent has to be in the .mmp file.

Run on the emulator and then look in epocwind.out and see if you get a -46 in there. It'll tell you the reason.

Re: CaptureKey security capability on S60 v3

johnny — Thu, 05 Oct 2006 18:39:24 +0200

I've made another application to test the RWsSession::SimulateKeyEvent which is also in the SwEvent capability. The method again works fine on the emulator but crashes on the phone with the WSERV 66 panic. So the problem seems to be from signing the application. Although my developer certificate was created with the SwEvent capabillity (I checked again on the SymbianSigned site for my generated certificate capabilities, and SwEvent is present) the application doesn't seem to really have it. So is there any way to test applications with Developer Certificates or do we have to pay 350$ (or even more) for a public certificate only for testing purposes??? But then again it might be just a E50 bug. So does anyone have any ideas on how to enforce the SwEvent capability?
Thanks a lot.

CaptureKey security capability on S60 v3

johnny — Thu, 05 Oct 2006 16:53:55 +0200