macOS Migration to Apple's Dispatch Queue, Network Framework, and SecItem #672
sfod
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
macOS migration to Apple's Dispatch Queue, Network Framework, and SecItem
macOS builds of aws-iot-device-sdk-java-v2 will replace kqueue with Apple's Dispatch Queue for thread management and replace Secure Transport and BSD based sockets with Apple's Network Framework and SecItem for socket and TLS negotiation.
Release Date
December 12, 2025
aws-iot-device-sdk-java-v2 v1.29.0+
What's changing
AWS IoT Device SDK for Java v2 will now support TLS 1.3 on macOS.
The API in aws-crt-java as well as aws-iot-device-sdk-java-v2 has not changed and no changes will be required of the user to accommodate this migration.
Where are the changes?
These changes have been implemented in aws-c-io (commit #758). A submodule of aws-crt-java which aws-iot-device-sdk-java-v2 depends on.
Why are you making this change?
The previously used Security Transport was deprecated by Apple in 2019. We do not know which version of macOS will fully drop this deprecated API. In deciding to migrate to their recommended Network Framework we were required to adopt their Dispatch Queue and SecItem frameworks.
I am having issues with these changes
Please visit the FAQ to check if you are running into a common issue. You may also investigate whether there is a similar issue or open a new issue here.
Beta Was this translation helpful? Give feedback.
All reactions