I have written an application in python (Pys60) that records the GSM/UMTS network information (using "location" in Pys60 and Chris Berger's "elocation") and also records GPS location (using "location"), and then sends this info from my Nokia N95 via URL to my web server.
I have signed the "elocation" module and my python Script shell via "Open Signed", and everything works great. Until...
When I use Ensymble 0.28 (I have Python 2.5 in my Ubuntu machine, and I'm using Pys60 1.4.5 on my phone) I use the py2sis, doing:
ensymble.py py2sis --caps=LocalServices+ReadUserData+etc.. myapp.sis(I apply all possible CAPS allowed, basic and extended, including especially Location, Read/Write DeviceData, Read/Write UserData). I then upload it to Open-Signed On-Line.
The SIS application runs all the way thru, and even confirms it sent the data. But when I check my server, no info is received (??). When I run the .py file (exact same as used in the py2sis) in the scriptshell, it works everytime (??).
What is the SIS file doing differently from the PY? Or did I not make the SIS file correctly? I'm confused...
PS- I use MD5 also, does this need any special treatemnt in terms of "signing" or "caps", or any other hoops of fire that need to be jumped thru?
PPS- As someone new to Symbian programming, I have to say I'm really happy by the ease of use and support given, however the "signing" and "capabilities" process really makes it a case of "one step forward, two steps back" I understand the need for security, but can't the user just simply agree to allow the app these abilities themselves? Why is Symbian complicating things with the current processes?