With BlackBerry 10.3.2 being tested through the BlackBerry Beta Zone, BlackBerry has now taken the next step and made the 10.3.2 beta autoloaders available for developers as well. Interestingly enough though they are a version behind what is being offered in the Beta Zone. Software version 10.3.2.159 is what's available through the autoloaders while Beta Zone is offering software version 10.3.2.304. In any case, BlackBerry has outlined what developers need to know about these autoloaders.
Get your applications ready for BlackBerry 10 OS 10.3.2. We've just released beta autoloaders with 10.3.2, which you can get from the software update page. There are also 10.3.2 beta simulators available for download for those without a BlackBerry 10 device to use for testing. No new APIs have been added in this release. Applications that supported BlackBerry 10.3.1 should also work on 10.3.2. There are a couple of known issues with this beta release that could affect your applications.
The first affects applications that use Active Frames. Your active frame may appear distorted or stretched in this beta release. The second issue affects BlackBerry WebWorks applications. Network requests (including XMLHttpRequest and normal subresource loads) that need HTTP authorization, display a credential dialog box when invoked from the browser, but don't display a dialog box when invoked from a WebWorks app. If you encounter any other API issues, please report them to us using Issue Tracker.
It should go without saying, that this OS is for developers only and normal folks shouldn't be downloading it and loading it onto their everyday devices, as we know from leaks some unintended things can happen. If you're a developer and looking to test your apps against this OS, you'll find it live on the Software Update page as well as the 10.3.2 simulators. Sadly as noted above, no new APIs have been added in this release.
PS: - There appears to be a bug on the page where it only links to the STL100-1 files, but all you need to do is change the URL to your device. Developers should know how to adjust this but hopefully BlackBerry will fix it.