Question 1: Does HTTPDNS support manual SDK integration?
Yes, it does. For detailed integration steps, see the iOS manual.
Question 2: Does the SDK support static or dynamic libraries?
The SDK currently supports only static libraries, not dynamic libraries.
Question 3: I received the following error during packaging: "error: Invalid bitcode version (Producer: ‘802.0.42.0_0’ Reader: ‘800.0.38_0’)". What is the minimum Xcode version required for the SDK bitcode?
The minimum required Xcode version for the SDK bitcode is 7.0.
Question 4: Why do I receive the "duplicate symbol _llvm.cmdline" error when I integrate the SDK in Xcode 6.x?
This error occurs because the HTTPDNS iOS SDK supports Bitcode, but its binary is not compatible with Xcode 6.x.
To resolve this issue, upgrade Xcode to version 7.0 or later.
Question 5: How do I resolve an error that occurs when I use use_frameworks! in the Podfile for a Swift project with CocoaPods integration?
If you use the use_frameworks! keyword, you must integrate the framework manually. For more information about the integration steps, see the iOS documentation.
Question 6: My client has App Transport Security (ATS) enabled, which restricts HTTP access. Does this affect the HTTPDNS solution?
App Transport Security (ATS) does not affect HTTPDNS.
This is because HTTPDNS sends network requests using IP addresses instead of domain names.
For issues in HTTPS scenarios, such as Server Name Indication (SNI) issues, you can configure the settings as described in the documentation.
Question 7: Is there a WebView example in the demo?
This feature is temporarily unpublished due to some issues. To integrate it, you must now use the following method.
We are developing a more comprehensive solution for this scenario and will provide it soon.
In the meantime, you can use NSURLProtocol to intercept and process requests as a workaround.
For more information, see Section 4.4 HTTPS/WebView/SNI Scenarios in the official documentation.