Hello, I am following this discussion for a moment cause I have the same problem. I have tried to used TARGET_CAPABILTY but to no avail : now the phone tells me "requested application, access not granted". So I have tried to opensign my application on symbian signed but the result is the same : my application is still untrustful and can't install.
Thanks Selon Jack Wootton <[email protected]>: > Hello, > > Thank you for this information. Since I am using a production device I > assume I can create the sis file and then use > https://www.symbiansigned.com/when I need to test it? > > Kind Regards, > Jack > > On Mon, Jun 21, 2010 at 4:36 PM, <[email protected]> wrote: > > > The patching removes Location because that is not self-signable on S60 3.1 > > devices. > > > > If you are creating All-TCB dlls (or need any capability outside of the > > self-signable set), then you should supply a suitable developer certificate > > when creating the sis file, so that patching step is skipped. > > > > If you're working with any kind of prototype device, you can add your own > > root certificate to the SWI certstore. > > Device manufacturers normally do this and distribute the RND cert+key to > > all developers. > > > > For production devices, you need to get a developer certificate from > > symbian signed, and use that to sign your sis files. > > > > Set these environment variables to point to your certificate and key files > > (to sign with a single cert) > > QT_SIS_CERTIFICATE > > QT_SIS_KEY > > > > To sign with multiple certs, set > > QT_SIS_OPTIONS=-c path_to_certfile\certfile.txt > > > > [-c|certfile <file>] = The file containing certificate information > > for signing. > > The file can have several certificates, each > > specified in > > separate line. The certificate, key and > > passphrase in line > > must be ';' separated. Lines starting with > > '#' are treated > > as a comments. Also empty lines are ignored. > > The paths in > > <file> can be absolute or relative to <file>. > > -- > > Communications with Accenture or any of its group companies ("Accenture > > Group") including telephone calls and emails (including content), may be > > monitored by our systems for the purposes of security and the assessment of > > internal compliance with company policy. Accenture Group does not accept > > service by e-mail of court proceedings, other processes or formal notices > of > > any kind. > > > > Accenture means Accenture (UK) Limited (registered number 4757301), > > Accenture Technology Solutions Limited (registered number 4442596), or > > Accenture HR Services Limited (registered number 3957974), all registered > in > > England and Wales with registered addresses at 30 Fenchurch Street, London > > EC3M 3BD, as the case may be. > > > > > -----Original Message----- > > > From: [email protected] [mailto:qt-mobility- > > > [email protected]] On Behalf Of [email protected] > > > Sent: Wednesday, June 16, 2010 23:08 > > > To: [email protected]; [email protected] > > > Subject: Re: [Qt-mobility-feedback] LBS Client fault > > > > > > Hi John, > > > > > > I agree that "All -tcb" should add all of the capabilities except tcb. > > > The terminal output from the signing and patching seems to indicate > > > that all of the user capabilities except for Location were added. > > > > > > I've got no idea why that's happening, but it seems to be a problem > > > from outside of Mobility. If Location works on it's own then it looks > > > like something is going wrong with the capabilities patching for self- > > > signing - I have not idea if it's a general problem or something to do > > > with the setup of the particular system in question. > > > > > > Cheers, > > > > > > Dave > > > ________________________________________ > > > From: [email protected] [qt-mobility-feedback- > > > [email protected]] On Behalf Of ext John Kern [[email protected]] > > > Sent: Thursday, 17 June 2010 12:35 AM > > > To: [email protected] > > > Subject: Re: [Qt-mobility-feedback] LBS Client fault > > > > > > Hello, > > > > > > When we sign an app for Symbian using 'All -tcb', we want all > > > capabilities on the device except tcb. Yes, Location is part of that > > > mix but so are other capabilities (e.g., AllFiles) which can only be > > > granted by the phone manufacturer. If you take the resulting sis file > > > and install it directly on the phone(ie, do not use Qt Creator), will > > > it install? I predict it will fail. > > > > > > What if we simplify this testcase by only using the capabilities > > > required? In the code shown we only need Location which is user- > > > grantable. If you only use this capability and self-sign it, does it > > > work? > > > > > > Sincerely, > > > john > > > > > > > > > Some facts about Symbian that we are legally obliged to tell you: > > > Symbian Foundation Limited is a Company Limited by Guarantee and not > > > having Share Capital > > > We're registered in England and Wales - Companies House knows us by the > > > number 6683783 > > > Our address is 1 Boundary Row, Southwark, London SE1 8HP. > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Qt-mobility-feedback mailing list > > > [email protected] > > > http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback > > > > > > > > This message is for the designated recipient only and may contain > > privileged, proprietary, or otherwise private information. If you have > > received it in error, please notify the sender immediately and delete the > > original. Any other use of the email by you is prohibited. > > > > _______________________________________________ > > Qt-mobility-feedback mailing list > > [email protected] > > http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback > > > > > > -- > Regards > Jack > _______________________________________________ Qt-mobility-feedback mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
