.xcworkspacefile in lieu of the .
xcodeprojfile to ensure
BugsplatMac.frameworkis included in your build.
carthageto build the framework and drag the built
BugsplatMac.frameworkinto your Xcode project.
BugsplatMac.frameworkfrom your window in the
Finderinto your project in Xcode and move it to the desired location in the
Create groups for any added foldersand set the checkmark for your target. Then click
Add Build Phasebutton at the bottom and choose
Add Copy Files.
Frameworksfrom the Destination list.
BugsplatMacfrom the Project Navigator left sidebar to the list in the new Copy Files phase.
DATABASE_NAMEwith your BugSplat database.
~/.bugsplat.conffile to store your Bugsplat credentials
upload-archive.shscript located in
Bugsplat.framework/Versions/A/Resourcesas an Archive Post-action in your build scheme. The script will be invoked when archiving completes which will upload the .xcarchive to BugSplat for processing. You can view the script output in
/tmp/bugsplat-upload.log. To share amongst your team, mark the scheme as Shared.
bugsplat-logoin the main app bundle or asset catalog
NOin order to prevent the name and email fields from displaying in the crash reporter UI
YESin order to send crash reports to the server automatically without presenting the crash reporter dialogue. Defaults to
YESto save and restore the user's name and email when presenting the crash reporter dialogue. Defaults to
expirationTimeIntervalto a desired value (in seconds) whereby if the difference in time between when the crash occurred and next launch is greater than the set expiration time, auto send the report without presenting the crash reporter dialogue. Defaults to
-1, which represents no expiration.
BugsplatStartupManagerDelegatethat can be implemented to provide an attachment to be uploaded.
-sectcreate __TEXT __info_plist "$(SRCROOT)/BugsplatTesterCLI/Info.plist"
@executable_path/to "Runtime Search Paths" build setting
BugsplatTester.xcworkspacefile. Edit the current scheme and uncheck Debug executable in the Run section, close the scheme editor and run the application.
.../Products/Applications. BugSplat will display function names and line numbers for all crashes posted from this executable.