Inconsistent Behaviour with SHA 256 Inbuilt Functions for x64 and x86 builts

Issue Details

I have a LabVIEW project which uses built in SHA-256 library and it is shared between LabVIEW 2022Q3 32bit and 64bit. As I require both x86 and x64 support for which I have created the platform specific application distribution and use the corresponding distribution to build the specific platform build (x86 or x64). Now the build generated using x64 works fine, but the build generated using x86 is not producing the proper SHA 256 outcome. Some times, none of the build produces the proper outcome.

Note: Only one LabVIEW application (x86 or x64) is active at one point of time. And the builds are platform specific, I have created the clean builds.

Solution

This is an expected behaviour as builts are different,

The inconsistency happens because you are relying on implicit string/hex display behavior and different implementations, so x86 and x64 end up hashing or formatting different underlying byte data even though it looks the same visually.

You can make the below modification to the LabVIEW code to resolve the issue, where the output string is designed to explicitly converts the string into a HEX string.

Note: The Output indicator should be set to "Normal Display" as the conversion of Hex has been explicitly performed.

As a result you will be seeing the expected outcome in both the executables matching the online tool results as shown below:

SHA253 - Online tool:

x64 Executable:

x86 Executable: