Logger

In most scenarios, adding a simple logger can give insight on what is incorrect.

DexcareSDKLogger

The DexcareSDKLogger is a protocol that you can use to see more information about what the SDK does. If an instance of DexcareSDKLogger is attached on initialization, the SDK will post results, errors, information to the logger, which can help you debug issues.

The DexcareSDKLogger has one function you must implement: func log(_ message: String, level: DexcareSDKLogLevel, sender: String)

// Example `DexcareSDKLogger` to pass into the SDK.
// Pass ConsoleLogger() into the SDK init method to post NSLog's to the console.
class ConsoleLogger: DexcareSDKLogger {
    static var shared: ConsoleLogger = ConsoleLogger()
    func log(_ message: String, level: DexcareSDKLogLevel, sender: String) {
        let emoji: String
        switch level {
            case .verbose: emoji = "➡️"
            case .debug: emoji = "✳️"
            case .info: emoji = "✏️"
            case .warning: emoji = "⚠️"
            case .error: emoji = "❌"
        }
        NSLog("\(emoji) \(sender): \(message)")
    }
}

As an example, if the above is implmented, and a function call fails to the server, it will print to the console:

❌ DexcareSDK: Response error in 1.58s for: https://dexcareurl.com/api/7/visits/providerbooking?product=healthconnect-iOS - Status: 500 - Correlation: AD5C5189-DC90-46CB-A5F8-2641A0886E2C

Correlation

By providing the Correlation GUID to your dexcare contact, we can easily tell what went wrong in the call.

Without it, it is more difficult to search on a server log to try and find out what happened.

Proxy

There are proxy observer apps that you can install on your machine to help you debug further what could be wrong. Proxies allow you to view what json is sent and returned from within the SDK to an API call. Charles Proxy and Proxyman are good examples.

Cocoapod Issues

Changes in Xcode 12 have changed the way we need to use cocoapods. Please see the v6.0 Migration Guide