Integrating as a Framework
Include DyScan.framework and the Assets folder (contained within the framework) into your project.
Include DyScan.framework as an “Embedded Binary” in your app. You can see this in your Xcode project’s “General” settings. In the “Build Phases” of the Xcode project settings, include the contents of the Assets folder in “Copy Bundle Resources.” Verify that DyScan.framework is included under “Link Binary with Libraries.” Still in “Build Phases,” add the contents of this script after “Embed frameworks” (use the + button in the top left of the window to add a script). This strips out the simulator-compatible part of the framework that the app store will reject. If your app does not already ask for camera permissions, add the key “NSCameraUsageDescription” (Privacy - Camera Usage Description) to your app's Info.plist file. You should set the value to be the string a user sees when they are prompted for the camera permission (e.g. To scan credit cards).
DyScan should be integrated properly now. See this guide on how to interface with it.
Include DyScan.framework (from the Static directory in our GitHub repo) and the Assets folder (contained within the framework) into your project.
If you have no Objective C++ files (with extension .mm), you will need to add a blank Objective C++ file to your project. If you have no bridging header, add a blank bridging header as well. This ensures Xcode compiles the framework properly.
In the “Build Phases” of the Xcode project settings, include the contents of the Assets folder in “Copy Bundle Resources.” Verify that DyScan.framework is included under “Link Binary with Libraries.” If your app does not already ask for camera permissions, add the key “NSCameraUsageDescription” (Privacy - Camera Usage Description) to your app's Info.plist file. You should set the value to be the string a user sees when they are prompted for the camera permission (e.g. To scan credit cards).
DyScan should be integrated properly now. See this guide on how to interface with it.