[S60,9.1]IAP-SelectionDialog pops up twice

[tobias_stoeger]

Hi guys,
new OS - new features ;-)

I'm using RConnection for selecting a default IAP (or none).
The code works already fine on OS7.0s upto 8.1a.
It also works on 9.1 S60 emulator.
But on the device(V3.18 03-03-06 RM-38 Nokia 3250) the IAP-SelectionDialog pops up two times before the first connect attempt.

The code looks like:
....
if (iPrefs.IapId()==0)
{
//Our default is ECommDbDialogPrefDoNotPrompt
iPrefs.SetDialogPreference(TCommDbDialogPref(ECommDbDialogPrefPrompt));
}
iPrefs.SetDirection(ECommDbConnectionDirectionOutgoing);
// Start an Outgoing Connection with overrides
TInt err = iConnection.Start(iPrefs);
....

The sis-file is selfsigned(unprotected range), maybe thats the problem?
But the sis gets granted by user during install time and the
connectivity works fine - except the above issue.

Any ideas are very welcome.
Please help! No more time left for the s60 challenge ;-)

Thank you very much.
--
Tobias
www.OutBank.de

[tobias_stoeger]

Changed all UID3s to protected range,
created a devcert for this IMEI, but
the failure still happens :-(

Any other of you also have problems with OS9.1 and IAP selection?
--
Tobias
www.OutBank.de

[tobias_stoeger]

correction...not exactly the same behaviour...the dialog now appears only once and not twice as before :-?

--
Tobias
www.OutBank.de

[tobias_stoeger]

After signing the sis with a dev cert and ACS cert
(correct capabilities are also there) the iap selection
dialog still pops up.
If running in the emulator all seems fine.
It happens only on the device (3250).

My code works perfect for OS7.0s and OS8.1a.

So whats the trick about it?

No one outside there, who has similiar problems or
any hints how or why the the RConnection behavior
under OS9.1 is different/faulty ?

Any comments are very welcome.

Thank you guys.
--
Tobias
www.OutBank.de

[tobias_stoeger]

Here are the results of the last 3 days:
1.
There has been a change in the API of
RSocket
and
RHostResolver

Now it is mandatory to set the RConnection if one want to
use a dedicated IAP! Without, it will work in the emulator
but not on the device.

SDK doc tells you now:
"NOTE: if you are starting connections via the RConnection or RSubConnection APIs, then you *must* use the RSocket::Open(..., RConnection&) or RSocket::Open(..., RSubConnection&) methods as appropriate to ensure that sockets are routed over the correct connection."

So in my case it looks like:
....
User::LeaveIfError(iResolver.Open(
CDefaultConnection::Instance().SocketServ(),
KAfInet,KProtocolInetUdp,
CDefaultConnection::Instance().Connection() //Mandatory for OS9.1
));
....
User::LeaveIfError(iSocket.Open(
CDefaultConnection::Instance().SocketServ(),
KAfInet, KSockStream, KProtocolInetTcp,
CDefaultConnection::Instance().Connection() //Mandatory for OS9.1
));


and

2.
It seems like user granted applications (usually selfsigned ones)
cannot prevent the IAP-SelectionDialog anymore.(But maybe this is
a customizable issue for each device/provider.)

Thank you Nokia, thank you Symbian!
--
Tobias
www.OutBank.de

[mike.b]

Same for me.
Actually, I first enumerate IAP's and let user select one.
However, whenever connection starts, using RConnection, a dialog is displayed for choosing access point.
Why??? it worked without dialog in previous Symbian IS. I've let user select preferred access point, so why bother him with another dialog before every connection?

Maybe it can be solved somehow, yet I didn't find how.

[mike.b]

Update:
I found problem in my application, and now it's able to connect to internet without any dialog!!! Problem solved!!

The problem was that altough I called RSocket::Open with intialized RConnection, I forgot do the same for RHostResolver::Open, so this was RHostResolver in my app that caused dialog to pop up.

And my app has unprotected ID.

So head up tobias, it'll work without dialog

[tobias_stoeger]

Hello Mike,
does it already run with unprotected UID on the device or only emulator.
And if, which device?
cu
Tobias

[mike.b]

Runs fine with Axxxxxxx UID (unprotected), with self-signed sis file, also on device Nokia N80.

[bytes]

But my issue is

Pop-up is not coming while establishing connection or till connection is OK., but when connection goes down, (but still sockets are in use, like recvfrom etc.,) pop-up is coming up. How to prevent this.

I have interlinked, RSocket and RConnection, so that sokcets will use my connection.

I want to re-connect to another AP without pop-up (as soon as I find disconnection).

-bytes

Update:
I found problem in my application, and now it's able to connect to internet without any dialog!!! Problem solved!!

The problem was that altough I called RSocket::Open with intialized RConnection, I forgot do the same for RHostResolver::Open, so this was RHostResolver in my app that caused dialog to pop up.

And my app has unprotected ID.

So head up tobias, it'll work without dialog

[wizard_hu_]

You may check if the notification methods of RConnection can help or not.

[bytes]

Hi,

Thanks for your reply.

My primary concern is to prevent WiFi pop-up.

Even if I find the connection down progress, how can I prevent the pop-up , before establishing a connection.

As for as I am aware, we can't start a new connection, unless the current one completely down or dis-connected.

BR
bytes

You may check if the notification methods of RConnection can help or not.

[wizard_hu_]

Even if I find the connection down progress, how can I prevent the pop-up , before establishing a connection.

I am not sure about this particular case, but if you do not use RConnection, "inbound" or "passive" networking (like RecvFrom, Accept) does not cause the IAP selection dialog to pop up. While Connect, SendTo does. So the thing I would try is still using the notification on link going down, and if this notification comes, I would try Cancel-ing everything on the affected RSockets, and Close-ing them. Then a silent re-Start of RConnection might help (perhaps it also needs a Close, re-Open), I do not know in fact.

[bytes]

Hi,

Yes, u r correct. Only connect and sendto will does this.
But unfortunately I am using multi threading; and 'sendto' is in different threads. Though I catch notification properly, by the time I notified to another thread, sendto may be in progress and pop-up will still arise.

I am not sure about this particular case, but if you do not use RConnection, "inbound" or "passive" networking (like RecvFrom, Accept) does not cause the IAP selection dialog to pop up. While Connect, SendTo does. So the thing I would try is still using the notification on link going down, and if this notification comes, I would try Cancel-ing everything on the affected RSockets, and Close-ing them. Then a silent re-Start of RConnection might help (perhaps it also needs a Close, re-Open), I do not know in fact.

[wizard_hu_]

I am not sure about your configuration:
- if you have succeeded in sharing an RConnection between threads (it can be possible, I have not tried), you should be able to get the notifications in the thread your SendTo resides
- if you have a separate RConnection for each thread, you should be able to get the notifications more obviously
- if you do not use RConnection in the thread your SendTo resides, it should regularly ask about an IAP unless it has been specified otherwise in the Settings application (by the user).