sysinfo capabilities required?

[iemorgan]

I added a call to sysinfo.ring_type() to my program (to figure out if I'm in silent profile or not), and now the program just crashes at startup when packaged in my own SIS with full devcert capabilities.

If I run the script via the script shell, it works fine.

Oh yeah. The call to sysinfo.ring_type() is not called immediately when the program starts up. It's burried in a function that is only called later on. Just the fact that it _exists_ in the program anywhere causes the crash at startup.

Pys60 v1.4.0

There seems to be a HUGE GAPING HOLE in the pys60 documentation, namely how on earth are we supposed to know what capabilities are required for each function/method call? And worse, the program just crashes and returns to the Menu. How are some people reporting that they get a KERRPermissionDenied or such messages?? It's almost impossible to debug a program by changing a single line, repackaging, uploading to the phone, re-installing, and trying to run it again, ad infinitum.

What capability could sysinfo be requiring that is not included in LocalServices, Location, NetworkServices, PowerMgmt, ProtServ, ReadUserData, SurroundingsDD, SWEvent, UserEnvironment, WriteUserData, ReadDeviceData, TrustedUI, WriteDeviceData ?

[lfd]

Hey iemorgan,

http://www.lfdm.net/thesis/index.php...d-capabilities

Try with the selfsigned application at first and if it does not work then go to an unsigned version that you will need to sign with your own developer certificate.

LFD

[iemorgan]

I did that. When devcert signed version failed, I tried a self-signed version and it still failed. I tried devcert again, with more limited capabilities but it would fail to install. Once enough theoretical capabilities have been granted that the app installs, it will crash on startup. But the same script run via the script shell works fine. I'm stumped.

[iemorgan]

OK, now I am flabbergasted. BUG in Ensymble py2sis?!

This generates an app that crashes on startup:

ensymble_python2.3-0.23.py py2sis --icon=smsremind_icon_plain.svg \
--shortcaption='SMSRemind' --caption='SMS Remind' --appname='SMS Remind' \
--cert=../symbian-devcert.cer --privkey=../symbian-devcert.key --verbose \
--caps=\
LocalServices+\
Location+\
NetworkServices+\
PowerMgmt+\
ProtServ+\
ReadUserData+\
SurroundingsDD+\
SWEvent+\
UserEnvironment+\
WriteUserData+\
ReadDeviceData+\
TrustedUI+\
WriteDeviceData \
smsremind.py

This works: (!)

ensymble_python2.3-0.23.py py2sis --icon=smsremind_icon_plain.svg \
--shortcaption='SMSRemind' --caption='SMS Remind' --appname='SMS Remind' \
--cert=../symbian-devcert.cer --privkey=../symbian-devcert.key --verbose \
--caps=\
LocalServices+\
Location+\
NetworkServices+\
PowerMgmt+\
ProtServ+\
ReadDeviceData+\
ReadUserData+\  
SurroundingsDD+\
SwEvent+\  
TrustedUI+\
UserEnvironment+\
WriteDeviceData+\
WriteUserData \
smsremind.py

Changing the order of the caps is the only difference!!! Is Symbian PlatSec really that broken, or is this a bug in Ensymble py2sis?

[jethro.fn]

OK, now I am flabbergasted. BUG in Ensymble py2sis?!

...

Changing the order of the caps is the only difference!!! Is Symbian PlatSec really that broken, or is this a bug in Ensymble py2sis?

That's interesting. What capability bitmasks Ensymble prints in each case (the line with "Capabilities 0xNNNN")?

Anyway, the script shell environment is different from standalone programs. See my post in this thread for a troubleshooting aid, an exception harness around your program: http://discussion.forum.nokia.com/fo...ad.php?t=99623