Before submitting
Area
SwiftUI client in apps/swift-ios on the owner branch from #5178.
Problem or use case
When diagnosing a native-client problem, SwiftUI Settings does not expose the app version alongside the selected environment server version. Testers also lack a direct route from the installed build to the relevant source or release changelog.
Proposed solution
Add a compact version section to SwiftUI Settings that shows the app version/build and the active environment server version. When public Git build metadata is present, include a link to the source comparison for that build; include the public release changelog link where applicable.
Why this matters
Support reports can identify the exact client/server pairing without asking users to inspect build tooling or server logs, and testers can quickly review what changed in their build.
Smallest useful scope
Expose the existing server version through the SwiftUI feature model and render read-only rows in Settings. Use only public repository/release URLs and optional embedded commit metadata. Do not include signing, TestFlight, private host, or personal release configuration.
Alternatives considered
Showing only the app version omits the server half of a compatibility report. Copying diagnostic data could be a later improvement but is not required for the first patch.
Risks or tradeoffs
The UI must handle disconnected environments and absent build metadata without fabricating values. Changelog links should only appear when a valid public target can be constructed.
References
SwiftUI owner PR: #5178.
Contribution
Before submitting
Area
SwiftUI client in
apps/swift-ioson the owner branch from #5178.Problem or use case
When diagnosing a native-client problem, SwiftUI Settings does not expose the app version alongside the selected environment server version. Testers also lack a direct route from the installed build to the relevant source or release changelog.
Proposed solution
Add a compact version section to SwiftUI Settings that shows the app version/build and the active environment server version. When public Git build metadata is present, include a link to the source comparison for that build; include the public release changelog link where applicable.
Why this matters
Support reports can identify the exact client/server pairing without asking users to inspect build tooling or server logs, and testers can quickly review what changed in their build.
Smallest useful scope
Expose the existing server version through the SwiftUI feature model and render read-only rows in Settings. Use only public repository/release URLs and optional embedded commit metadata. Do not include signing, TestFlight, private host, or personal release configuration.
Alternatives considered
Showing only the app version omits the server half of a compatibility report. Copying diagnostic data could be a later improvement but is not required for the first patch.
Risks or tradeoffs
The UI must handle disconnected environments and absent build metadata without fabricating values. Changelog links should only appear when a valid public target can be constructed.
References
SwiftUI owner PR: #5178.
Contribution