You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -53,7 +53,7 @@ The SDK should be initialized as early as possible in the app lifecycle. This is
53
53
As such, the SDK should (ideally) be initialized in host application’s `applicationDidFinishLaunching` method, so that the SDK can continue uploading any files that remain to be uploaded. This helps expedite 3D model generation, as we need all the captured images and metadata to begin the 3D reconstruction process.
@@ -69,14 +69,14 @@ class AppDelegate: UIResponder, UIApplicationDelegate {
69
69
The host app can launch the SDK in any way it sees fit, as long as there is an active ViewController somewhere in the app. Here is one example using SwiftUI of launching the SDK capture flow on a button click:
70
70
71
71
```swift
72
-
importHVCaptureSDK
72
+
importHVCaptureSDK
73
73
importSwiftUI
74
74
75
75
structFooView: View {
76
76
let jobInfo: CaptureJobInformation
77
77
let sessionSettings: HVCameraSettings
78
78
79
-
// ... populate settings, etc.
79
+
// ... populate settings, etc.
80
80
81
81
var body: some View {
82
82
Button("Start Capture") {
@@ -117,7 +117,7 @@ Note that the SDK executed asynchronously, and the task that calls ``startCaptur
117
117
118
118
#### Cancelling a Capture Session
119
119
120
-
Since we execute asynchronously, within a Swift ``Task``, we also honor its cancellation functionality and stop the capture session and capture flow UI if the task is cancelled.
120
+
Since we execute asynchronously, within a Swift ``Task``, we also honor its cancellation functionality and stop the capture session and capture flow UI if the task is cancelled.
Notable changes to the SDK across recent versions. The format below is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
145
+
146
+
147
+
148
+
# 2.4.0 2025-07-29
149
+
150
+
### Changed
151
+
* Miscellaneous Improvements
152
+
153
+
154
+
# 2.2.1 2025-07-21
155
+
156
+
### Changed
157
+
* Fix build issues due to xcode version mismatch
158
+
159
+
160
+
# 2.2.0 2025-07-17
161
+
162
+
### Changed
163
+
164
+
* Gallery image display with full-screen support
165
+
* Started Swift 6 migration
166
+
167
+
### Fixed
168
+
169
+
* Camera orientation issues
170
+
* Errors related to session management
171
+
* Shutter button bugs
172
+
* Gallery display issues
173
+
174
+
# 2.1.0 2024-12-06
175
+
176
+
### Changed
177
+
178
+
* Offline Job Creation: The Hover SDK can now initiate Jobs without internet connection. When connectivity returns, a job ID can be linked to the offline job dynamically.
179
+
* Miscellaneous Bug Fixes.
180
+
181
+
# 2.0.1 2024-11-12
182
+
183
+
### Changed
184
+
185
+
* Some bug fixes around theming and overridable resources
186
+
* Fix some tutorial code snippets that used deprecated / removed symbols
187
+
188
+
# 2.0.0 2024-11-01
189
+
190
+
### Added
191
+
192
+
* Opt-in support for background uploads – see the Getting Stated guide and Capture SDK Essentials tutorial for more details.
193
+
* More flexible remote logging authentication and key management, so New Relic keys are no longer embedded in the SDK.
194
+
195
+
### Changed
196
+
197
+
*[BREAKING] Various HVTheme resources were renamed to better account for future attributes and better align with the corresponding Android resource names. See the Migration Guide for the old-to-new name mappings and theming tutorial for more detailed specifics.
198
+
* Deprecated old HVCameraExterior symbol, HVPartnerSDK should be used instead.
199
+
200
+
### Fixed
201
+
202
+
* Resolved a rare deadlock at camera start for consecutive camera sessions.
203
+
* Fixed a corner case where the minimum photo validations could be bypassed.
204
+
* Fixed a warning about checking CLLocationManager.authorizationStatus on the main thread.
205
+
206
+
Also, as of this release the hover-capture-ios repository is public, so users are no longer required to have authorization or Personal Access Tokens set up to use the package.
0 commit comments