|
|
Rank: Advanced Member
Groups: Member
Joined: 4/15/2009
Posts: 61
Location: Bavaria
|
HI all,
does anyone else experience problems currently with m programs which have been packaed as SIS with MakeSIS here, for S60 5th edition?
My testers complain that on S60 5th my program simply won't start anymore. Installation runs fine, icon appears, but when tapping the icon, nothing happens.
I have verified that it is not my code which causes this problem, by recompiling and MakeSIS-ing an older version of my code which ran well before. I use the same MEX file as input for MakeSIS, as well as the same icon and the same documents-dir zip file as before. But the newly generated SIS file shows the problem. Program not startable.
No error message, no crash. Simply doesn't start.
Any pointers on where to look for the root cause (assuming it is not a problem with MakeSIS itself on the airbit server)?
It's really strange.
Thanks!
Daniel
Sony Ericsson M600i (UIQ3)
Nokia E50 (S60 3rd edition)
|
|
Rank: Advanced Member
Groups: Member
Joined: 4/15/2009
Posts: 61
Location: Bavaria
|
Addition:
S60 3rd is also affected by this problem!
Sony Ericsson M600i (UIQ3)
Nokia E50 (S60 3rd edition)
|
|
Rank: Advanced Member
Groups: Member
Joined: 6/3/2009
Posts: 37
Location: Italy
|
Hi, I had the same problem but afer many tests I understund why: my problem was that I always put "dynamic" when I compiled the .sis file, but I have to put "static" to make it work correctely.
I'm sorry for my english and I hope you will manage to solve your problem.
ρѕρ & gт-ι8910 н∂ нα¢кє∂
|
|
Rank: Administration
Groups: Administration
, Member
Joined: 4/3/2008
Posts: 105
Location: Herrliberg/Switzerland
|
This was not a real problem. daniel3000 used static session links to the mex2sis ("Make SIS") Web-page. Since these sessions where created before release 3.05 it resulted in a version mismatch - this is, roughly spoken, the reason.
Please do not longer use your static session links, if there was created prior to release 3.05!
|
|
Rank: Advanced Member
Groups: Member
Joined: 4/15/2009
Posts: 61
Location: Bavaria
|
Hi all,
the problem was solved by me upgradeing m-Shell on my phone to the latest version 3.05.
Without knowing the exact reason for the problem that my S60 SISes (not the UIQ ones) installed applications which wouldn't start when the icon is clicked, I can say at least, that with having consistent versions across your phone and on the airbit server, this problem should not be occur anymore.
I didn't use static session links or something. I just tried to compile / pack an MEX created with m-Shell 3.04 on the phone by MakeSIS (after version 3.05 was out).
Daniel
Sony Ericsson M600i (UIQ3)
Nokia E50 (S60 3rd edition)
|
|
Rank: Advanced Member
Groups: Member
Joined: 10/1/2008
Posts: 62
Location: Turkey
|
I guess I have the same problem for my all mShell applications which were compiled with older versions of mShell. None of them works now on my s60v2 device (6630) I also tried a new script compilation and it had the same problem. So what should i do to solve this problem?
My applications:CepTeam - ShutDownMySkin v1.0Shut Down Mac Mode
|
|
Rank: Advanced Member
Groups: Member
Joined: 4/15/2009
Posts: 61
Location: Bavaria
|
Hi TheOne,
if you install the latest mShell on your phone (3.05), and then recompile your scripts with that new version, the problem should be solved (according to my experience).
Daniel
Sony Ericsson M600i (UIQ3)
Nokia E50 (S60 3rd edition)
|
|
Rank: Advanced Member
Groups: Member
Joined: 10/22/2007
Posts: 30
Location: philippines
|
I also experience this bug. Im trying to download the latest version and HOPEFUlly recompile my mex file.
By the way. Thanks to the Mshell team for doing a well job.
Thank you very much.
|
|
Rank: Advanced Member
Groups: Member
Joined: 10/1/2008
Posts: 62
Location: Turkey
|
hi daniel3000 yes maybe you are right but I have another scripts which are already compiled and i don't have .m file of them. What should i do then :S?
My applications:CepTeam - ShutDownMySkin v1.0Shut Down Mac Mode
|
|
Rank: Administration
Groups: Administration
, Member
Joined: 4/3/2008
Posts: 105
Location: Herrliberg/Switzerland
|
We have investigated mex2sis carefully but we can't see any reason for the reported behavior. Anyway, its true we had also one app, which did not start in standalone version. Then we mex2sised the app again, with a new session, and it worked. There must be a subtle problem. If everything fails, use this link to our internal mex2sis facility, on this installation we saw no problem so far.
|
|
|
Guest |
