I got the following error detail when I tried the library in a Objective C project with deployment target 8.0.

Undefined symbols for architecture x86_64: "OBJC_CLASS$_DBDebugToolkit", referenced from: objc-class-ref in AppDelegate.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)

How to overcome this issue ?

We use AFNetworking and have code like the following

let httpSessionManager = AFHTTPSessionManager(baseURL: baseURL)
httpSessionManager.setTaskWillPerformHTTPRedirectionBlock { urlSession, task, response, request in
  return someCheck
    ? request
    : nil // Stop following redirect
}

After we integrated DBDebugToolkit we noticed that this block was not getting called anymore. Disabling networking logging via DBDebugToolkit.setNetworkRequestsLoggingEnabled(false) fixes the issue.

I looked at AFNetworking's related code (part 1, part 2) and it does not seem to do anything special which leads me to believe that this is a general issue.

Please let me know if additional information is needed to reproduce this behavior.

Hi,

For first, very good job, I'm trying to use your library and it appears that it's not compatible with URLSessionDelegate, in my app i'm using https with a self-signed certificate and I use URLSessionDelegate for debug and when i'm setup your library, delegate are not fired and make me errors.

Steps for reproducing: AppDelegate.swift

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
        // Override point for customization after application launch.
        
        #if DEBUG
            DBDebugToolkit.setup() // <-- if I comment network works good
        #endif

        ...

SSLDebugSessionDelegate.swift

class SSLDebugSessionDelegate: NSObject, URLSessionDelegate {
    
    /// The host to allow a self-signed SSL certificate for.
    let host: String
    
    
    /** Designated initializer.
     
     - parameter host: The host to which the exception should apply
     */
    public init(host: String) {
        self.host = host
    }
    
    open func urlSession(_ session: URLSession, didReceive challenge: URLAuthenticationChallenge,
                         completionHandler: @escaping (URLSession.AuthChallengeDisposition, URLCredential?) -> Void) {
        Log.debug("----DEBUG SESSION DELEGATE----")
        if challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodServerTrust {
            if challenge.protectionSpace.host == host, let trust = challenge.protectionSpace.serverTrust {
                let credential = URLCredential(trust: trust)
                completionHandler(.useCredential, credential)
                return
            }
        }
        completionHandler(.performDefaultHandling, nil)
    }

}

let sessionDelegate = SSLDebugSessionDelegate(host:"xxxxxxx")
URLSession(configuration: config, delegate: sessionDelegate, delegateQueue: nil)

And use a self-signed certificate.

Crash message *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'

Stack trace

version 0.7.0 crash if any network request triggered before DBDebugToolkit.setup():

file name: NSURLSessionConfiguration+DBURLProtocol.m [originalProtocols insertObject:DBNetworkURLProtocolClass atIndex:0]; *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'

The cause is from the update for issue #50.

In this update, NSURLSessionConfiguration+DBURLProtocol.m: [originalProtocols insertObject:DBNetworkURLProtocolClass atIndex:0]

1. NSURLSessionConfiguration's swizzing happens in +(void)load, which is when app starts, even before appDelegate.didFinishLaunchingWithOptions.
2. DBNetworkURLProtocolClass is initialised in + (void)initialize, which will be triggered by DBDebgToolkit.setup().

So, without executing DBDebgToolkit.setup(), DBNetworkURLProtocolClass will not be initialed, and it will be crashed.

We can use load to initialise DBNetworkURLProtocolClass, or ask user to run DBDebgToolkit.setup() before any network calls that involved NSURLSessionConfiguration.

Rewire delegate to UISearchBar instance. UISearchController is deprecated and is raising warning when compiling our code. It also breaks Catalyst builds.

There is a weird bug related to custom URLSession and URLCache.

Project setup

Here is my AppDelegate that enables DBDebugToolkit.

class AppDelegate: UIResponder, UIApplicationDelegate {

    var window: UIWindow?

    func application(_ application: UIApplication,
                     didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {

        DBDebugToolkit.setup()

        let window = UIWindow(frame: UIScreen.main.bounds)
        self.window = window
        window.backgroundColor = UIColor.white
        window.rootViewController = ViewController()

        window.makeKeyAndVisible()
        return true
    }
}

In my ViewController, I have a button that loads an url with Cache-Control header set, meaning the system should cache the response.

class ViewController: UIViewController {

    private lazy var button: UIButton = {
        let button = UIButton(type: .system)
        button.setTitle("Load", for: .normal)
        button.addTarget(self, action: #selector(load), for: .touchUpInside)
        return button
    }()

    // Custom URLSession with custom cache and custom diskPath
    private lazy var session: URLSession = {
        let memoryCapacity = 500 * 1024 * 1024 // 500 MB
        let diskCapacity = 500 * 1024 * 1024 // 500 MB

        let cache = URLCache(
            memoryCapacity: memoryCapacity,
            diskCapacity: diskCapacity,
            diskPath: "com.xxxxx.yyyyy"
        )

        let configuration = URLSessionConfiguration.default
        configuration.urlCache = cache

        return URLSession(
            configuration: configuration,
            delegate: self,
            delegateQueue: nil
        )
    }()

    override func viewDidLoad() {
        super.viewDidLoad()
        view.addSubview(button)
        button.frame = view.bounds
    }

    // MARK: - Private

    @objc private func load() {
        // A ~130 KB image, small enough to be cached by the default URLSession session
        let url = URL(string: "https://images.unsplash.com/photo-1518791841217-8f162f1e1131?ixlib=rb-1.2.1&auto=format&fit=crop&w=1000&q=80")!
        session.dataTask(with: url).resume()
    }
}

extension ViewController: URLSessionDataDelegate {

    // MARK: - URLSessionDataDelegate

    func urlSession(_ session: URLSession,
                    dataTask: URLSessionDataTask,
                    willCacheResponse proposedResponse: CachedURLResponse,
                    completionHandler: @escaping (CachedURLResponse?) -> Void) {
        print("session:willCacheResponse:")
        completionHandler(proposedResponse)
    }

    func urlSession(_ session: URLSession,
                    dataTask: URLSessionDataTask,
                    didReceive response: URLResponse,
                    completionHandler: @escaping (URLSession.ResponseDisposition) -> Void) {
        print("dataTask:didReceive response")
        completionHandler(.allow)
    }

    func urlSession(_ session: URLSession,
                    dataTask: URLSessionDataTask,
                    didReceive data: Data) {
        print("data = \(data)")
    }
}

With DBDebugToolKit activated

When I first clic on the load button, the request is sent to the server, and the logs are the following :

dataTask:didReceive response
data = 129408 bytes

When I clic a second time, the request is not sent to the server, the cached image is used and the logs are the same.

We can note that the log print("session:willCacheResponse:") is never called even it should be.

The cache folder structure is :

Note the duplication of the Cache.db files. What's more the fsCachedData folder, that contains the cached image, is at the wrong location. That means the image is saved in the default URLCache and not in the custom one I defined in my sesssion.

Without DBDebugToolKit activated

If I trash the app and remove the line DBDebugToolkit.setup() in the AppDelegate, when I first clic on the image, the request is sent to the server and the logs are the following:

dataTask:didReceive response
data = 16384 bytes
data = 16384 bytes
data = 16384 bytes
data = 16383 bytes
data = 16384 bytes
data = 16384 bytes
data = 16384 bytes
data = 14721 bytes
session:willCacheResponse:

Note that this time the logs are correct and session:willCacheResponse: is printed !

The cache folder structure is This time there is only one Cache.db file, and the fsCachedData folder is under the com.xxxxx.yyyyy directory. Which is the expected behavior.

Issue

So the issue is that a custom url session with a custom url cache is never taken into account with DBDebugToolkit activated. What's more the URLSessionDataDelegate method urlSession(_:, dataTask:, willCacheResponse:, completionHandler:) is not called.

// UIView+DBUserInterfaceToolkit.h

+ (void)load {
    static dispatch_once_t onceToken;
    dispatch_once(&onceToken, ^{
        __block IMP originalInitWithCoderIMP = [self replaceMethodWithSelector:@selector(initWithCoder:)
                                                                         block:^UIView * (UIView *blockSelf, NSCoder *aDecoder) {
                                                                            UIView *res = ((UIView * (*)(id, SEL, NSCoder *))originalInitWithCoderIMP)(blockSelf, @selector(initWithCoder:), aDecoder);
                                                                            [res db_refreshDebugBorders];
                                                                            [res db_registerForNotifications];
                                                                            return res;
                                                                         }];
        __block IMP originalInitWithFrameIMP = [self replaceMethodWithSelector:@selector(initWithFrame:)
                                                                         block:^UIView * (UIView *blockSelf, CGRect frame) {
                                                                             UIView *res = ((UIView * (*)(id, SEL, CGRect))originalInitWithFrameIMP)(blockSelf, @selector(initWithCoder:), frame);
                                                                             [res db_refreshDebugBorders];
                                                                             [res db_registerForNotifications];
                                                                             return res;
                                                                         }];
        __block IMP originalDeallocIMP = [self replaceMethodWithSelector:NSSelectorFromString(@"dealloc")
                                                                   block:^(__unsafe_unretained UIView *blockSelf) {
                                                                       [[NSNotificationCenter defaultCenter] removeObserver:blockSelf];
                                                                       ((void (*)(id, SEL))originalDeallocIMP)(blockSelf, NSSelectorFromString(@"dealloc"));
                                                                   }];
    });
}

Is there a bug with this line:

UIView *res = ((UIView * (*)(id, SEL, CGRect))originalInitWithFrameIMP)(blockSelf, @selector(initWithCoder:), frame);

You pass @selector(initWithCoder:) but shouldn't you pass @selector(initWithFrame:)?

After installing DBDebugToolkit, the phone crashes every time two successive popups were created (shown at the same time) and then when dismissing both (one after the other) causes the app to crash. Uninstalling DBDebugToolkit causes the crash not to happen. It is replicable within all scenarios whereby two popups were created and then dismissed.

• (void)windowDidResignKey:(UIWindow *)window { [window removeObserver:self forKeyPath:@"layer.sublayers"]; // causes exception if UIPickerView is displayed from modal form }

*** Terminating app due to uncaught exception 'NSRangeException', reason: 'Cannot remove an observer <DBPerformanceToolkit 0x1741193e0> for the key path "layer.sublayers" from <_UIAlertControllerShimPresenterWindow 0x102cdacd0> because it is not registered as an observer.'

Also wrapping a try-catch around it does not fix the issue.

Hello,

Very nice toolkit! One thing I’ve noticed is, the more blocked the main thread is, the less accurate the measurements are. Especially the FPS measurement, it is possible to lose entire CPU spikes (60 fps -> quick ramp up of a CPU spike for some time -> 60 fps). I have found that the CADisplayLink strategy for measuring FPS is not the most accurate if main thread spikes exist.

One challenge with moving the measurements to a background queue is updating the widget and table view. This can be solved by using a CATextLayer to update the text in a background queue (CALayer and CATransation are thread safe as of iOS 4).

Would you be interested in a PR that accomplishes this?

A crash occurred when my app continued to send requests while the Network section was open

__71-[DBNetworkViewController networkDebugToolkit:didUpdateRequestAtIndex:]_block_invoke (DBNetworkViewController.m:210)
__29-[DBMainQueueOperation start]_block_invoke (DBMainQueueOperation.m:72)

DBDebugToolkit (0.6.0) iOS 15.5 MacOS 12 Xcode 13.4.1

Bumping from 0.8.0 to 0.9.0 completely breaks all network requests that are done through Alamofire.

This is what I see in the console:

API MISUSE: NSURLSession delegate Alamofire.SessionDelegate: <Alamofire.SessionDelegate: 0x600000e609b0> (0x600000e609b0)
API MISUSE: dataTask:didReceiveResponse:completionHandler: completion handler not called

Feels like methods are not correctly swizzled anymore?

Hello! Version: 0.9.0 installed by cocoapods App works fine in debug mode, but crashes app immediately on Test Flight/App Store without crash logs. iOS 15.4.1 Xcode 13.3.1 OS X Monterey I've experienced similar crashes when external dynamic library was not embedded into the target.

Could you add a button that allows to copy the entire request and response body? Often they are huge, and scrolling and selecting is very inconvenient. cmd+A not always works in simulator

Thank you

Hello, dbukowski!

I've faced an issue (bug?) while using DBDebugToolkit with Swift iOS(iPhone) application. If app being built to Simulator, or directly to device using XCode and usb cable, everything works perfectly fine.

But for testing purposes, I upload application to Firebase App Distribution. I do that with Fastlane. Fastlane builds the app, and then loads the build to Firebase App Distribution (through Firebase CLI). After that, the build becomes available for installation on approved devices without a cable, directly from Firebase App Distribution service.

When app installed this way, Console output in DBDebugToolkit is incomplete. Many lines are, for sure, missing. And, sometimes, missing lines appear, but with long delay. Sometimes missing lines don't appear at all.

What I've tried: 1/ Change build configuration from debug to adhoc and build directly to device using usb cable - console output was complete, means issue is not dependant on build configuration. 2/ Change build options in Fastfile and build to Firebase again (available options: include bitcode, include symbols) - nothing changed.

About environment: Xcode 13.1 Swift 5 DBDebugToolkit 0.6.2 Fastlane 2.205.1

My build settings in fastfile: