Network Masking

Luciq automatically logs all network requests performed by your app from the start of the session. Requests details, along with their responses, are sent with each report. Luciq will also show you an alert at the top of the bug report in your dashboard when network requests have timed-out or taken too long to complete. Note that the maximum number of network logs sent with each report is 1,000.

An example of network request logs in the Luciq dashboard

Logging HttpUrlConnection requests for Android

To log network requests, use LuciqNetworkLog then use the following method at the HttpUrlConnection, requestBody and responseBody referenced here.

Auto-Masking Network Headers

Starting from SDK Version 14.2.0, our SDK will automatically mask the below keys from Network Headers and Query Parameters to ensure that no sensitive data reaches our servers.

The below keys will be displayed normally on the dashboard, but their corresponding values will be replaced with an asterisk (*) to protect sensitive data.

Keys

List of keys that will be automatically masked" 
 "authorization_token, auth_token, auth, access_token, token, oauth_token, bearer_token, refresh_token, jwt_token, jwt, Username, password, pwd, api_key, apikey, secret, client_secret, app_secret, consumer_secret"

Adding New Keys

The list of masked keys is configurable on our side. This means you don't need to make any code changes to add new keys; they will be automatically reflected in the next session. If you need additional keys added, please reach out to support.

Disabling Network Header Auto-Masking

This feature is enabled by default and we strongly recommend to keep it enabled to make sure PII data is not collected by our SDK. However, if you need to disable it for any reason, please use the below API.

Swift

NetworkLogger.autoMaskingEnabled = false

Objective-C

Omitting Requests

You can omit requests from being logged based on their request or response details. You can also specify an expression to be evaluated against every request and response to determine if the request should be included in logs or not.

Swift

let path = "/products"
let requestPredicate = NSPredicate(format: "URL.path MATCHES %@", path)
let responsePredicate = NSPredicate(format: "statusCode >= %d AND statusCode <= %d", 200, 399)
NetworkLogger.setNetworkLoggingRequestFilterPredicate(requestPredicate, responseFilterPredicate: responsePredicate)

Objective-C

Obsucating Data

Requests

You can obfuscate sensitive user data, such as authentication tokens, in requests without filtering out the whole request.

Swift

NetworkLogger.setRequestObfuscationHandler { (request) -> URLRequest in
    var myRequest: NSMutableURLRequest = request as! NSMutableURLRequest
    let urlString = request.url?.absoluteString
    urlString = obfuscateAuthenticationTokenInString()
    let obfuscatedURL = URL(string: urlString)
    myRequest.url = obfuscatedURL
    return myRequest.copy() as! URLRequest
}

Objective-C

Responses

Swift

NetworkLogger.setResponseObfuscationHandler { (data, response, completion) in
    if let data = data {
        let modifiedData = self.modify(data: data)
        let modifiedResponse = self.modify(response: response)
        completion(modifiedData, modifiedResponse)
    }
}

Objective-C

Note: Protecting sensitive information and respecting user privacy are vital. By following these steps, you'll create a secure and trustworthy environment for your users.