IBC doesn't click some dialogs (they are changed in new IB Gateway)

[pps83]

Not sure if IBC cares about it, but I did have some boxes show up and not clicked. It appears that there was code to click them, but it didn't work because these boxes were updated in ibgw. See the fixes:

Recognize Connection to server failed text when it's not in a JLabel

Recognize Gateway's Exit Session Setting countdown as auto-restart confirmation

[rlktradewright]

Well I'm not sure that IBC ever cares about anything, but i certainly care.

I was just looking at the auto-restart confirmation bit of this, and testing the current code agaoinst Gateway 10.47 worked fine. So please can you tell me which Gateway or TWS version you had the problem with?

[pps83]

Well I'm not sure that IBC ever cares about anything, but i certainly care.

I was just looking at the auto-restart confirmation bit of this, and testing the current code agaoinst Gateway 10.47 worked fine. So please can you tell me which Gateway or TWS version you had the problem with?

I use latest IB GW. These boxes were visible when I was testing. I took screenshot and asked claude to fix it, and he said these were supposed to be handled in IBC code (and perhaps stopped working after change on ibgw side). After these fixes it was handled as expected. To verify, make it auto restart 2-3 mins from your local time and see count down dialog show up. If [you apply the fix](Recognize Gateway's Exit Session Setting countdown as auto-restart confirmation) and retry, you'll see the dialog is auto dismissed by IBC as it was originally made to handle the dialog. The other issue with broken sock happens when testing flaky connection. If the dialog shows up it basically fails completely: nothing clicks it, it doesn't try to restart. After clicking it manually it simply returns to login screen. Basically complete failure happens with flaky network - if no outside watcher (automated or not) is made to kill/restart it then it will block ibgw from working completely

[rlktradewright]

I repeat, which version? Mine is 10.45.1g May 27. And it goes through the countdown and restarts with no problem.

That's the WIndows version. I'll try it later with the Linux x64 and ARM versions, though they should all behave exactly the same way.

[pps83]

Win10/Win11 ibgw 10.47.1c

[rlktradewright]

I'm an idiot! It's official!...

10.45 is not, of course, the latest version,. Apologies for that.

So I used 10.47.1d, Jun 2, 2026 4:30:40 PM. But that still worked ok.

Perhaps they've fixed the problem?

[pps83]

I don't know if that was a problem in ibgw and if that's changed, it definitely had that count down show up and after the fix and java rebuild it got auto dismissed by ibc as intended.

I can take your unmodified IBC and quickly retry to confirm if the problem exists, but I highly doubt it anything changed there.

[rlktradewright]

I don't doubt that there was a genuine problem that you hit, and that your fix did inedeed fix it.

I'd be willing to bet that it will still be there in the Gateway version you were using, because IBKR don't fix bugs in released versions. They just fix the bug and bump up the version number, and expect users to notice that a new version is available (that's why it's so important to regularly check for new versions, for both the 'stable' and 'latest' versions.

I've just realised I haven't tried the flaky connection aspect. I'll give it a go.

[rlktradewright]

No problems when I disconnected my router, just 'No internet connection' messages.

I tried it on my RaspBerry Pi 5 as well, no issues.

[pps83]

No problems when I disconnected my router, just 'No internet connection' messages.

did you have this dialog when trying to sign in (not trying flaky connection after singed in)?

specifically with this, after when this msg showed up it would just sit doing nothing. After I clicked OK manually it would go into asking to enter password absolutely breaking unattended operation:

[pps83]

I just rebased, I saw PAUSE command was added, no idea what it's for. I also added my own command, perhaps it's way more that anything else you'd be interested to merge, but I wanted to be able to have full control of IBC through the tcp control channel (it mainly notifies my code about IBC events so my code knows what's happening).

these are two relevant changes:
Support optional REQ /RES request-id form in command channel
Add IBC control/event channel

[pps83]

I saw PAUSE command was added, no idea what it's for

asked claude what's PAUSE is for. Looks like it's the same as STOP, except it leaves out auto restart cookie so next start skips 2fa. If this is correct then PAUSE doesn't seem like the right name there. More like STOP_XXX where XXX something about preserving cookie etc.

[rlktradewright]

Please don't pollute this thread with other topics (like PAUSE). And see the release note for v3.24.0, and the User Guide for info about PAUSE.

[rlktradewright]

Yes, I tried both logging-in and already running with flaky connection (ie router disconnected so no internet connection for anything - maybe you did something different?).

Here it is trying to login without an internet connection:

So, have you tried with 10.47.1d ? I claim that there is no problem in that version. If you agree, then there is no point wasting any more time on ths issue. If you disagree, then tell me exact instructions to reproduce it. Icertainly have no intention to release a fix that is only relevant for a superseded TWS/Gateway.

[pps83]

I used VPN and sometimes it was making specifically SSL connections. No idea how/why, it wasn't fully absent connection, but it was specifically making SSL fail with that exact message. Also, if I have ssh open and enable that broken VPN ssh would drop randomly in the middle of connection. I could reconnect SSH though instantly (with turned off router that would be impossible).

The thing is, the code actually existed already in IBC to handle these: when I asked claude to fix it, it found code for handling these in IBC and said that likely when the code was initially written for these ibgw used different msg boxes. After ibgw changed its code slightly it stopped working. Maybe by looking in the change itself you'll see if it makes sense to accept the change. It's not complex imo (just in case, I don't do java at all. it's all done by clade)

[pps83]

By the way, just look at the diff here. Your code CANNOT work with current dialog for obvious reason: pps83@39e3ba6?w=1

The dialog has this text: "the application will automatically restart in" while old code checks for this string: "trading platform restart automatically". My change adds JFrame with "Exit Session Setting" title and with label containing "automatically restart" text.