New SDK files were changed, but their version was never incremented

When you released a new version of your SDK, the following files were updated, but their version never changed. This poses an issue for deployments using Windows MSI, as by default it will not overwrite files that have the same version. We only found the issue after Zoom library failed to load at runtime and threw an exception (see screenshot below). There are workarounds, but they are cumbersome, and the fact that you have two different files with the same version is definitely not good in general.

Here is the list of files where the binaries changed, but the version remained the same between v4.4.57220.1211 and v4.6.15798.0403:

annoter.dll - 35.0.1602.20
CptShare.dll - 2.1.2013.626
mdnsclient.dll -
mDNSResponder.dll -
ssb_sdk.dll - 2.7.507.2014
tp.dll - 1.0.2012.1222
util.dll| - 1.0.2012.1222
XmppDll.dll -
zCrashReport.dll -
zCrashReport.exe -
Aomhost/zCrashReport64.dll -
Aomhost/zCrashReport64.exe -

Which version?
The discrepancy is between SDK v4.4.57220.1211 and v4.6.15798.0403

To Reproduce(If applicable)
Compare binaries and version of the files specified above, between the two SDK releases.


Device (please complete the following information):

  • Device Spec: PC
  • OS: Windows 10

Hi Zoomer1,

Thank you very much for mentioning this. I will forward this to the engineering team for investigation.