Debugger tool for iOS, support both Swift and Objective-C language.
The author stole the idea from Dotzu JxbDebugTool SWHttpTrafficRecorder Sandboxer so that people can make crappy clones.
DebugMan has the following features:
- Display all app network http requests details, including SDKs and image preview.
- Display app device informations and app identity informations.
- Preview and share sandbox files on device/simulator.
- Display all app logs in different colors as you like.
- App memory real-time monitoring.
- Display app crash logs.
- iOS 8.0+
- Xcode 9.0+
- Swift 3.0+
Use CocoaPods to install
DebugMan by adding it to your
platform :ios, '8.0'
target 'your_project' do
pod 'DebugMan', :configurations => ['Debug']
~> 3.x.x for Swift 3
~> 4.x.x for Swift 4
[[DebugMan shared] enableWithServerURL:nil ignoredURLs:nil onlyURLs:nil tabBarControllers:nil recordCrash:YES];
For more advanced usage, check in demo.
The collapse of the statistical functions collected should only be called once, if the third party is also best to use only a third party, so access to the collapse of the statistical information is also the only way. Third-party statistical tools are not used as much as possible, the use of multiple crashes to collect third-party will lead to malicious coverage of
NSSetUncaughtExceptionHandler() function pointer, resulting in some third-party can not receive the crash information.
- So, if you are using crash reporting SDKs like Crashlytics or Bugly, I recommend to close
DebugMan crash reporting. For more, see
DebugMan advanced usages.
You can shake device/simulator to hide/show the black bubble.
DebugMan, app's key window is DebugMan's transparent window. You can check app's UI layout by Reveal.
If you want to get the root view controller for the app's key window,
UIApplication.shared.keyWindow?.rootViewController may crash. You should use
If you want to show a toast in app's key window, like MBProgressHUD SVProgressHUD,
UIApplication.shared.keyWindow to get app's key window may cause toast invisible. You should use
- Author: liman
- WeChat: liman_888
- QQ: 723661989
- E-mail: email@example.com
Welcome to star and fork. If you have any questions, welcome to open issues.