RHttpDownloadMgr download sisx works, but cannot install

[bill-wang]

Hi, Buddies

I use RHttpDownloadMgr to download a new version of my applcation at fcuksports.com, then I need to install on the phone(I use N97mini for test), then it will hanged the at the install progress bar.

Do any body knows the issue?

The step as:

1, When application start, it check the server, there is new version of fcuksports.
2, Down the application with RHttpDownloadMgr, and save it to local driver.
3, after the download successfully, then automation to install the new version.
4. System shows it need to close the application.
5, then close the application to install the newer one.
6, the phone is hanged with the install progress one.


Does this is because the installer is invoked by the old one, so the new one cannot install? Or do anybody know how to fix it?

Thank you!

Kind Regards
Bill

[wizard_hu_]

Similar issues are discussed already, just the search engine is a bit dizzy since the new installment of the Forum. Since the installer is related to the process which launches it, generally you can not update an executable via launching the installer from itself. A possible workaround is to temporarily deploy a different application for doing the update. Then you can start it, exit from your own app, and the update process should work.

[bill-wang]

Thank you!

I got example code for this

and I meet another problem that I use a another application(let's call it update.exe) to run installer, but its show some application need close for install, then I click yes, but now the first application and the update.exe are close both, and still hanged at the installer. The code as:


_LIT(KMyExeFile,"updateexe.exe");


TThreadId app_threadid;
CApaCommandLine* cmdLine;
cmdLine=CApaCommandLine::NewLC();
cmdLine->SetExecutableNameL(KMyExeFile);
cmdLine->SetCommandL( EApaCommandRun );
RApaLsSession ls;
User::LeaveIfError(ls.Connect());
TInt err=ls.StartApp(*cmdLine);
ls.Close();
CleanupStack::PopAndDestroy(); // cmdLine


This is OK in invoke updateexe.exe to start install.


And the following code is updateexe.exe:

LOCAL_C void MainL()
{


SwiUI::RSWInstLauncher iLauncher;
SwiUI::TInstallOptions iOptions;
SwiUI::TInstallOptionsPckg iOptionsPckg;
_LIT(filename, "c:\\data\\fcuksports_s60v5.sisx");
TInt err = iLauncher.Connect();

CAOSync* waiter = CAOSync::NewL();

CleanupStack::PushL( waiter );

TBufC<50> FName(filename);

iLauncher.Install(waiter->iStatus,FName,iOptionsPckg);

waiter->Execute();

CleanupStack::PopAndDestroy( waiter );

}

LOCAL_C void DoStartL()
{
// Create active scheduler (to run active objects)
CActiveScheduler* scheduler = new (ELeave) CActiveScheduler();
CleanupStack::PushL(scheduler);
CActiveScheduler::Install(scheduler);

MainL();

// Delete active scheduler
CleanupStack::PopAndDestroy(scheduler);
}

// Global Functions

GLDEF_C TInt E32Main()
{
// Create cleanup stack
__UHEAP_MARK;
CTrapCleanup* cleanup = CTrapCleanup::New();


// Run application code inside TRAP harness, wait keypress when terminated
TRAPD(mainError, DoStartL());

delete cleanup;
__UHEAP_MARKEND;
return KErrNone;
}




this is the CAOSync code:
CAOSync* CAOSync::NewL()
{
CAOSync* self = new(ELeave) CAOSync();
CleanupStack::PushL(self);
self->ConstructL();
CleanupStack::Pop();
return self;
}

CAOSync::~CAOSync()
{
Cancel();
delete iWait;
}

CAOSync::CAOSync() : CActive(CActive::EPriorityStandard)
{
}

void CAOSync::ConstructL()
{
iWait = new(ELeave) CActiveSchedulerWait();
CActiveScheduler::Add(this);
}


void CAOSync::Execute()
{
SetActive();
iWait->Start();
}


void CAOSync:oCancel()
{
iWait->AsyncStop();
}

void CAOSync::RunL()
{
iWait->AsyncStop();
}


Does this has problem? or issue?


Thank you!

[bill-wang]

hey, do anybody know the issue?

[kamalakshan]

You need to close your application first and then do the update with update.exe.

[wizard_hu_]

update.exe has to be installed separately
- it can not be part of the main application package
- it can not be embedded in in the main application package
- there should be a completely standalone update.sisx, deployed as any other file (the .exe, the .rsc-s) - as a first try I would put it on a public location, however the installer can access your private folder too
- when you want the update to happen, the main application can install update.sisx, execute update.exe, and as a completely independent installation, update.exe will not get shut down when it installs the updated main application.
Of course it is faster to check if update.exe can be launched, and do the extra installation only if it is necessary (so the first time).