Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Crash after upgrading to v7.0.1 (FBSDKCrashHandler.m line 182) #1435

Closed
siddheshc27 opened this issue Jul 10, 2020 · 27 comments
Closed

Crash after upgrading to v7.0.1 (FBSDKCrashHandler.m line 182) #1435

siddheshc27 opened this issue Jul 10, 2020 · 27 comments

Comments

@siddheshc27
Copy link

siddheshc27 commented Jul 10, 2020 •
edited
Loading

Checklist

  • I'd updated to the latest released version of the SDK which is v7.1.1 and it started producing this crash.
  • I thought, since it's very recent version of the SDK, something must be wrong so I set back to v7.0.1 which was released In June. But this same crash is still getting reported.
  • Firebase stack trace is not of any help to understand what's going wrong.

Environment

Describe your dev environment here, giving as many details as possible. If you have them, make sure to include:

  • Xcode Version: 11.3.1

  • Swift Version: 5.1 (if issue is Swift related)

  • Installation Platform & Verison: Manual version 7.0.1

  • These are the details from Crash Log

Error:
FBSDKCrashHandler.m line 182

Stack Trace:
Crashed: com.apple.main-thread
0 libsystem_platform.dylib 0x1b54bf184 _os_unfair_lock_recursive_abort + 36
1 libsystem_platform.dylib 0x1b54bd074 _os_unfair_lock_lock_slow + 304
2 libobjc.A.dylib 0x1b54e03e8 lookUpImpOrForward + 128
3 libobjc.A.dylib 0x1b54ccd60 _objc_msgSend_uncached + 64
4 Shaadi 0x1022545a8 FBSDKSignalHandler + 182 (FBSDKCrashHandler.m:182)
5 libsystem_platform.dylib 0x1b54bf404 _sigtramp + 44
6 libobjc.A.dylib 0x1b54d6188 getMethodNoSuper_nolock(objc_class*, objc_selector*) + 44
7 libobjc.A.dylib 0x1b54e04d4 lookUpImpOrForward + 364
8 libobjc.A.dylib 0x1b54ccd60 _objc_msgSend_uncached + 64
9 StoreKit 0x1c4798dd4 __PurchaseDidSucceedNotification + 32
10 CoreFoundation 0x1b5714474 CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 28
11 CoreFoundation 0x1b57144c4 ___CFXRegistrationPost1_block_invoke + 68
12 libdispatch.dylib 0x1b545aec4 _dispatch_call_block_and_release + 32
13 libdispatch.dylib 0x1b545c33c _dispatch_client_callout + 20
14 libdispatch.dylib 0x1b5468600 _dispatch_main_queue_callback_4CF + 832
15 CoreFoundation 0x1b57376b0 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16
16 CoreFoundation 0x1b57322c8 __CFRunLoopRun + 1708
17 CoreFoundation 0x1b57318f4 CFRunLoopRunSpecific + 480
18 GraphicsServices 0x1bfb48604 GSEventRunModal + 164
19 UIKitCore 0x1b9905358 UIApplicationMain + 1944
20 Shaadi 0x100d79320 main + 17 (main.m:17)
21 libdyld.dylib 0x1b55ad2dc start + 4

We are not able to reproduce this crash at our end. But some of our users are facing it. Request you to please help us fix this.
@MauriceArikoglu
Copy link

Happens for us as well. This is crashing a production application on launch. Not cool.

@Ded77
Copy link

Ded77 commented Jul 10, 2020

It's time to migrate to ASWebAuthenticationSession…
https://developer.apple.com/documentation/authenticationservices/aswebauthenticationsession

@darsta65
Copy link

My Husband had the same issue this morning when trying to use the Waze app. It would open then close again immediately. We are driving for a few days and using Waze but didn’t have the problem until this morning. After trying things like delete and reload the app, shutting down the phone, etc, I finally solved the issue by deleting the Waze app, shutting down the phone, restarting the phone, then reloading the Waze app. It started to go through its start up questions (allow app to use location etc) and went down twice, but as soon as all the questions were answered it worked and has been on and working fine for the last 45 minutes.

@sozdayka
Copy link

My Husband had the same issue this morning when trying to use the Waze app. It would open then close again immediately. We are driving for a few days and using Waze but didn’t have the problem until this morning. After trying things like delete and reload the app, shutting down the phone, etc, I finally solved the issue by deleting the Waze app, shutting down the phone, restarting the phone, then reloading the Waze app. It started to go through its start up questions (allow app to use location etc) and went down twice, but as soon as all the questions were answered it worked and has been on and working fine for the last 45 minutes.

It's just FB fixed the problem

@joesus
Copy link
Contributor

joesus commented Jul 10, 2020

Duplicate of #1427

@joesus joesus marked this as a duplicate of #1427 Jul 10, 2020
@joesus joesus closed this as completed Jul 10, 2020
@siddheshc27
Copy link
Author

siddheshc27 commented Jul 11, 2020 •
edited
Loading

@joesus - This parent issue you mentioned doesn't look like duplicate of this one. The reason for crash & even the SDK Version is totally different there. They are talking about SDK v5.0.2 And it is v7.0.1

Are we sure about it ?

Also, can you please update whether this got fixed or not ?

@siddheshc27 siddheshc27 mentioned this issue Jul 11, 2020
Closed
5 tasks
@joesus
Copy link
Contributor

joesus commented Jul 11, 2020

@siddheshc27 are you still seeing the crash?

@siddheshc27
Copy link
Author

siddheshc27 commented Jul 11, 2020 •
edited
Loading

@joesus

Yes, our users are still facing it.

Till yesterday, it was one crash per user. But now the status is like 11 Users & 20 Crashes for the build which contains FB SDK v7.0.1. The recent one logged at 12:02 PM.

@joesus joesus reopened this Jul 11, 2020
@tianqibt
Copy link
Contributor

Thanks for reporting the issue! We are looking into it.

@tianqibt
Copy link
Contributor

tianqibt commented Jul 11, 2020 •
edited
Loading

@siddheshc27 would you please provide your app id so that we can disable it on our side to prevent crash for your production user? Thanks!

@siddheshc27
Copy link
Author

siddheshc27 commented Jul 12, 2020 •
edited
Loading

@tianqibt - Facebook App ID or AppStore Connect's App ID ?

If Facebook App ID, is it ok to share it here?

@tianqibt
Copy link
Contributor

You can share your app name here, and we will be able to find out the Facebook App ID. Also it would be helpful you can provide crash rate, pattern of those crashes, repro steps, etc.

@siddheshc27
Copy link
Author

siddheshc27 commented Jul 12, 2020 •
edited
Loading

@tianqibt

App Name: Shaadi.com: #1 Matchmaking App

38% of Total crashes are getting reported due to Facebook SDK (FBSDKCrashHandler.m line 182)

We are not able to reproduce these crashes. Attaching some information from Firebase Logs -

Stack Trace:

Crashed: com.google.GDTCORStorage
0 libsystem_platform.dylib 0x18864b1a4 _os_unfair_lock_recursive_abort + 36
1 libsystem_platform.dylib 0x1886490ac _os_unfair_lock_lock_slow + 304
2 libobjc.A.dylib 0x18866b68c lookUpImpOrForward + 128
3 libobjc.A.dylib 0x188659360 _objc_msgSend_uncached + 64
4 Shaadi 0x105e785a8 FBSDKSignalHandler + 182 (FBSDKCrashHandler.m:182)
5 libsystem_platform.dylib 0x18864b424 _sigtramp + 44
6 libobjc.A.dylib 0x18866b788 lookUpImpOrForward + 380
7 libobjc.A.dylib 0x188659360 _objc_msgSend_uncached + 64
8 Shaadi 0x105c733cc __31-[GDTCORStorage initWithCoder:]_block_invoke + 311 (GDTCORStorage.m:311)
9 libdispatch.dylib 0x1885e9fd8 _dispatch_client_callout + 20
10 libdispatch.dylib 0x1885f67f4 _dispatch_lane_barrier_sync_invoke_and_complete + 60
11 Shaadi 0x105c73330 -[GDTCORStorage initWithCoder:] + 310 (GDTCORStorage.m:310)
12 Foundation 0x188d01c60 _decodeObjectBinary + 2256
13 Foundation 0x188d010dc _decodeObject + 344
14 Foundation 0x188c08e58 -[NSKeyedUnarchiver decodeObjectForKey:] + 172
15 Foundation 0x188c08cac -[NSKeyedUnarchiver decodeObjectOfClasses:forKey:] + 356
16 Foundation 0x188c08900 -[NSCoder(Exceptions) __tryDecodeObjectForKey:error:decodeBlock:] + 104
17 Foundation 0x188c08870 -[NSCoder decodeTopLevelObjectOfClasses:forKey:error:] + 124
18 Foundation 0x188c07adc +[NSKeyedUnarchiver unarchivedObjectOfClasses:fromData:error:] + 140
19 Foundation 0x188c4fbf0 +[NSKeyedUnarchiver unarchivedObjectOfClass:fromData:error:] + 120
20 Shaadi 0x105c72d5c -[GDTCORStorage appWillForeground:] + 234 (GDTCORStorage.m:234)
21 Shaadi 0x105c6ff10 -[GDTCORLifecycle applicationWillEnterForeground:] + 100 (GDTCORLifecycle.m:100)
22 Foundation 0x188d0effc __57-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_2 + 28
23 CoreFoundation 0x18889c99c CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 28
24 CoreFoundation 0x18889c9ec ___CFXRegistrationPost1_block_invoke + 68
25 CoreFoundation 0x18889bce4 _CFXRegistrationPost1 + 396
26 CoreFoundation 0x18889b97c ___CFXNotificationPost_block_invoke + 108
27 CoreFoundation 0x188814910 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1424
28 CoreFoundation 0x18889b2ac _CFXNotificationPost + 1268
29 Foundation 0x188bfdb8c -[NSNotificationCenter postNotificationName:object:userInfo:] + 64
30 Shaadi 0x105c70ba4 -[GDTCORApplication iOSApplicationWillEnterForeground:] + 272 (GDTCORPlatform.m:272)
31 Foundation 0x188d0effc __57-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_2 + 28
32 CoreFoundation 0x18889c99c CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER + 28
33 CoreFoundation 0x18889c9ec ___CFXRegistrationPost1_block_invoke + 68
34 CoreFoundation 0x18889bce4 _CFXRegistrationPost1 + 396
35 CoreFoundation 0x18889b97c ___CFXNotificationPost_block_invoke + 108
36 CoreFoundation 0x188814910 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1424
37 CoreFoundation 0x18889b2ac _CFXNotificationPost + 1268
38 Foundation 0x188bfdb8c -[NSNotificationCenter postNotificationName:object:userInfo:] + 64
39 UIKitCore 0x18c1d9550 -[_UISceneLifecycleMonitor willEnterForeground] + 348
40 UIKitCore 0x18c1da5d8 __111-[_UIWindowSceneFBSSceneLifecycleMonitor transitionToTargetState:fromState:withTransitionContext:preparations:]_block_invoke_2 + 180
41 UIKitCore 0x18c68d518 _UIScenePerformActionsWithLifecycleActionMask + 112
42 UIKitCore 0x18c1da388 __111-[_UIWindowSceneFBSSceneLifecycleMonitor transitionToTargetState:fromState:withTransitionContext:preparations:]_block_invoke.116 + 160
43 UIKitCore 0x18c1dfc08 ___UISceneLifecycleSettingsUpdateBlockWithCanvasAndTransitionContext_block_invoke_2 + 364
44 UIKitCore 0x18c1d9e34 -[_UIWindowSceneFBSSceneLifecycleMonitor transitionToTargetState:fromState:withTransitionContext:preparations:] + 876
45 UIKitCore 0x18c1df940 ___UISceneLifecycleSettingsUpdateBlockWithCanvasAndTransitionContext_block_invoke + 356
46 UIKitCore 0x18c1e0510 __186-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]_block_invoke_2 + 144
47 UIKitCore 0x18c6a739c ___UISceneSettingsDiffActionPerformChangesWithTransitionContext_block_invoke + 28
48 UIKitCore 0x18c5b97bc +[BSAnimationSettings(UIKit) tryAnimatingWithSettings:actions:completion:] + 868
49 UIKitCore 0x18c6a7354 _UISceneSettingsDiffActionPerformChangesWithTransitionContext + 260
50 UIKitCore 0x18c1e025c __186-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]_block_invoke + 152
51 UIKitCore 0x18c6a723c _UISceneSettingsDiffActionPerformActionsWithDelayForTransitionContext + 108
52 UIKitCore 0x18c1e00b8 -[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:] + 392
53 UIKitCore 0x18c048434 __64-[UIScene scene:didUpdateWithDiff:transitionContext:completion:]_block_invoke + 640
54 UIKitCore 0x18c046ef8 -[UIScene _emitSceneSettingsUpdateResponseForCompletion:afterSceneUpdateWork:] + 256
55 UIKitCore 0x18c048164 -[UIScene scene:didUpdateWithDiff:transitionContext:completion:] + 236
56 UIKitCore 0x18c5dbb7c -[UIApplicationSceneClientAgent scene:handleEvent:withCompletion:] + 480
57 FrontBoardServices 0x18db3a918 -[FBSSceneImpl updater:didUpdateSettings:withDiff:transitionContext:completion:] + 560
58 FrontBoardServices 0x18db60ff8 __88-[FBSWorkspaceScenesClient sceneID:updateWithSettingsDiff:transitionContext:completion:]_block_invoke_2 + 136
59 FrontBoardServices 0x18db44ef4 -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 240
60 FrontBoardServices 0x18db60f14 __88-[FBSWorkspaceScenesClient sceneID:updateWithSettingsDiff:transitionContext:completion:]_block_invoke + 200
61 libdispatch.dylib 0x1885e9fd8 _dispatch_client_callout + 20
62 libdispatch.dylib 0x1885ecd1c _dispatch_block_invoke_direct + 264
63 FrontBoardServices 0x18db87254 FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK + 48
64 FrontBoardServices 0x18db86f00 -[FBSSerialQueue _queue_performNextIfPossible] + 432
65 FrontBoardServices 0x18db8746c -[FBSSerialQueue _performNextFromRunLoopSource] + 32
66 CoreFoundation 0x1888c0108 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 28
67 CoreFoundation 0x1888c005c __CFRunLoopDoSource0 + 84
68 CoreFoundation 0x1888bf7c8 __CFRunLoopDoSources0 + 184
69 CoreFoundation 0x1888ba694 __CFRunLoopRun + 1068
70 CoreFoundation 0x1888b9f40 CFRunLoopRunSpecific + 480
71 GraphicsServices 0x192b4a534 GSEventRunModal + 108
72 UIKitCore 0x18ca45580 UIApplicationMain + 1940
73 Shaadi 0x10499d320 main + 17 (main.m:17)
74 libdyld.dylib 0x188738e18 start + 4

Crash Info Entry:

Screenshot 2020-07-12 at 6 18 13 PM

@tianqibt
Copy link
Contributor

@siddheshc27 would you please provide the last 5 digits of your app id for us to confirm? Thanks!

@siddheshc27
Copy link
Author

siddheshc27 commented Jul 13, 2020 •
edited
Loading

@tianqibt - Can there be some better private place where we should carry out this exercise?

@siddheshc27
Copy link
Author

siddheshc27 commented Jul 13, 2020 •
edited
Loading

@joesus @tianqibt -

Any update on the issue fix ?

@siddheshc27
Copy link
Author

@joesus @tianqibt -

Can you please help us know about the version which is stable and not producing crashes for other apps? So that I will set back my App that version and release it for users.

@joesus
Copy link
Contributor

joesus commented Jul 13, 2020

@siddheshc27 please use the latest release 7.1.1

Also please subscribe to notifications about releases as this will help you stay on the latest, most stable versions.

https://docs.github.com/en/enterprise/2.15/user/articles/watching-and-unwatching-repositories

@joesus joesus closed this as completed Jul 13, 2020
@tianqibt
Copy link
Contributor

@siddheshc27 v6.3.0 is the version before we introduce signal handler and will not producing that crash.

@siddheshc27
Copy link
Author

siddheshc27 commented Jul 13, 2020 •
edited
Loading

@joesus -

This started with v7.1.1 itself. Initially, I'd used the same version SDK and crashes started appearing.

Did you fix the crash from server side OR you are just saying to update SDK to v7.1.1 ?

@siddheshc27
Copy link
Author

@tianqibt -

Did you happen to fix the crashes from server side ??

@tianqibt
Copy link
Contributor

@siddheshc27 please send your App ID to tianqibt@fb.com.

@siddheshc27
Copy link
Author

@tianqibt - sent.

@artud2000
Copy link

Any updates on this issue, we are observing a similar issue in our app

@crazymanish
Copy link

In case, someone looking for a solution: #1431 (comment)

@artud2000
Copy link

I fixed it by doing

[FBSDKSettings setAutoLogAppEventsEnabled:NO];

@tianqibt
Copy link
Contributor

@artud2000 would you please share the reproduce steps? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@Ded77 @joesus @crazymanish @artud2000 @MauriceArikoglu @sozdayka @siddheshc27 @tianqibt @darsta65