Hi Authorize.Net team,
We’re seeing inconsistent version values for the iOS SDK in production diagnostics and wanted to report it in case packaging/metadata is out of sync.
Observed version values
In the same app build/environment, we observe:
- GitHub release/docs version: 4.5.1
- Embedded framework plist (
AnetEMVSdk.framework → CFBundleShortVersionString): 4.2
- Runtime/library API (
AnetEMVManager.anetSDKVersion()): 3.0.3
Why this matters
We log SDK version telemetry for incident triage and rollout verification.
These mismatched values make it difficult to determine which SDK build is actually running on device.
How we retrieve each value
- Runtime SDK string:
AnetEMVManager.anetSDKVersion()
- Framework bundle version:
CFBundleShortVersionString from embedded AnetEMVSdk.framework
- Public expected version:
- GitHub release/documented version (
4.5.1)
Request
Could you please confirm:
- Which value should be treated as the source of truth?
- Whether these three values are expected to differ by design?
- If not expected, can version metadata be normalized in an upcoming release?
Thanks for your help.
Hi Authorize.Net team,
We’re seeing inconsistent version values for the iOS SDK in production diagnostics and wanted to report it in case packaging/metadata is out of sync.
Observed version values
In the same app build/environment, we observe:
AnetEMVSdk.framework→CFBundleShortVersionString): 4.2AnetEMVManager.anetSDKVersion()): 3.0.3Why this matters
We log SDK version telemetry for incident triage and rollout verification.
These mismatched values make it difficult to determine which SDK build is actually running on device.
How we retrieve each value
AnetEMVManager.anetSDKVersion()CFBundleShortVersionStringfrom embeddedAnetEMVSdk.framework4.5.1)Request
Could you please confirm:
Thanks for your help.