FTP problem: works on emulator, but fails on device

[jumartinelli]

Hi,
I am on an Univesity project that is a software that communicates through wifi connection with an FTP Server (FileZilla Server) running on my desktop computer. The program runs perfectly on emulator, but on the phone release compilation the application starts on the phone, but disconnects from wireless as soon as it starts, the server receives the message requesting a connection, but can’t return the answer as the connection already broke down.
When trying to debug with TRK, after downloading the application to the handset, carbide shows a message informing that it couldn’t be launched because of some missing libraries.
I already have the capabilities for network control and network services. It works fine in the emulator. Any ideas about this behavior? Could it be that my cert key it’s not “capable” of signing these 2 capabilities?
I’m using Nokia 5800.

void CFtpHandler::sendConnect(RSocket *sock, TRequestStatus status, TUint8 *cleanupCount){
RBuf8 response;
	TSockXfrLength len;

	TBuf8<5> cmd;
	cmd.Append(_L("CONN")); //store the command sent
	// Open socket server session	
	CleanupClosePushL(ss);
	(*cleanupCount)++;
	User::LeaveIfError(ss.Connect());
	// Open connection on the socket server session
	CleanupClosePushL(conn);
	(*cleanupCount)++; //counts the objects inserted on cleanup stack
	
	// Start the default connection
	User::LeaveIfError(conn.Open(ss));	
	conn.Start(status);
	// Wait for the connection to start
	User::WaitForRequest(status);
	// Check if Start succeed
	User::LeaveIfError(status.Int());		
	// Open TCP socket on the started connection
	User::LeaveIfError(
sock->Open(ss, KAfInet, KSockStream, KProtocolInetTcp, conn));
		
	// connect to the remote ftp server.
	TInetAddr remoteAddr(INET_ADDR(192, 168, 1, 180), 21);
	sock->Connect(remoteAddr, status);	
		
	response.CreateL(512);
	response.CleanupClosePushL();	
	sock.RecvOneOrMore(response,0,status,len);		
	User::WaitForRequest(status);		
	User::LeaveIfError(status.Int());
}

[wizard_hu_]

Do you have the proper certificate for using NetworkControl? Besides that you do not need it in fact, consider removing. NetworkServices is enough, and it can be used with any kind of signing, including self-signed.
RecvOneOrMore attempts to complete as soon as it can, but as its name indicates, it is going to receive at least one byte. So you may want to check that response, most likely it contains some part of the expected response.
Otherwise your code leaks everything it can. And passing TRequestStatus by value is also questionable.

[jumartinelli]

Thanks for the tips wizard_hu_.
It turns out my problem was temporization. As I was using assynchronous functions, I forgot to put some wait for request after them.
So, it worked on emulator because of breakpoints and things like that which slows down the application. And on device the time was more strict, in a device release version it didn't work.