Hello,

We have encountered a problem with Instabug iOS SDK when using file protection type URLFileProtection.complete.

We are developing a fintech app and our security guys requested us to use URLFileProtection.complete file protection class for all app files, that includes Instabug sqlite database too. And now we are getting quite a lot of crashes from Instabug, because it is unable to access database when app is locked. I am guessing that Instabug SDK is trying to finish some tasks in the background and if the device is locked, it crashes, because SDK cannot access the database file.

Could you help us with this issue?

Here is the stack trace of the crash that happens most offen:

Crashed: SQLQueue 0x11fe03620 for InstabugDataModel 0 libsqlite3.dylib 0x21f3cf6e0 sqlite3_finalize + 24896 1 libsqlite3.dylib 0x21f3cdf94 sqlite3_finalize + 18932 2 libsqlite3.dylib 0x21f3cd864 sqlite3_finalize + 17092 3 libsqlite3.dylib 0x21f3cbcc0 sqlite3_finalize + 10016 4 libsqlite3.dylib 0x21f3cb100 sqlite3_finalize + 7008 5 libsqlite3.dylib 0x21f3ea54c sqlite3_step + 12952 6 libsqlite3.dylib 0x21f3e7464 sqlite3_step + 432 7 CoreData 0x221c6ad50 _execute + 156 8 CoreData 0x221aca4f4 -[NSSQLiteConnection execute] + 2772 9 CoreData 0x221c81818 newFetchedRowsForFetchPlan_MT + 848 10 CoreData 0x221d20e28 _executeFetchRequest + 68 11 CoreData 0x221acd3e4 -[NSSQLFetchRequestContext executeRequestCore:] + 36 12 CoreData 0x221ac3984 -[NSSQLStoreRequestContext executeRequestUsingConnection:] + 252 13 CoreData 0x221c27870 __52-[NSSQLDefaultConnectionManager handleStoreRequest:]_block_invoke + 84 14 libdispatch.dylib 0x21e9e6484 _dispatch_client_callout + 16 15 libdispatch.dylib 0x21e9935d8 _dispatch_lane_barrier_sync_invoke_and_complete + 56 16 CoreData 0x221ac37ec -[NSSQLDefaultConnectionManager handleStoreRequest:] + 256 17 CoreData 0x221ac36a8 -[NSSQLCoreDispatchManager routeStoreRequest:] + 264 18 CoreData 0x221ac3464 -[NSSQLCore dispatchRequest:withRetries:] + 260 19 CoreData 0x221acd2d8 -[NSSQLCore processFetchRequest:inContext:] + 108 20 CoreData 0x221ac4348 -[NSSQLCore executeRequest:withContext:error:] + 496 21 CoreData 0x221c31de4 __65-[NSPersistentStoreCoordinator executeRequest:withContext:error:]_block_invoke + 1712 22 CoreData 0x221ac3254 -[NSPersistentStoreCoordinator _routeHeavyweightBlock:] + 240 23 CoreData 0x221ac3ee4 -[NSPersistentStoreCoordinator executeRequest:withContext:error:] + 860 24 CoreData 0x221acc47c -[NSManagedObjectContext executeFetchRequest:error:] + 900 25 CoreData 0x221ad070c -[NSManagedObjectContext(_NestedContextSupport) _parentObjectsForFetchRequest:inContext:error:] + 464 26 CoreData 0x221c09cec __82-[NSManagedObjectContext(_NestedContextSupport) executeRequest:withContext:error:]_block_invoke + 580 27 CoreData 0x221c0bad0 internalBlockToNSManagedObjectContextPerform + 92 28 libdispatch.dylib 0x21e9e6484 _dispatch_client_callout + 16 29 libdispatch.dylib 0x21e9935d8 _dispatch_lane_barrier_sync_invoke_and_complete + 56 30 CoreData 0x221bffd70 _perform + 268 31 CoreData 0x221ad1154 -[NSManagedObjectContext(_NestedContextSupport) executeRequest:withContext:error:] + 172 32 CoreData 0x221acc47c -[NSManagedObjectContext executeFetchRequest:error:] + 900 33 Instabug 0x105b47244 __65-[IBGEventLogger loadSnapshotSynchronouslyWithCompletionHandler:]_block_invoke (IBGEventLogger.m:93) 34 Instabug 0x105c29e3c __26-[IBGDALService readSync:]_block_invoke (IBGDALService.m:108) 35 CoreData 0x221c02e88 developerSubmittedBlockToNSManagedObjectContextPerform + 156 36 libdispatch.dylib 0x21e9e6484 _dispatch_client_callout + 16 37 libdispatch.dylib 0x21e9935d8 _dispatch_lane_barrier_sync_invoke_and_complete + 56 38 CoreData 0x221aca8b8 -[NSManagedObjectContext performBlockAndWait:] + 304 39 Instabug 0x105c29cc8 -[IBGDALService readSync:] (IBGDALService.m:109) 40 Instabug 0x105b47188 -[IBGEventLogger loadSnapshotSynchronouslyWithCompletionHandler:] (IBGEventLogger.m:90) 41 Instabug 0x105ad6b28 -[IBGSnapshotManager surveyConditionsWithCompletionHandler:] (IBGSnapshotManager.m:263) 42 Instabug 0x105b05a1c -[InstabugSurveys pendingSurveyToShowWithCompletionHandler:] (InstabugSurveys.m:238) 43 Instabug 0x105b06348 -[InstabugSurveys surveysRequestDone:isSucess:withSurveys:pausedSurveysIDs:] (InstabugSurveys.m:359) 44 Instabug 0x105b4d474 -[IBGSurveysRequest networkDone:URLSessionDataTask:response:error:responseDictionary:] (IBGSurveysRequest.m:62) 45 Instabug 0x105c23020 __51-[IBGNetwork URLSession:task:didCompleteWithError:]_block_invoke_2 + 128 46 libdispatch.dylib 0x21e9e56c8 _dispatch_call_block_and_release + 24 47 libdispatch.dylib 0x21e9e6484 _dispatch_client_callout + 16 48 libdispatch.dylib 0x21e9929b4 _dispatch_main_queue_callback_4CF$VARIANT$mp + 1068 49 CoreFoundation 0x21ef3bdd0 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 12 50 CoreFoundation 0x21ef36c98 __CFRunLoopRun + 1964 51 CoreFoundation 0x21ef361cc CFRunLoopRunSpecific + 436 52 GraphicsServices 0x2211ad584 GSEventRunModal + 100 53 UIKitCore 0x24c179054 UIApplicationMain + 212 54 Momo-prod 0x104e05174 main (AppDelegate.swift:23) 55 libdyld.dylib 0x21e9f6bb4 start + 4

Is there any chance that you all could provide static framework versions of Instabug as well as or in place of the dynamic ones? CocoaPods supports this for the past few versions. There are 2 benefits I think we'd see.

1. Any unused symbols could be removed at link time. Meaning if consumers of the SDK don't end up using the whole thing, they can end up with a smaller binary size increase from integrating Instabug.

2. This decreases the amount of dynamic linking time when the apps are being launched, which helps the app launch faster.

Thoughts?

Steps to reproduce the problem

I have added Instabug to my project using Cocoapods. I am using the latest version (7.37). I have uploaded my archive to the App Store.

Expected behavior

The build should be processed and then be available for testing on iTunes Connect.

Actual behavior

I receive an e-mail from iTunes Connect saying: "Too many symbol files - These symbols have no corresponding slice in any binary [3DB3A537-99E9-3A79-B51A-25084C271623.symbols]"

I have checked the 3DB3A537-99E9-3A79-B51A-25084C271623 UUID and it belongs to the Instabug dSYM file.

Although I need my app's dSYM file, the Instabug dSYM file should not be included. I believe the Instabug pod should work that way out of the box.

Thanks.

Steps to Reproduce the Problem

it's a user case... i don't know actually how can reproduce that. But, App try to send http request with the Instabug integrated, and server say that request received well but there are no Instabug logs for that.

99% of requests and responses logs well. Except just before crash.

Expected Behavior

don't crash

Actual Behavior

Instabug integration code

Make sure to remove your app token.

SDK Version

9.1.2

iOS Version

13.4.1

Device Model

iPhone 8 Plus

[Optional] Project That Reproduces the Issue

Parent NSManagedObjectContext must not be nil. _68-[IBGConsoleLogger loadSnapshotWithSessionId:withCompletionHandler:]_block_invoke (IBGConsoleLogger.m:154)

data:text/text;charset=utf-8,

Cause: Parent NSManagedObjectContext must not be nil.

Reported at: 2020-04-28 19:42:41 UTC

Thread 0 [Crashed]:

0 CoreFoundation 0x1a1a215f0 _exceptionPreprocess + 224 1 libobjc.A.dylib 0x1a1743bcc objc_exception_throw + 55 2 CoreData 0x1a63bacb4 -[NSManagedObjectContext setParentContext:] + 303 3 Instabug 0x101ff50f8 _68-[IBGConsoleLogger loadSnapshotWithSessionId:withCompletionHandler:]_block_invoke (IBGConsoleLogger.m:154) 4 Instabug 0x10215b4f0 _43-[IBGDALService readASync:completionBlock:]_block_invoke (IBGDALService.m:0) 5 CoreData 0x1a6464794 developerSubmittedBlockToNSManagedObjectContextPerform + 155 6 libdispatch.dylib 0x1a16e7524 _dispatch_client_callout + 15 7 libdispatch.dylib 0x1a16c4b3c _dispatch_lane_serial_drain$VARIANT$armv81 + 563 8 libdispatch.dylib 0x1a16c554c _dispatch_lane_invoke$VARIANT$armv81 + 395 9 libdispatch.dylib 0x1a16ce84c _dispatch_workloop_worker_thread + 579 10 libsystem_pthread.dylib 0x1a1738b74 _pthread_wqthread + 271 11 libsystem_pthread.dylib 0x1a173b740 $start_wqthread + 7

Steps to Reproduce the Problem

1- Configure the SDK 2- launch the app

Expected Behavior

No error / warning on the Xcode console

Actual Behavior

Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 11086, TID: 2521424, Thread name: com.apple.CoreMotion.MotionThread, Queue name: com.apple.root.default-qos.overcommit, QoS: 0
Backtrace:
4   libobjc.A.dylib                     0x00000001cab13894 <redacted> + 56
5   CoreMotion                          0x00000001d1390760 CoreMotion + 304992
6   CoreMotion                          0x00000001d1390c94 CoreMotion + 306324
7   CoreMotion                          0x00000001d1390ba4 CoreMotion + 306084
8   CoreMotion                          0x00000001d13c2384 CoreMotion + 508804
9   CoreMotion                          0x00000001d13c23e4 CoreMotion + 508900
10  CoreFoundation                      0x00000001cb8a94d8 <redacted> + 28
11  CoreFoundation                      0x00000001cb8a8dbc <redacted> + 276
12  CoreFoundation                      0x00000001cb8a3ba4 <redacted> + 1016
13  CoreFoundation                      0x00000001cb8a3494 CFRunLoopRunSpecific + 452
14  CoreFoundation                      0x00000001cb8a41f8 CFRunLoopRun + 84
15  CoreMotion                          0x00000001d13c1d1c CoreMotion + 507164
16  libsystem_pthread.dylib             0x00000001cb51e9c8 <redacted> + 132
17  libsystem_pthread.dylib             0x00000001cb51e924 _pthread_start + 52
18  libsystem_pthread.dylib             0x00000001cb526ddc thread_start + 4

Instabug integration code

Instabug.start(withToken: "yourToken",
                   invocationEvents: IBGInvocationEvent([.shake]))
BugReporting.shakingThresholdForiPhone = 3
BugReporting.shakingThresholdForiPad = 1.2

SDK Version

• 8.0.15

iOS Version

• iOS 12.1

Device Model

iPhone XS

[Optional] Project That Reproduces the Issue

We just implemented the instabug framework in our App. But we are experiencing a lot of bugs related to the StatusBar color, we made a lot of tests and its definitely Instabug's fault.

We use a ViewController based StatusBar configuration, and most view controllers have a white StatusBar. And even without accessing the instabug button, the status bar turn black in some app VCS.

One small case is when we present in a VC (white statusbar) a SFViewController (black statusbar) it changes to black (as it should) and when we dismiss the SFViewController it should change back to white. Bug with Instabug enabled it doesnt change back in some times. When it does changes it appears to be fake and without animations.

I love instabug, but with this bug its very unlikely we can push to our betas :/

Thanks! 👍

Steps to Reproduce the Problem

The crash happens intermittently. We couldn't find the exact steps to reproduce this crash. However, the crash stacktrace indicates the root cause to be method swizzling.

We started seeing this crash only after the SDK configuration changes wherein we assigned trackUserSteps to true.

Expected Behavior

App should not crash.

Actual Behavior

App is crashing sporadically.

Instabug integration code

Instabug.start(withToken: <KEY>, invocationEvents: [.shake])
Instabug.trackUserSteps = false
Instabug.reproStepsMode = .disable
CrashReporting.enabled = false
Instabug.tintColor = UIColor.Core.blue

SDK Version

9.1.6

iOS Version

13.6.1

Device Model

iPhone 11 Pro

Stack Trace

Crashed: com.apple.main-thread
0  libobjc.A.dylib                0x1a8fa2a70 objc_msgSend + 16
1  UIKitCore                      0x1ad86f320 -[UIView(Geometry) convertPoint:fromView:] + 112
2  UIKitCore                      0x1ad443b78 _UITouchConvertLocationInWindowToView + 68
3  UIKitCore                      0x1ad443b00 -[UITouch locationInView:] + 84
4  Instabug                       0x101eb7a10 _hidden#17171_ + 89 (__hidden#17209_:89)
5  Instabug                       0x101eafbe8 _hidden#16825_ + 429 (__hidden#16870_:429)
6  Instabug                       0x101eadd38 _hidden#16795_ + 81 (__hidden#16870_:81)
7  Instabug                       0x101edf900 __IBGSwizzle_sendEvent + 161 (__hidden#18590_:161)
8  UIKitCore                      0x1ad455da4 __dispatchPreprocessedEventFromEventQueue + 6688
9  UIKitCore                      0x1ad458988 __handleEventQueueInternal + 5368
10 UIKitCore                      0x1ad4508c8 __handleHIDEventFetcherDrain + 144
11 CoreFoundation                 0x1a920cd14 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
12 CoreFoundation                 0x1a920cc68 __CFRunLoopDoSource0 + 84
13 CoreFoundation                 0x1a920c3c4 __CFRunLoopDoSources0 + 188
14 CoreFoundation                 0x1a92071fc __CFRunLoopRun + 780
15 CoreFoundation                 0x1a9206bc8 CFRunLoopRunSpecific + 480
16 GraphicsServices               0x1b35e85cc GSEventRunModal + 164
17 UIKitCore                      0x1ad3b9744 UIApplicationMain + 1936
18 Compass                        0x1001abe0c launch() + 20 (main.swift:20)
19 Compass                        0x1001abcd0 main + 28 (main.swift:28)
20 libdyld.dylib                  0x1a9083384 start + 4

With the latest version of the Instabug SDK my app is killed when I put in the background (typically after 180 seconds)

I spent several days isolating the problem to this pod upgrade. The app is killed with a background assertion:

SBApplicationStateRunningReasonsKey =     (
                {
            SBApplicationStateRunningReasonAssertionIdentifierKey = "Shared Background Assertion 9 for ***";
            SBApplicationStateRunningReasonAssertionReasonKey = 4;
        }
    );

I reverted back version 8.0.8 from my last prod deploy and the app is no longer killed by iOS.

SDK Version

8.0.17 (Latest)

iOS Version

12.1.1

Device Model

iPhone X

Hello guys, I just updated Instabug SDK from v7.0.5 to v7.2.4 and Network logs stopped working

let config = URLSessionConfiguration.default
config.httpCookieStorage = HTTPCookieStorage.shared
config.httpCookieAcceptPolicy = .always
config.httpShouldSetCookies = true
Instabug.enableLogging(for: config)
session = Foundation.URLSession(configuration: config, delegate: self, delegateQueue: OperationQueue.main)

Do I have to do something extra? or its a bug on that version?

After updating to Instabug 6.3.1 (from 6.0.2) I am getting a build error:

ld: framework not found Instabug clang: error: linker command failed with exit code 1 (use -v to see invocation)

I've updated the Instabug framework through pod update. I've already tried to completely reinstall all the pods from the project. The cocoapods version that I am using is 1.1.1. Any help is much appreciated.

Steps to Reproduce the Problem

Launch an app with Instabug integrated with the debugger attached.

Expected Behavior

No warnings.

Actual Behavior

Receive some warnings in the console at app launch.

CoreData: annotation:  Failed to load optimized model at path '/.../Frameworks/Instabug.framework/InstabugResources.bundle/InstabugDataModel.momd/InstabugDataModel 18.omo'
CoreData: fault: One or more models in this application are using transformable properties with transformer names that are either unset, or set to NSKeyedUnarchiveFromDataTransformerName. Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead. At some point, Core Data will default to using "NSSecureUnarchiveFromData" when nil is specified, and transformable properties containing classes that do not support NSSecureCoding will become unreadable.
CoreData: warning: Property 'headers' on Entity 'NetworkLog' is using nil or an insecure NSValueTransformer.  Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.
CoreData: warning: Property 'requestBody' on Entity 'NetworkLog' is using nil or an insecure NSValueTransformer.  Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.
CoreData: warning: Property 'responseBody' on Entity 'NetworkLog' is using nil or an insecure NSValueTransformer.  Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.
CoreData: warning: Property 'responseHeaders' on Entity 'NetworkLog' is using nil or an insecure NSValueTransformer.  Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.
CoreData: annotation:  Failed to load optimized model at path '/.../Frameworks/Instabug.framework/InstabugResources.bundle/InstabugSurveysDataModel.momd/InstabugSurveysDataModel 3.omo'
CoreData: warning: Property 'responses' on Entity 'SurveyEvent' is using nil or an insecure NSValueTransformer.  Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.
CoreData: warning: Property 'locales' on Entity 'Survey' is using nil or an insecure NSValueTransformer.  Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.
CoreData: warning: Property 'value' on Entity 'SurveyCondition' is using nil or an insecure NSValueTransformer.  Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.
CoreData: warning: Property 'answers' on Entity 'SurveyQuestion' is using nil or an insecure NSValueTransformer.  Please switch to using "NSSecureUnarchiveFromData" or a subclass of NSSecureUnarchiveFromDataTransformer instead.
CoreData: annotation:  Failed to load optimized model at path '/.../Frameworks/Instabug.framework/InstabugResources.bundle/InstabugUserStepsDataModel.momd/UserStepsDataModel 3.omo'

Instabug integration code

Make sure to remove your app token.

SDK Version

Instabug 8.6.3

iOS Version

iOS 13.0 (17A5565b)

Device Model

Simulator

[Optional] Project That Reproduces the Issue

None.

Steps to Reproduce the Problem

Use both the custom URLsessionConfiguration and the default URLSession for making the request , at times the network logs are not appearing on the dashboard

Expected Behavior

All the network requests must be listed

Actual Behavior

Network logs are going missing

Instabug integration code

urlSessionConfig = URLSessionConfiguration.ephemeral urlSessionConfig.timeoutIntervalForRequest = 60 * 4 NetworkLogger.enableLogging(for: urlSessionConfig)

SDK Version

'Instabug', '11.4.1'

iOS Version

iOS 15.5

Device Model

iPhone 13 Pro

[Optional] Project That Reproduces the Issue

How would one handle redacting or hiding certain views when using SwiftUI?

Looking at the docs, I see that for UIKit there is:

view.instabug_privateView = true

For instance, I have some TextFields that I have sensitive information that I don't want to capture in a video or screenshot.

Any guidance much appreciated :)

Hi there, do you think you could add Slovenian Language support Localizable_slovenian.zip

Do you think you could add it to version: 8.6.3 to Xamarin Nugget package

because my app targets Android 9 and for some reason after migration to AndroidX happened in version 9 I am not able to integrate Instabug anymore into my app (I cannot access Instabug.Builder Com.Instabug.Library doesn't even exists,

Thanks for Anwsering and Best Regards