Given this code from one of my open source projects:
[code]Dim Pass As Xojo.Core.MemoryBlock = Beacon.DecodeHex(Dict.Value(“Pass”))
Try
Pass = Xojo.Crypto.RSADecrypt(Pass, Identity.PrivateKey)
Catch Err As Xojo.Crypto.CryptoException
MsgBox(“Failed”)
Return
End Try
MsgBox(“Success”)[/code]
On Mac, this behaves as expected with the “Failed” message box showing. On 2017r3 Windows 32-bit on Win 10, the exception is triggered while debugging but the “Success” message box displays instead of the “Failed” message. This seems to be happening with every exception handler in my app, which is obviously creating havoc.
This is the first I’ve seen something like this. Any advice? I can’t reproduce this in a simple project. The code is executing on the main thread.
Good find. It seems to be exclusive to Xojo.Crypto.CryptoException. Xojo.Data.InvalidJSONException is caught correctly too, so it’s not new framework stuff.