Aardvark alternatives and similar libraries
Based on the "Logging" category.
Alternatively, view Aardvark alternatives based on common mentions on social networks and blogs.
CocoaLumberjack9.9 5.5 L1 Aardvark VS CocoaLumberjackA fast & simple, yet powerful & flexible logging framework for Mac and iOS
NSLogger9.4 0.0 L1 Aardvark VS NSLoggerA modern, flexible logging tool
SwiftyBeaver9.4 2.1 L4 Aardvark VS SwiftyBeaverConvenient & secure logging during development & release in Swift 4 & 5
Pulse9.3 9.7 Aardvark VS PulseNetwork logger for Apple platforms
GodEye9.1 0.0 Aardvark VS GodEyeAutomaticly display Log,Crash,Network,ANR,Leak,CPU,RAM,FPS,NetFlow,Folder and etc with one line of code based on Swift. Just like God opened his eyes
XCGLogger9.1 0.0 L3 Aardvark VS XCGLoggerA debug log framework for use in Swift projects. Allows you to log details to the console (and optionally a file), just like you would have with NSLog() or print(), but with additional information, such as the date, function name, filename and line number.
TinyConsole8.1 0.0 L5 Aardvark VS TinyConsole📱💬🚦 TinyConsole is a micro-console that can help you log and display information inside an iOS application, where having a connection to a development computer is not possible.
Watchdog8.0 0.0 Aardvark VS WatchdogClass for logging excessive blocking on the main thread
Rainbow7.9 2.5 L5 Aardvark VS RainbowDelightful console output for Swift developers.
CleanroomLogger7.6 0.0 L4 Aardvark VS CleanroomLoggerCleanroomLogger provides an extensible Swift-based logging API that is simple, lightweight and performant
Willow7.5 0.0 L5 Aardvark VS WillowWillow is a powerful, yet lightweight logging library written in Swift.
KZLinkedConsole6.8 0.0 L5 Aardvark VS KZLinkedConsoleClickable links in your Xcode console, so you never wonder which class logged the message.
QorumLogs6.6 0.0 L4 Aardvark VS QorumLogs:closed_book: Swift Logging Utility for Xcode & Google Docs
AFNetworkActivityLogger6.6 0.0 L3 Aardvark VS AFNetworkActivityLoggerAFNetworking 3.0 Extension for Network Request Logging
Log6.5 0.0 L4 Aardvark VS LogAn extensible logging framework for Swift
Diagnostics6.3 1.6 Aardvark VS DiagnosticsAllow users to easily share Diagnostics with your support team to improve the flow of fixing bugs.
SwiftTrace5.8 4.1 Aardvark VS SwiftTraceTrace Swift and Objective-C method invocations
JustLog5.7 4.2 L4 Aardvark VS JustLogJustLog brings logging on iOS to the next level. It supports console, file and remote Logstash logging via TCP socket with no effort. Support for logz.io available.
LxDBAnything5.2 0.0 Aardvark VS LxDBAnythingAutomate box any value! Print log without any format control symbol! Change debug habit thoroughly!
Gedatsu5.2 0.0 Aardvark VS GedatsuGedatsu provide readable format about AutoLayout error console log
XLFacility4.6 0.0 L2 Aardvark VS XLFacilityElegant and extensive logging facility for OS X & iOS (includes database, Telnet and HTTP servers)
Twitter Logging ServiceTwitter Logging Service is a robust and performant logging framework for iOS clients
SwiftyTextTable4.1 0.0 L5 Aardvark VS SwiftyTextTableA lightweight library for generating text tables.
Loggerithm4.0 0.0 L3 Aardvark VS LoggerithmA lightweight Swift logger, uses print in development and NSLog in production. Support colourful and formatted output.
BlockTypeDescription3.8 0.0 Aardvark VS BlockTypeDescriptionShow type signatures when logging blocks
puree3.6 0.0 Aardvark VS puree[Obsoleted] A log collector for iOS (new version! -> https://github.com/cookpad/Puree-Swift)
Logkit3.5 0.0 L5 Aardvark VS LogkitAn efficient logging library for OS X, iOS, watchOS, and tvOS – written in Swift. Log to console, file, HTTP service, or your own endpoint. Simple to get started, but smartly customizable.
Atlantis3.5 0.0 L3 Aardvark VS AtlantisA powerful input-agnostic swift logging framework made to speed up development with maximum readability.
AEConsole3.1 0.0 L5 Aardvark VS AEConsoleCustomizable Console UI overlay with debug log on top of your iOS App
Bugfender2.8 0.0 Aardvark VS BugfenderBugfender SDK for iOS, a remote logger tailor-made for mobile
Reqres2.6 0.0 Aardvark VS ReqresSimple network activity logger for iOS
CleanroomASL2.5 0.0 L3 Aardvark VS CleanroomASLA Swift-based API for reading from & writing to the Apple System Log (more commonly known somewhat inaccurately as "the console")
Evergreen2.1 0.0 L4 Aardvark VS EvergreenMost natural Swift logging
TraceLog2.0 1.0 Aardvark VS TraceLogTraceLog is a highly configurable, flexible, portable, and simple to use debug logging system for Swift and Objective-C applications running on Linux, macOS, iOS, watchOS, and tvOS.
ReflectedStringConvertible1.8 0.0 L5 Aardvark VS ReflectedStringConvertibleA protocol that allows any class to be printed as if it were a struct or a JSON object.
XLTestLog1.7 0.0 L5 Aardvark VS XLTestLogStyling and coloring your XCTest logs on Xcode Console
Lighty1.5 0.0 L5 Aardvark VS LightyEasy to use and lightweight logger for iOS, macOS, tvOS, watchOS and Linux in Swift.
AELog1.3 0.0 L5 Aardvark VS AELogSimple, lightweight and flexible debug logging framework written in Swift
Spy1.0 0.0 Aardvark VS SpySpy is a flexible, lightweight, multiplatform logging utility written in pure Swift. It allows to log with different levels and on different channels. You can define what levels and channels actually are.
OkLog0.9 0.0 Aardvark VS OkLogA network logger for iOS and macOS projects.
LumberMill0.6 0.0 L5 Aardvark VS LumberMillA Simple iOS Testing Framework
StoryTeller0.5 0.0 L4 Aardvark VS StoryTellerA log should tell a story, not drown the reader in irrelevance.
Appwrite - The Open Source Firebase alternative introduces iOS support
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Aardvark or a related project?
Aardvark is a library that makes it dead simple to create actionable bug reports.
There are only three steps to get Aardvark logging and bug reporting up and running.
1) Install Aardvark.
platform :ios, '8.0' pod 'Aardvark'
Using Git Submodules
Or manually checkout the submodule with
git submodule add [email protected]:Square/Aardvark.git, drag Aardvark.xcodeproj to your project, and add Aardvark as a build dependency.
2) Setup email bug reporting with a single method call
It is best to do this when you load your application’s UI.
3) Replace calls to
In Objective-C, replace calls to
After doing the above, your users can report a bug by making a two-finger long-press gesture. This gesture triggers a UIAlert asking the user what went wrong. When the user enters this information, an email bug report is generated complete with an attached app screenshot and a text file containing the last 2000 logs. Screenshots are created and stored within Aardvark and do not require camera roll access.
[[Bug Report Flow](BugReportFlow.gif)](BugReportFlow.gif)
Want to look at logs on device? Push an instance of [ARKLogTableViewController](Aardvark/ARKLogTableViewController.h) onto the screen to view your logs.
Logs are distributed to loggers on an internal background queue that will never slow down your app. Logs observed by the log store are incrementally appended to disk and not stored in memory.
To turn on logging of uncaught exceptions, call
ARKEnableLogOnUncaughtException(). When an uncaught exception occurs, the stack trace will be logged to the default log distributor. To test this out in the sample app, hold one finger down on the screen for at least 5 seconds.
Once the exception is logged, it will be propogated to any existing uncaught exception handler. By default, the exception will be logged to the default log distributor. To log to a different distributor, call
ARKEnableLogOnUncaughtExceptionToLogDistributor(...). You can enable logging to multiple log distributors by calling the method multiple times.
Want to customize how bug reports are filed? Pass your own object conforming to the [ARKBugReporter](Aardvark/ARKBugReporter.h) protocol and the desired subclass of
[Aardvark addBugReporter:triggeringGestureRecognizerClass:]. You can further customize how bug reports will be triggered by modifying the returned gesture recognizer.
Want to change how logs are formatted? Set your own
logFormatter on the [ARKEmailBugReporter](Aardvark/ARKEmailBugReporter.h) returned from
Want to log to the console?
[ARKLogDistributor defaultDistributor].defaultLogStore.printsLogsToConsole = YES;.
Want different log files for different features? Create an [ARKLogStore](CoreAardvark/ARKLogStore.h) for each feature you want to have its own log file and add them to the default log distributor with
[[[ARKLogDistributor](Logging/ARKLogDistributor.h) defaultDistributor] addLogObserver:featureLogStore]. Set the
logFilterBlock on your [ARKLogStore](CoreAardvark/ARKLogStore.h) to make sure only the logs you want are observed by the [ARKLogStore](CoreAardvark/ARKLogStore.h). Use
userInfo dictionary to specify to which feature a log pertains. See [SampleViewController](AardvarkSample/AardvarkSample/SampleViewController.swift)’s
tapGestureLogStore for an example.
Want to send your logs to third party services? One log can be easily distributed to multiple services by adding objects conforming to [ARKLogObserver](CoreAardvark/ARKLogObserver.h) to the default [ARKLogDistributor](CoreAardvark/ARKLogDistributor.h) via
addLogObserver:. [SampleCrashlyticsLogObserver](AardvarkSample/AardvarkSample/SampleCrashlyticsLogObserver.h) is an example of an [ARKLogObserver](CoreAardvark/ARKLogObserver.h) that sends event logs to Crashlytics.
Want to log with Aardvark but don’t want to use Aardvark’s bug reporting tool? Skip step #2 in Getting Started and manually add [ARKLogObserver](CoreAardvark/ARKLogObserver.h) to the default [ARKLogDistributor](CoreAardvark/ARKLogDistributor.h).
- Xcode 8.0 or later
- iOS 8 or later
We’re glad you’re interested in Aardvark, and we’d love to see where you take it. Please read our [contributing guidelines](Contributing.md) prior to submitting a Pull Request.
Thanks, and happy logging!
*Note that all licence references and agreements mentioned in the Aardvark README section above are relevant to that project's source code only.