Filter

Let us know how we can improve our product!
We are not able to reply, but know that we review ALL submissions - Your feedback is essential to us!
Align CFBundleShortVersion with Actual Release Version of the Smart Agent
Currently, in Lightspeed Agent v3.2.0, the CFBundleShortVersionString in Lightspeed Agent.app/Contents/Info.plist reports 1.2.1, which does not align with the actual agent release version. Issue: This inconsistency creates challenges for MDM-based software management (e.g., Jamf Pro), which typically relies on CFBundleShortVersionString to track application versions. While I understand that the version reported in the .app bundle reflects the Network Extension rather than the core agent, this approach is non-standard and inconsistent with how most macOS applications report their versions. As a result, administrators must write custom scripts to pull the correct version from alternative sources (/usr/local/bin/mobilefilter -v or /Applications/.lightspeed-agent/mac-manifest.json), which complicates deployment and patch management workflows. Proposed Solution: Update CFBundleShortVersionString in Info.plist to reflect the actual Lightspeed Agent release version (e.g., 3.2.0). Move the Network Extension version to an alternative location, such as within mac-manifest.json, rather than using it as the primary version in Info.plist. Benefits: Standardizes version tracking with macOS and MDMs like Jamf Pro, eliminating the need for custom scripting. Aligns with Apple's expected versioning conventions for macOS applications. Simplifies software management for IT administrators handling deployments and patch updates. I appreciate your consideration of this request. Standardizing the versioning approach would greatly improve Lightspeed Agent management across macOS environments.
Load More