bugsnag / bugsnag-cocoa-performance Goto Github PK

Monitor the start-up, screen loading and network requests of your iOS app and see the results in your BugSnag dashboard.

Home Page: https://docs.bugsnag.com/performance/integration-guides/ios

License: MIT License

Swift 16.80% Objective-C++ 43.57% Objective-C 18.53% C++ 0.26% Shell 0.73% Ruby 2.15% Gherkin 15.88% C 0.07% Makefile 2.01%

performance platforms bugsnag cocoa ios real-user-monitoring

bugsnag-cocoa-performance's Introduction

Performance monitoring for iOS

Monitor the start-up, screen loading and network requests of your app and see the results in your BugSnag dashboard.

Features

Reporting of app startup time
Automatic measurement of UIViewController loading times
Report NSURLSession request times

Getting started

This functionality is currently in its preview phase – please contact us for more information.

For integration instructions, see our online docs: docs.bugsnag.com/performance/ios

Pre-releases

We are currently publishing pre-1.0 releases. These releases may contain breaking changes, which are documented in the CHANGELOG.md.

Support

Read the integration guide
Search open and closed issues for similar problems
Report a bug or request a feature

License

The BugSnag Cocoa Performance SDK is free software released under the MIT License. See the LICENSE for details.

bugsnag-cocoa-performance's People

Contributors

Stargazers

Watchers

Forkers

tinder-owenthomas maxwelle lfurukawa-ml anihovhannisyanani 00mjk 5l1v3r1 square-tomb mpdifran

bugsnag-cocoa-performance's Issues

Incorrect config property for network request in documentation

Describe the bug

The Documentation

describe the network configuration property as autoInstrumentNetworkRequests but the code declares it as autoInstrumentNetwork

Environment

BugSnag Cocoa Performance version: 0.1.5
CocoaPods version: 0.1.5

Crash in iOS 14 simulator

Describe the bug

When I run my project, I get a crash in the iOS 14 simulator. All other simulators work fine. A colleague also reported the same issue on their machine using the same project, though I was unable to reproduce it in a minimal test case project.

I believe it's restricted to the simulator, though I don't have any iOS 14 devices to confirm that. I don't have any crash reports coming through from App Store Connect (though there aren't many iOS 14 devices in the wild).

Crash log

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes: 0x0000000000000001, 0x0000000000000000
VM Region Info: 0 is not in any region.  Bytes before following region: 4343136256
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      102df0000-103c68000    [ 14.5M] r-x/r-x SM=COW  ...o.app/Occasio
Termination Reason: SIGNAL 11 Segmentation fault: 11
Terminating Process: exc handler [6210]

Triggered by Thread:  0

Kernel Triage:
VM - (arg = 0x0) pmap_enter retried due to resource shortage
VM - (arg = 0x0) pmap_enter retried due to resource shortage
VM - (arg = 0x0) pmap_enter retried due to resource shortage
VM - (arg = 0x0) pmap_enter retried due to resource shortage
VM - (arg = 0x0) pmap_enter retried due to resource shortage


Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   ???                           	               0x0 ???
1   Occasio                       	       0x1031e3d54 bugsnag::BugsnagPerformanceLibrary::calledAsEarlyAsPossible() + 16 (BugsnagPerformanceLibrary.mm:27)
2   dyld_sim                      	       0x1050b9e3c ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 424
3   dyld_sim                      	       0x1050ba204 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 52
4   dyld_sim                      	       0x1050b4ab4 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, char const*, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 448
5   dyld_sim                      	       0x1050b2d18 ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 184
6   dyld_sim                      	       0x1050b2de0 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 92
7   dyld_sim                      	       0x1050a6354 dyld::initializeMainExecutable() + 216
8   dyld_sim                      	       0x1050aab98 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 4076
9   dyld                          	       0x104fb3d88 dyld4::prepareSim(dyld4::RuntimeState&, char const*) + 1328
10  dyld                          	       0x104fb264c dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 276
11  dyld                          	       0x104fb1e18 start + 1964

Environment

BugSnag Performance library version: 1.1.1
BugSnag Error Monitoring library version (if any): 6.27.2
iOS/tvOS/macOS version(s): iOS 14.0.1
Simulator or physical device: Simulator
Xcode version: 15.0 (15A240d)

No support for macOS

Describe the bug

My app is a universal app that runs on iOS, iPadOS, and macOS. Because of UIKit imports (which does not exist on macOS), I cannot link this library in my app.

Steps to reproduce

Create a universal app in SwiftUI that runs on iOS, iPadOS, and macOS
Link bugsnag-cocoa-performance.
Try and archive for macOS.

Environment

BugSnag Performance library version: 1.5.0
BugSnag Error Monitoring library version (if any):
CocoaPods version: N.A
iOS/tvOS/macOS version(s): 17.4
Simulator or physical device: Physical Device
Xcode version: 15.3
Swift version (if applicable): N.A

Are view load spans intended to include the animation duration?

Describe the bug

Based on the documentation and the manual instrumentation code sample on the same page, as well as some preliminary results I'm seeing, it seems that any reported view controller loads will include the time taken to animate that view controller into place, as loadView() is called before any animations, and viewDidAppear(_:) is called after.

My concern is, if sometimes view controllers animate in, and sometimes they don't (because it might e.g. be a root view controller or be added in as a child of another view controller, and possibly motion accessibility settings can affect the duration as well), they might produce misleading results?

Crash in the SpanAttributesProvider.mm file

Crash file is attached
Crash.docx

bugsnag / bugsnag-cocoa-performance Goto Github PK

bugsnag-cocoa-performance's Introduction

Performance monitoring for iOS

Features

Getting started

Pre-releases

Support

License

bugsnag-cocoa-performance's People

Contributors

Stargazers

Watchers

Forkers

bugsnag-cocoa-performance's Issues

Describe the bug

Environment

Describe the bug

Crash log

Environment

Describe the bug

Steps to reproduce

Environment

Describe the bug

Recommend Projects

Recommend Topics

Recommend Org