This is another interim release before the final release (which will be IBC 4.0, and which I hope to publish before September 1 2026).
The main fix here is to support the latest versions of TWS and Gateway (ie 10.48 onwards).
Because there is quite a lot of detailed change in this release, I recommend that you rename your current IBC folder (eg to IBC-old), and re-install from scratch so that you can easily carry your settings forward. There are no new config.ini settings, so your existing config.ini file should work fine: it's only the settings in the start scripts that you'll need to change.
Note that if you are running IBC on a Raspberry Pi (or other ARM-based hardware), you will need to install the Java 25 version of whatever Java runtime you are using and set the JAVA_PATH variable accordingly in the twsstart.sh and gatewaystart.sh scripts. This is because IBKR have re-targeted TWS and Gateway from Java 17 to Java 25 for the latest releases. Windows and non-ARM users don't need to do anything in this respect, and the bundled JRE will work fine.
I should also point out that running Gateway 10.45.1j (the current stable version) on the RaspberryPi encounters a problem after autorestart: for some reason, Gateway claims it cannot find its settings file (even though it is very visibly there), suggesting it might be corrupted, and offering to use an earlier version of this file. Accepting that offer results in the Trusted IP Addresses in the API configuration being removed; rejecting the offer leaves the settings in some indeterminate state. Curiously, running immediately after this with the ‘latest’ Gateway 10.50.1d runs perfectly normally.
This issue does not occur on PCs with Intel or AMD processors, or with the ‘latest’ Gateway. I don’t know yet whether it’s the same with TWS. Until I can get some clarification on this issue, I’ve decided to run the ‘latest’ version on my Raspberry Pi for both my live and paper accounts.