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.

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

UI API being called from background thread. #91

Closed
rickbdotcom opened this Issue Jun 9, 2017 · 70 comments

Comments

Projects
None yet
@rickbdotcom

rickbdotcom commented Jun 9, 2017

Using the new main thread checker in Xcode 9.

Main Thread Checker: UI API called on a background thread: -[UIApplication statusBarOrientation]
PID: 5551, TID: 36888, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4 Flurry_iOS_SDK 0x00000001035fcb70 +[FlurryiOSUtil canvasInLandscapeRight] + 55
5 Flurry_iOS_SDK 0x00000001035fcb1f +[FlurryiOSUtil canvasInLandscape] + 31
6 Flurry_iOS_SDK 0x00000001035e9433 +[FlurryUtil canvasInLandscape] + 44
7 Flurry_iOS_SDK 0x00000001035d3ef6 -[FlurrySession data] + 2739
8 Flurry_iOS_SDK 0x00000001035d17cf +[FlurrySession addToSavedSessions:] + 169
9 Flurry_iOS_SDK 0x00000001035d0b9d -[FlurrySession recordCrashedRecordSet:] + 1206
10 Flurry_iOS_SDK 0x00000001035bcdfa __67-[FlurryImpl crashedFrameLogProcessingCompleteWithEntityRecordSet:]_block_invoke + 62
11 libdispatch.dylib 0x000000010b7856dd _dispatch_call_block_and_release + 12
12 libdispatch.dylib 0x000000010b7866c8 _dispatch_client_callout + 8
13 libdispatch.dylib 0x000000010b78f217 _dispatch_queue_serial_drain + 1272
14 libdispatch.dylib 0x000000010b78fc6c _dispatch_queue_invoke + 342
15 libdispatch.dylib 0x000000010b78b4ab _dispatch_queue_override_invoke + 755
16 libdispatch.dylib 0x000000010b792ef4 _dispatch_root_queue_drain + 783
17 libdispatch.dylib 0x000000010b792b82 _dispatch_worker_thread4 + 54
18 libsystem_pthread.dylib 0x000000010bbd95a2 _pthread_wqthread + 1299
19 libsystem_pthread.dylib 0x000000010bbd907d start_wqthread + 13
2017-06-09 13:31:13.650071-0500 Production[5551:36888] [reports] Main Thread Checker: UI API called on a background thread: -[UIApplication statusBarOrientation]
PID: 5551, TID: 36888, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4 Flurry_iOS_SDK 0x00000001035fcb70 +[FlurryiOSUtil canvasInLandscapeRight] + 55
5 Flurry_iOS_SDK 0x00000001035fcb1f +[FlurryiOSUtil canvasInLandscape] + 31
6 Flurry_iOS_SDK 0x00000001035e9433 +[FlurryUtil canvasInLandscape] + 44
7 Flurry_iOS_SDK 0x00000001035d3ef6 -[FlurrySession data] + 2739
8 Flurry_iOS_SDK 0x00000001035d17cf +[FlurrySession addToSavedSessions:] + 169
9 Flurry_iOS_SDK 0x00000001035d0b9d -[FlurrySession recordCrashedRecordSet:] + 1206
10 Flurry_iOS_SDK 0x00000001035bcdfa __67-[FlurryImpl crashedFrameLogProcessingCompleteWithEntityRecordSet:]_block_invoke + 62
11 libdispatch.dylib 0x000000010b7856dd _dispatch_call_block_and_release + 12
12 libdispatch.dylib 0x000000010b7866c8 _dispatch_client_callout + 8
13 libdispatch.dylib 0x000000010b78f217 _dispatch_queue_serial_drain + 1272
14 libdispatch.dylib 0x000000010b78fc6c _dispatch_queue_invoke + 342
15 libdispatch.dylib 0x000000010b78b4ab _dispatch_queue_override_invoke + 755
16 libdispatch.dylib 0x000000010b792ef4 _dispatch_root_queue_drain + 783
17 libdispatch.dylib 0x000000010b792b82 _dispatch_worker_thread4 + 54
18 libsystem_pthread.dylib 0x000000010bbd95a2 _pthread_wqthread + 1299
19 libsystem_pthread.dylib 0x000000010bbd907d start_wqthread + 13

@kolyuchiy

This comment has been minimized.

Show comment
Hide comment
@kolyuchiy

kolyuchiy Jun 16, 2017

One more stack trace

runtime: UI API called from background thread: -[UIApplication applicationState] must be called from main thread only

Thread 11
#0	0x000000010b641e3f in +[FlurryiOSUtil isInBackground] ()
#1	0x000000010b631489 in +[FlurryUtil isInBackground] ()
#2	0x000000010b658766 in -[FlurryDataSenderBase performRetransmitNotSentBlocks] ()
#3	0x000000011760b6dd in _dispatch_call_block_and_release ()
#4	0x000000011760c6c8 in _dispatch_client_callout ()
#5	0x0000000117615217 in _dispatch_queue_serial_drain ()
#6	0x0000000117615c6c in _dispatch_queue_invoke ()
#7	0x00000001176114ab in _dispatch_queue_override_invoke ()
#8	0x0000000117618ef4 in _dispatch_root_queue_drain ()
#9	0x0000000117618b82 in _dispatch_worker_thread4 ()
#10	0x0000000117a5f5a2 in _pthread_wqthread ()
#11	0x0000000117a5f07d in start_wqthread ()

kolyuchiy commented Jun 16, 2017

One more stack trace

runtime: UI API called from background thread: -[UIApplication applicationState] must be called from main thread only

Thread 11
#0	0x000000010b641e3f in +[FlurryiOSUtil isInBackground] ()
#1	0x000000010b631489 in +[FlurryUtil isInBackground] ()
#2	0x000000010b658766 in -[FlurryDataSenderBase performRetransmitNotSentBlocks] ()
#3	0x000000011760b6dd in _dispatch_call_block_and_release ()
#4	0x000000011760c6c8 in _dispatch_client_callout ()
#5	0x0000000117615217 in _dispatch_queue_serial_drain ()
#6	0x0000000117615c6c in _dispatch_queue_invoke ()
#7	0x00000001176114ab in _dispatch_queue_override_invoke ()
#8	0x0000000117618ef4 in _dispatch_root_queue_drain ()
#9	0x0000000117618b82 in _dispatch_worker_thread4 ()
#10	0x0000000117a5f5a2 in _pthread_wqthread ()
#11	0x0000000117a5f07d in start_wqthread ()
@tomasz-czyzak

This comment has been minimized.

Show comment
Hide comment
@tomasz-czyzak

tomasz-czyzak Jul 27, 2017

Flurry 8.1.0 Xcode9 beta3

=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication statusBarOrientation]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8ab70 +[FlurryiOSUtil canvasInLandscapeRight] + 55
5   Flurry_iOS_SDK                      0x0000000108b8ab1f +[FlurryiOSUtil canvasInLandscape] + 31
6   Flurry_iOS_SDK                      0x0000000108b77433 +[FlurryUtil canvasInLandscape] + 44
7   Flurry_iOS_SDK                      0x0000000108b61ef6 -[FlurrySession data] + 2739
8   Flurry_iOS_SDK                      0x0000000108b5f7cf +[FlurrySession addToSavedSessions:] + 169
9   Flurry_iOS_SDK                      0x0000000108b5eb9d -[FlurrySession recordCrashedRecordSet:] + 1206
10  Flurry_iOS_SDK                      0x0000000108b4adfa __67-[FlurryImpl crashedFrameLogProcessingCompleteWithEntityRecordSet:]_block_invoke + 62
11  libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
12  libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
13  libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
14  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
15  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
16  libdispatch.dylib                   0x0000000111e07d79 _dispatch_root_queue_drain + 785
17  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
18  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
19  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13
2017-07-27 19:16:56.559934+0200 XXXAPP[84499:4741162] [reports] Main Thread Checker: UI API called on a background thread: -[UIApplication statusBarOrientation]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8ab70 +[FlurryiOSUtil canvasInLandscapeRight] + 55
5   Flurry_iOS_SDK                      0x0000000108b8ab1f +[FlurryiOSUtil canvasInLandscape] + 31
6   Flurry_iOS_SDK                      0x0000000108b77433 +[FlurryUtil canvasInLandscape] + 44
7   Flurry_iOS_SDK                      0x0000000108b61ef6 -[FlurrySession data] + 2739
8   Flurry_iOS_SDK                      0x0000000108b5f7cf +[FlurrySession addToSavedSessions:] + 169
9   Flurry_iOS_SDK                      0x0000000108b5eb9d -[FlurrySession recordCrashedRecordSet:] + 1206
10  Flurry_iOS_SDK                      0x0000000108b4adfa __67-[FlurryImpl crashedFrameLogProcessingCompleteWithEntityRecordSet:]_block_invoke + 62
11  libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
12  libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
13  libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
14  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
15  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
16  libdispatch.dylib                   0x0000000111e07d79 _dispatch_root_queue_drain + 785
17  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
18  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
19  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication isRegisteredForRemoteNotifications]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8b95f +[FlurryiOSUtil isNotificationsSettingsEnabled] + 55
5   Flurry_iOS_SDK                      0x0000000108b5ab98 -[FlurrySession isPushNotificationSettingEnabled] + 29
6   Flurry_iOS_SDK                      0x0000000108b63f9b -[FlurrySession dataForSessions:] + 2780
7   Flurry_iOS_SDK                      0x0000000108b5bcbc -[FlurrySession dataForSending:] + 19
8   Flurry_iOS_SDK                      0x0000000108b8c2f4 -[FlurryDataSender sendSessionsData:withCompletionHandler:] + 266
9   Flurry_iOS_SDK                      0x0000000108b60cd3 -[FlurrySession sendSessionsToServerIncludingCurrentSession:withCompletionHandler:] + 1659
10  Flurry_iOS_SDK                      0x0000000108b6062a -[FlurrySession sendSessionsToServerForCreateSession] + 280
11  Flurry_iOS_SDK                      0x0000000108b48df9 __50-[FlurryImpl sendSessionsToServerForCreateSession]_block_invoke + 52
12  libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
13  libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
14  libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
15  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
16  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
17  libdispatch.dylib                   0x0000000111e07d79 _dispatch_root_queue_drain + 785
18  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
19  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
20  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13
2017-07-27 19:16:56.724773+0200 XXXAPP[84499:4741162] [reports] Main Thread Checker: UI API called on a background thread: -[UIApplication isRegisteredForRemoteNotifications]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8b95f +[FlurryiOSUtil isNotificationsSettingsEnabled] + 55
5   Flurry_iOS_SDK                      0x0000000108b5ab98 -[FlurrySession isPushNotificationSettingEnabled] + 29
6   Flurry_iOS_SDK                      0x0000000108b63f9b -[FlurrySession dataForSessions:] + 2780
7   Flurry_iOS_SDK                      0x0000000108b5bcbc -[FlurrySession dataForSending:] + 19
8   Flurry_iOS_SDK                      0x0000000108b8c2f4 -[FlurryDataSender sendSessionsData:withCompletionHandler:] + 266
9   Flurry_iOS_SDK                      0x0000000108b60cd3 -[FlurrySession sendSessionsToServerIncludingCurrentSession:withCompletionHandler:] + 1659
10  Flurry_iOS_SDK                      0x0000000108b6062a -[FlurrySession sendSessionsToServerForCreateSession] + 280
11  Flurry_iOS_SDK                      0x0000000108b48df9 __50-[FlurryImpl sendSessionsToServerForCreateSession]_block_invoke + 52
12  libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
13  libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
14  libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
15  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
16  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
17  libdispatch.dylib                   0x0000000111e07d79 _dispatch_root_queue_drain + 785
18  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
19  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
20  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13
2017-07-27 19:16:56.840544+0200 XXXAPP[84499:4741153] [WC] already in progress or activated
2017-07-27 19:16:56.838643+0200 XXXAPP[84499:4741157] [WC] -[WCSession onqueue_handleUpdateSessionState:]_block_invoke dropping as pairingIDs no longer match. pairingID (null), client pairingID: (null)
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8b90f +[FlurryiOSUtil isInBackground] + 55
5   Flurry_iOS_SDK                      0x0000000108b772f3 +[FlurryUtil isInBackground] + 44
6   Flurry_iOS_SDK                      0x0000000108ba243f -[FlurryDataSenderBase performRetransmitNotSentBlocks] + 29
7   libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
8   libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
9   libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
10  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
11  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
12  libdispatch.dylib                   0x0000000112017-07-27 19:16:56.847010+0200 XXXAPP[84499:4741157] [WC] WCSession is not paired
1e07d79 _dispatch_root_queue_drain + 785
13  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
14  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
15  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13
2017-07-27 19:16:56.858153+0200 XXXAPP[84499:4741162] [reports] Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8b90f +[FlurryiOSUtil isInBackground] + 55
5   Flurry_iOS_SDK                      0x0000000108b772f3 +[FlurryUtil isInBackground] + 44
6   Flurry_iOS_SDK                      0x0000000108ba243f -[FlurryDataSenderBase performRetransmitNotSentBlocks] + 29
7   libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
8   libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
9   libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
10  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
11  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
12  libdispatch.dylib                   0x0000000111e07d79 _dispatch_root_queue_drain + 785
13  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
14  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
15  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13

tomasz-czyzak commented Jul 27, 2017

Flurry 8.1.0 Xcode9 beta3

=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication statusBarOrientation]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8ab70 +[FlurryiOSUtil canvasInLandscapeRight] + 55
5   Flurry_iOS_SDK                      0x0000000108b8ab1f +[FlurryiOSUtil canvasInLandscape] + 31
6   Flurry_iOS_SDK                      0x0000000108b77433 +[FlurryUtil canvasInLandscape] + 44
7   Flurry_iOS_SDK                      0x0000000108b61ef6 -[FlurrySession data] + 2739
8   Flurry_iOS_SDK                      0x0000000108b5f7cf +[FlurrySession addToSavedSessions:] + 169
9   Flurry_iOS_SDK                      0x0000000108b5eb9d -[FlurrySession recordCrashedRecordSet:] + 1206
10  Flurry_iOS_SDK                      0x0000000108b4adfa __67-[FlurryImpl crashedFrameLogProcessingCompleteWithEntityRecordSet:]_block_invoke + 62
11  libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
12  libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
13  libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
14  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
15  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
16  libdispatch.dylib                   0x0000000111e07d79 _dispatch_root_queue_drain + 785
17  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
18  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
19  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13
2017-07-27 19:16:56.559934+0200 XXXAPP[84499:4741162] [reports] Main Thread Checker: UI API called on a background thread: -[UIApplication statusBarOrientation]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8ab70 +[FlurryiOSUtil canvasInLandscapeRight] + 55
5   Flurry_iOS_SDK                      0x0000000108b8ab1f +[FlurryiOSUtil canvasInLandscape] + 31
6   Flurry_iOS_SDK                      0x0000000108b77433 +[FlurryUtil canvasInLandscape] + 44
7   Flurry_iOS_SDK                      0x0000000108b61ef6 -[FlurrySession data] + 2739
8   Flurry_iOS_SDK                      0x0000000108b5f7cf +[FlurrySession addToSavedSessions:] + 169
9   Flurry_iOS_SDK                      0x0000000108b5eb9d -[FlurrySession recordCrashedRecordSet:] + 1206
10  Flurry_iOS_SDK                      0x0000000108b4adfa __67-[FlurryImpl crashedFrameLogProcessingCompleteWithEntityRecordSet:]_block_invoke + 62
11  libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
12  libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
13  libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
14  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
15  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
16  libdispatch.dylib                   0x0000000111e07d79 _dispatch_root_queue_drain + 785
17  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
18  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
19  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication isRegisteredForRemoteNotifications]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8b95f +[FlurryiOSUtil isNotificationsSettingsEnabled] + 55
5   Flurry_iOS_SDK                      0x0000000108b5ab98 -[FlurrySession isPushNotificationSettingEnabled] + 29
6   Flurry_iOS_SDK                      0x0000000108b63f9b -[FlurrySession dataForSessions:] + 2780
7   Flurry_iOS_SDK                      0x0000000108b5bcbc -[FlurrySession dataForSending:] + 19
8   Flurry_iOS_SDK                      0x0000000108b8c2f4 -[FlurryDataSender sendSessionsData:withCompletionHandler:] + 266
9   Flurry_iOS_SDK                      0x0000000108b60cd3 -[FlurrySession sendSessionsToServerIncludingCurrentSession:withCompletionHandler:] + 1659
10  Flurry_iOS_SDK                      0x0000000108b6062a -[FlurrySession sendSessionsToServerForCreateSession] + 280
11  Flurry_iOS_SDK                      0x0000000108b48df9 __50-[FlurryImpl sendSessionsToServerForCreateSession]_block_invoke + 52
12  libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
13  libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
14  libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
15  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
16  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
17  libdispatch.dylib                   0x0000000111e07d79 _dispatch_root_queue_drain + 785
18  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
19  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
20  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13
2017-07-27 19:16:56.724773+0200 XXXAPP[84499:4741162] [reports] Main Thread Checker: UI API called on a background thread: -[UIApplication isRegisteredForRemoteNotifications]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8b95f +[FlurryiOSUtil isNotificationsSettingsEnabled] + 55
5   Flurry_iOS_SDK                      0x0000000108b5ab98 -[FlurrySession isPushNotificationSettingEnabled] + 29
6   Flurry_iOS_SDK                      0x0000000108b63f9b -[FlurrySession dataForSessions:] + 2780
7   Flurry_iOS_SDK                      0x0000000108b5bcbc -[FlurrySession dataForSending:] + 19
8   Flurry_iOS_SDK                      0x0000000108b8c2f4 -[FlurryDataSender sendSessionsData:withCompletionHandler:] + 266
9   Flurry_iOS_SDK                      0x0000000108b60cd3 -[FlurrySession sendSessionsToServerIncludingCurrentSession:withCompletionHandler:] + 1659
10  Flurry_iOS_SDK                      0x0000000108b6062a -[FlurrySession sendSessionsToServerForCreateSession] + 280
11  Flurry_iOS_SDK                      0x0000000108b48df9 __50-[FlurryImpl sendSessionsToServerForCreateSession]_block_invoke + 52
12  libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
13  libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
14  libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
15  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
16  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
17  libdispatch.dylib                   0x0000000111e07d79 _dispatch_root_queue_drain + 785
18  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
19  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
20  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13
2017-07-27 19:16:56.840544+0200 XXXAPP[84499:4741153] [WC] already in progress or activated
2017-07-27 19:16:56.838643+0200 XXXAPP[84499:4741157] [WC] -[WCSession onqueue_handleUpdateSessionState:]_block_invoke dropping as pairingIDs no longer match. pairingID (null), client pairingID: (null)
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8b90f +[FlurryiOSUtil isInBackground] + 55
5   Flurry_iOS_SDK                      0x0000000108b772f3 +[FlurryUtil isInBackground] + 44
6   Flurry_iOS_SDK                      0x0000000108ba243f -[FlurryDataSenderBase performRetransmitNotSentBlocks] + 29
7   libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
8   libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
9   libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
10  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
11  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
12  libdispatch.dylib                   0x0000000112017-07-27 19:16:56.847010+0200 XXXAPP[84499:4741157] [WC] WCSession is not paired
1e07d79 _dispatch_root_queue_drain + 785
13  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
14  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
15  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13
2017-07-27 19:16:56.858153+0200 XXXAPP[84499:4741162] [reports] Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 84499, TID: 4741162, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000108b8b90f +[FlurryiOSUtil isInBackground] + 55
5   Flurry_iOS_SDK                      0x0000000108b772f3 +[FlurryUtil isInBackground] + 44
6   Flurry_iOS_SDK                      0x0000000108ba243f -[FlurryDataSenderBase performRetransmitNotSentBlocks] + 29
7   libdispatch.dylib                   0x0000000111dfa711 _dispatch_call_block_and_release + 12
8   libdispatch.dylib                   0x0000000111dfb7a0 _dispatch_client_callout + 8
9   libdispatch.dylib                   0x0000000111e040ad _dispatch_queue_serial_drain + 1173
10  libdispatch.dylib                   0x0000000111e04ae3 _dispatch_queue_invoke + 342
11  libdispatch.dylib                   0x0000000111e00534 _dispatch_queue_override_invoke + 739
12  libdispatch.dylib                   0x0000000111e07d79 _dispatch_root_queue_drain + 785
13  libdispatch.dylib                   0x0000000111e07a05 _dispatch_worker_thread4 + 54
14  libsystem_pthread.dylib             0x00000001122725a2 _pthread_wqthread + 1299
15  libsystem_pthread.dylib             0x000000011227207d start_wqthread + 13
@brwong20

This comment has been minimized.

Show comment
Hide comment
@brwong20

brwong20 Jul 28, 2017

Any updates on this issue? Error is definitely happening because of Xcode 9's new main thread checker.

brwong20 commented Jul 28, 2017

Any updates on this issue? Error is definitely happening because of Xcode 9's new main thread checker.

@jaz-ah

This comment has been minimized.

Show comment
Hide comment
@jaz-ah

jaz-ah Aug 1, 2017

still seeing the same w/ Xcode9 Beta4.

jaz-ah commented Aug 1, 2017

still seeing the same w/ Xcode9 Beta4.

@lucabartoletti

This comment has been minimized.

Show comment
Hide comment
@lucabartoletti

lucabartoletti Aug 3, 2017

Yes, same here. It would be nice to have those solved

lucabartoletti commented Aug 3, 2017

Yes, same here. It would be nice to have those solved

@rollinsio

This comment has been minimized.

Show comment
Hide comment
@rollinsio

rollinsio Aug 7, 2017

Contributor

We've taken care of some of these in the latest release. Specifically the statusBar issues. Some of the others have been worked on but I'm not 100% if they are in this release. We are working on it and will have the problem sorted out by launch of iOS 11 GM.

Contributor

rollinsio commented Aug 7, 2017

We've taken care of some of these in the latest release. Specifically the statusBar issues. Some of the others have been worked on but I'm not 100% if they are in this release. We are working on it and will have the problem sorted out by launch of iOS 11 GM.

@crossle

This comment has been minimized.

Show comment
Hide comment
@crossle

crossle Aug 8, 2017

Same problem, plz fix, hate the third part library issue

crossle commented Aug 8, 2017

Same problem, plz fix, hate the third part library issue

@DarkoDamjanovic

This comment has been minimized.

Show comment
Hide comment
@DarkoDamjanovic

DarkoDamjanovic Aug 30, 2017

This can also be seen easily in Runtime Analysis:

screen shot 2017-08-30 at 11 09 28

I have to admit that I sometime call Flurry from a background thread (because it should not block the main thread at all) but nevertheless all UI related stuff should be called by Flurry on the main thread.

DarkoDamjanovic commented Aug 30, 2017

This can also be seen easily in Runtime Analysis:

screen shot 2017-08-30 at 11 09 28

I have to admit that I sometime call Flurry from a background thread (because it should not block the main thread at all) but nevertheless all UI related stuff should be called by Flurry on the main thread.

@jalbano

This comment has been minimized.

Show comment
Hide comment
@jalbano

jalbano Sep 5, 2017

I'm still seeing the statusBarOrientation issue using 8.1.0

jalbano commented Sep 5, 2017

I'm still seeing the statusBarOrientation issue using 8.1.0

@samjohn

This comment has been minimized.

Show comment
Hide comment
@samjohn

samjohn Sep 5, 2017

Also seeing the issue in 8.2.0

samjohn commented Sep 5, 2017

Also seeing the issue in 8.2.0

@Svantulden

This comment has been minimized.

Show comment
Hide comment
@Svantulden

Svantulden Sep 6, 2017

I'm seeing the same issue in 8.2.0. Here the corresponding stacktrace:

=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication statusBarOrientation]
PID: 31422, TID: 2487302, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   OurApp                        0x00000001011c3b13 +[FlurryiOSUtil getStatusBarOrientation] + 55
5   OurApp                        0x00000001011c3a91 +[FlurryiOSUtil canvasInLandscapeRight] + 24
6   OurApp                        0x00000001011c3a5f +[FlurryiOSUtil canvasInLandscape] + 31
7   OurApp                        0x00000001011b0252 +[FlurryUtil canvasInLandscape] + 44
8   OurApp                        0x000000010119a3b9 -[FlurrySession data] + 2739
9   OurApp                        0x0000000101198ebd -[FlurrySession sendSessionsToServerIncludingCurrentSession:withCompletionHandler:] + 930
10  OurApp                        0x0000000101198aed -[FlurrySession sendSessionsToServerForCreateSession] + 280
11  OurApp                        0x0000000101180695 __50-[FlurryImpl sendSessionsToServerForCreateSession]_block_invoke + 52
12  libdispatch.dylib                   0x000000010b37a273 _dispatch_call_block_and_release + 12
13  libdispatch.dylib                   0x000000010b37b2b5 _dispatch_client_callout + 8
14  libdispatch.dylib                   0x000000010b382e3f _dispatch_queue_serial_drain + 654
15  libdispatch.dylib                   0x000000010b383690 _dispatch_queue_invoke + 329
16  libdispatch.dylib                   0x000000010b37fd94 _dispatch_queue_override_invoke + 477
17  libdispatch.dylib                   0x000000010b385a72 _dispatch_root_queue_drain + 568
18  libdispatch.dylib                   0x000000010b3857dc _dispatch_worker_thread3 + 119
19  libsystem_pthread.dylib             0x000000010b8315a2 _pthread_wqthread + 1299
20  libsystem_pthread.dylib             0x000000010b83107d start_wqthread + 1

Svantulden commented Sep 6, 2017

I'm seeing the same issue in 8.2.0. Here the corresponding stacktrace:

=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication statusBarOrientation]
PID: 31422, TID: 2487302, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   OurApp                        0x00000001011c3b13 +[FlurryiOSUtil getStatusBarOrientation] + 55
5   OurApp                        0x00000001011c3a91 +[FlurryiOSUtil canvasInLandscapeRight] + 24
6   OurApp                        0x00000001011c3a5f +[FlurryiOSUtil canvasInLandscape] + 31
7   OurApp                        0x00000001011b0252 +[FlurryUtil canvasInLandscape] + 44
8   OurApp                        0x000000010119a3b9 -[FlurrySession data] + 2739
9   OurApp                        0x0000000101198ebd -[FlurrySession sendSessionsToServerIncludingCurrentSession:withCompletionHandler:] + 930
10  OurApp                        0x0000000101198aed -[FlurrySession sendSessionsToServerForCreateSession] + 280
11  OurApp                        0x0000000101180695 __50-[FlurryImpl sendSessionsToServerForCreateSession]_block_invoke + 52
12  libdispatch.dylib                   0x000000010b37a273 _dispatch_call_block_and_release + 12
13  libdispatch.dylib                   0x000000010b37b2b5 _dispatch_client_callout + 8
14  libdispatch.dylib                   0x000000010b382e3f _dispatch_queue_serial_drain + 654
15  libdispatch.dylib                   0x000000010b383690 _dispatch_queue_invoke + 329
16  libdispatch.dylib                   0x000000010b37fd94 _dispatch_queue_override_invoke + 477
17  libdispatch.dylib                   0x000000010b385a72 _dispatch_root_queue_drain + 568
18  libdispatch.dylib                   0x000000010b3857dc _dispatch_worker_thread3 + 119
19  libsystem_pthread.dylib             0x000000010b8315a2 _pthread_wqthread + 1299
20  libsystem_pthread.dylib             0x000000010b83107d start_wqthread + 1
@zocario

This comment has been minimized.

Show comment
Hide comment
@zocario

zocario Sep 13, 2017

Any news about this? iOS 11 is coming next week and I still see those issues in 8.2.1.

zocario commented Sep 13, 2017

Any news about this? iOS 11 is coming next week and I still see those issues in 8.2.1.

@ko0f

This comment has been minimized.

Show comment
Hide comment
@ko0f

ko0f Sep 13, 2017

Too slow, removing SDK.

ko0f commented Sep 13, 2017

Too slow, removing SDK.

@alekplay

This comment has been minimized.

Show comment
Hide comment
@alekplay

alekplay Sep 13, 2017

It is ridiculous that this hasn't been taken care of yet. Any timeframe for when you think it'll be done?

alekplay commented Sep 13, 2017

It is ridiculous that this hasn't been taken care of yet. Any timeframe for when you think it'll be done?

@crossle

This comment has been minimized.

Show comment
Hide comment
@crossle

crossle Sep 14, 2017

Too slow, removing the SDK

crossle commented Sep 14, 2017

Too slow, removing the SDK

@DarkoDamjanovic

This comment has been minimized.

Show comment
Hide comment
@DarkoDamjanovic

DarkoDamjanovic Sep 14, 2017

The Golden Master is out, both iOS 11 and Xcode 9. We need to submit our App to Apple in the next days before the official iOS 11 launch. Please fix this as soon as possible. Today is 14th September 2017 and current version is Flurry-iOS-SDK 8.2.1. But the error is still there. Thanks.

screen shot 2017-09-14 at 11 53 41

DarkoDamjanovic commented Sep 14, 2017

The Golden Master is out, both iOS 11 and Xcode 9. We need to submit our App to Apple in the next days before the official iOS 11 launch. Please fix this as soon as possible. Today is 14th September 2017 and current version is Flurry-iOS-SDK 8.2.1. But the error is still there. Thanks.

screen shot 2017-09-14 at 11 53 41

@jkichline

This comment has been minimized.

Show comment
Hide comment
@jkichline

jkichline Sep 14, 2017

Error is still there. Seems it could be fixed by wrapping those calls in dispatch_async on the main queue...

jkichline commented Sep 14, 2017

Error is still there. Seems it could be fixed by wrapping those calls in dispatch_async on the main queue...

@DarkoDamjanovic

This comment has been minimized.

Show comment
Hide comment
@DarkoDamjanovic

DarkoDamjanovic Sep 14, 2017

@jkichline Which calls? I have removed all calls to Flurry from my project and it still happens on two API calls which the Flurry SDK somehow seems to do by itself. The last resort is to remove the Flurry SDK completely from my project. After all - it's not a big deal because I can't see anything bad happening. The problem is just that we have a zero warnings policy and Apple could complain about this.

DarkoDamjanovic commented Sep 14, 2017

@jkichline Which calls? I have removed all calls to Flurry from my project and it still happens on two API calls which the Flurry SDK somehow seems to do by itself. The last resort is to remove the Flurry SDK completely from my project. After all - it's not a big deal because I can't see anything bad happening. The problem is just that we have a zero warnings policy and Apple could complain about this.

@Svantulden

This comment has been minimized.

Show comment
Hide comment
@Svantulden

Svantulden Sep 14, 2017

Version 8.2.1 is out and contains the following changes (from the release notes):

- Fix for potential race condition during app foreground/ background transitions

Does this fix the issue? I currently don't have time to try it out myself until monday next week.

Svantulden commented Sep 14, 2017

Version 8.2.1 is out and contains the following changes (from the release notes):

- Fix for potential race condition during app foreground/ background transitions

Does this fix the issue? I currently don't have time to try it out myself until monday next week.

@jkichline

This comment has been minimized.

Show comment
Hide comment
@jkichline

jkichline Sep 14, 2017

@DarkoDamjanovic No, I meant it's not a difficult fix for Flurry devs to make. THEY need to make the change to ensure that the UIKit calls are made on the main queue.

jkichline commented Sep 14, 2017

@DarkoDamjanovic No, I meant it's not a difficult fix for Flurry devs to make. THEY need to make the change to ensure that the UIKit calls are made on the main queue.

@jkichline

This comment has been minimized.

Show comment
Hide comment
@jkichline

jkichline Sep 14, 2017

@Svantulden Nope. I just pod updated to FlurrySDK 8.2.1 and performed a clean rebuild and the errors are still there.

jkichline commented Sep 14, 2017

@Svantulden Nope. I just pod updated to FlurrySDK 8.2.1 and performed a clean rebuild and the errors are still there.

@frijole

This comment has been minimized.

Show comment
Hide comment
@frijole

frijole Sep 14, 2017

just the reminder I needed to clean up another unused dependency from our project. #thanksxcode!

frijole commented Sep 14, 2017

just the reminder I needed to clean up another unused dependency from our project. #thanksxcode!

@abhandary

This comment has been minimized.

Show comment
Hide comment
@abhandary

abhandary Sep 14, 2017

Contributor

We are actively working on this and it will be addressed in an upcoming release.

Contributor

abhandary commented Sep 14, 2017

We are actively working on this and it will be addressed in an upcoming release.

@jcredmond

This comment has been minimized.

Show comment
Hide comment
@jcredmond

jcredmond Sep 18, 2017

You've known about this for over 3 months and the general release of iOS 11 is tomorrow. Can you at the very least give an ETA for the fix?

jcredmond commented Sep 18, 2017

You've known about this for over 3 months and the general release of iOS 11 is tomorrow. Can you at the very least give an ETA for the fix?

@dpiletski

This comment has been minimized.

Show comment
Hide comment
@dpiletski

dpiletski Sep 18, 2017

Thanks @abhandary. Waiting this upcoming release with fix for this issue. Everyone will be happy when this issue will be resolved.

dpiletski commented Sep 18, 2017

Thanks @abhandary. Waiting this upcoming release with fix for this issue. Everyone will be happy when this issue will be resolved.

@deni2s

This comment has been minimized.

Show comment
Hide comment
@deni2s

deni2s Sep 20, 2017

iOS 11 released. Not even ETA yet!?

deni2s commented Sep 20, 2017

iOS 11 released. Not even ETA yet!?

@rollinsio

This comment has been minimized.

Show comment
Hide comment
@rollinsio

rollinsio Sep 20, 2017

Contributor

We're working hard on this right now and have been for some time. For all analytics "UI" manipulations on a background thread (we never actually manipulate the UI on a background thread, but that's a different story) we should have them nailed down and out in the next release. The PRs are in and are being reviewed. Assuming no major issues pop up we should be good for the 8.3.0 release to have analytics "cleansed".

With regards to UI manipulation on background threads for ads, some of that work has been done but there is still more outstanding. All of it will not make it into the 8.3.0 release, though some will. These particular changes require some crafty thread manipulations that we want to make sure to get right and test effectively.

Thank you for your patience so far. You are all correct in that this has been "seeable" since the first beta. We're working on it (and have been for some time).

Contributor

rollinsio commented Sep 20, 2017

We're working hard on this right now and have been for some time. For all analytics "UI" manipulations on a background thread (we never actually manipulate the UI on a background thread, but that's a different story) we should have them nailed down and out in the next release. The PRs are in and are being reviewed. Assuming no major issues pop up we should be good for the 8.3.0 release to have analytics "cleansed".

With regards to UI manipulation on background threads for ads, some of that work has been done but there is still more outstanding. All of it will not make it into the 8.3.0 release, though some will. These particular changes require some crafty thread manipulations that we want to make sure to get right and test effectively.

Thank you for your patience so far. You are all correct in that this has been "seeable" since the first beta. We're working on it (and have been for some time).

@deni2s

This comment has been minimized.

Show comment
Hide comment
@deni2s

deni2s Sep 20, 2017

Thanks for update! But what is ETA for 8.3.0 then?

deni2s commented Sep 20, 2017

Thanks for update! But what is ETA for 8.3.0 then?

@DarkoDamjanovic

This comment has been minimized.

Show comment
Hide comment
@DarkoDamjanovic

DarkoDamjanovic Sep 22, 2017

FYI: I just got my App approved by Apple despite the runtime warnings created by the Flurry SDK.

DarkoDamjanovic commented Sep 22, 2017

FYI: I just got my App approved by Apple despite the runtime warnings created by the Flurry SDK.

@abhandary

This comment has been minimized.

Show comment
Hide comment
@abhandary

abhandary Oct 9, 2017

Contributor

@dzungpv where are you seeing this? the SDK is available for download and use as a Cocoapod.
https://cocoapods.org/pods/Flurry-iOS-SDK

Contributor

abhandary commented Oct 9, 2017

@dzungpv where are you seeing this? the SDK is available for download and use as a Cocoapod.
https://cocoapods.org/pods/Flurry-iOS-SDK

@dzungpv

This comment has been minimized.

Show comment
Hide comment
@dzungpv

dzungpv Oct 9, 2017

@abhandary i am not use cocapod, i download it from flurry site.

dzungpv commented Oct 9, 2017

@abhandary i am not use cocapod, i download it from flurry site.

@jianming

This comment has been minimized.

Show comment
Hide comment
@jianming

jianming Oct 9, 2017

when 8.3.0 will be out?

jianming commented Oct 9, 2017

when 8.3.0 will be out?

@JohnnyTseng

This comment has been minimized.

Show comment
Hide comment
@JohnnyTseng

JohnnyTseng Oct 10, 2017

@jianming
The answer is just right above yours, please read comments carefully
#91 (comment)

JohnnyTseng commented Oct 10, 2017

@jianming
The answer is just right above yours, please read comments carefully
#91 (comment)

@jianming

This comment has been minimized.

Show comment
Hide comment
@jianming

jianming Oct 10, 2017

on the flurry site (dashboard), I found 8.2.2. Where can I find 8.3.0?

screen shot 2017-10-10 at 9 36 28 am

jianming commented Oct 10, 2017

on the flurry site (dashboard), I found 8.2.2. Where can I find 8.3.0?

screen shot 2017-10-10 at 9 36 28 am

@agordeev

This comment has been minimized.

Show comment
Hide comment
@agordeev

agordeev Oct 11, 2017

There's still 8.2.2 version on cocoapods. Looks like you guys haven't updated trunk?

Installing Flurry-iOS-SDK 8.2.2 (was 8.2.1)

agordeev commented Oct 11, 2017

There's still 8.2.2 version on cocoapods. Looks like you guys haven't updated trunk?

Installing Flurry-iOS-SDK 8.2.2 (was 8.2.1)
@deni2s

This comment has been minimized.

Show comment
Hide comment
@deni2s

deni2s Oct 11, 2017

@agordeev read more carefully, 8.3.0 is not yet released. Should be released any time soon.

deni2s commented Oct 11, 2017

@agordeev read more carefully, 8.3.0 is not yet released. Should be released any time soon.

@jianming

This comment has been minimized.

Show comment
Hide comment
@jianming

jianming Oct 11, 2017

is that we will go to mar any time soon kind of any time soon?

As a loyal user of Flurry since the first version, I feel utterly disappointed now, maybe it is time to move on.

jianming commented Oct 11, 2017

is that we will go to mar any time soon kind of any time soon?

As a loyal user of Flurry since the first version, I feel utterly disappointed now, maybe it is time to move on.

@dkk

This comment has been minimized.

Show comment
Hide comment
@dkk

dkk Oct 12, 2017

Still no 8.3.0 release?

dkk commented Oct 12, 2017

Still no 8.3.0 release?

@dwsolberg

This comment has been minimized.

Show comment
Hide comment
@dwsolberg

dwsolberg Oct 12, 2017

You can bet that I'm not recommending any new projects use Flurry. This is too much trouble.

dwsolberg commented Oct 12, 2017

You can bet that I'm not recommending any new projects use Flurry. This is too much trouble.

@DarkoDamjanovic

This comment has been minimized.

Show comment
Hide comment
@DarkoDamjanovic

DarkoDamjanovic Oct 13, 2017

Just got the 8.3.0 release - problems solved. Thanks.

DarkoDamjanovic commented Oct 13, 2017

Just got the 8.3.0 release - problems solved. Thanks.

@jkichline

This comment has been minimized.

Show comment
Hide comment
@jkichline

jkichline Oct 13, 2017

jkichline commented Oct 13, 2017

@DarkoDamjanovic

This comment has been minimized.

Show comment
Hide comment
@DarkoDamjanovic

DarkoDamjanovic Oct 13, 2017

@jkichline No reason, to be sarcastic. Are you doing all your stuff always 100% perfect and in time? I am not from Flurry, just a user of this free service. But you could pay massive amounts of money to e.g. Mixpanel and then demand things.

Nevertheless, I will answer you: I did a pod update.
This is my current Podfile.lock line for Flurry: - Flurry-iOS-SDK/FlurrySDK (8.3.0)
Everything fine now.

Btw.: on Github is a branch named br_8.3.0.

DarkoDamjanovic commented Oct 13, 2017

@jkichline No reason, to be sarcastic. Are you doing all your stuff always 100% perfect and in time? I am not from Flurry, just a user of this free service. But you could pay massive amounts of money to e.g. Mixpanel and then demand things.

Nevertheless, I will answer you: I did a pod update.
This is my current Podfile.lock line for Flurry: - Flurry-iOS-SDK/FlurrySDK (8.3.0)
Everything fine now.

Btw.: on Github is a branch named br_8.3.0.

@jkichline

This comment has been minimized.

Show comment
Hide comment
@jkichline

jkichline Oct 13, 2017

jkichline commented Oct 13, 2017

@MrMuetze

This comment has been minimized.

Show comment
Hide comment
@MrMuetze

MrMuetze Oct 13, 2017

MrMuetze commented Oct 13, 2017

@agordeev

This comment has been minimized.

Show comment
Hide comment
@agordeev

agordeev Oct 18, 2017

I'm still experiencing the issue from time to time even after updating to 8.3.0:

Main Thread Checker: UI API called on a background thread: -[UIApplication statusBarOrientation]
PID: 6156, TID: 2109261, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000101c1f150 +[FlurryiOSUtil getStatusBarOrientation] + 56
5   Flurry_iOS_SDK                      0x0000000101c1f0b0 +[FlurryiOSUtil canvasInLandscapeRight] + 28
6   Flurry_iOS_SDK                      0x0000000101c1f070 +[FlurryiOSUtil canvasInLandscape] + 32
7   Flurry_iOS_SDK                      0x0000000101c0add8 +[FlurryUtil canvasInLandscape] + 44
8   Flurry_iOS_SDK                      0x0000000101bf4fe8 -[FlurrySession data] + 2444
9   Flurry_iOS_SDK                      0x0000000101bf2a68 +[FlurrySession addToSavedSessions:] + 188
10  Flurry_iOS_SDK                      0x0000000101bf1e58 -[FlurrySession recordCrashedRecordSet:] + 1020
11  Flurry_iOS_SDK                      0x0000000101bdbe80 __67-[FlurryImpl crashedFrameLogProcessingCompleteWithEntityRecordSet:]_block_invoke + 60
12  libdispatch.dylib                   0x00000001032c949c _dispatch_call_block_and_release + 24
13  libdispatch.dylib                   0x00000001032c945c _dispatch_client_callout + 16
14  libdispatch.dylib                   0x00000001032d8110 _dispatch_queue_serial_drain + 692
15  libdispatch.dylib                   0x00000001032cc9a4 _dispatch_queue_invoke + 332
16  libdispatch.dylib                   0x00000001032d9104 _dispatch_root_queue_drain_deferred_wlh + 424
17  libdispatch.dylib                   0x00000001032e0100 _dispatch_workloop_worker_thread + 652
18  libsystem_pthread.dylib             0x0000000182776fe0 _pthread_wqthread + 932
19  libsystem_pthread.dylib             0x0000000182776c30 start_wqthread + 4

agordeev commented Oct 18, 2017

I'm still experiencing the issue from time to time even after updating to 8.3.0:

Main Thread Checker: UI API called on a background thread: -[UIApplication statusBarOrientation]
PID: 6156, TID: 2109261, Thread name: (none), Queue name: com.Flurry.Analytics.Session, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x0000000101c1f150 +[FlurryiOSUtil getStatusBarOrientation] + 56
5   Flurry_iOS_SDK                      0x0000000101c1f0b0 +[FlurryiOSUtil canvasInLandscapeRight] + 28
6   Flurry_iOS_SDK                      0x0000000101c1f070 +[FlurryiOSUtil canvasInLandscape] + 32
7   Flurry_iOS_SDK                      0x0000000101c0add8 +[FlurryUtil canvasInLandscape] + 44
8   Flurry_iOS_SDK                      0x0000000101bf4fe8 -[FlurrySession data] + 2444
9   Flurry_iOS_SDK                      0x0000000101bf2a68 +[FlurrySession addToSavedSessions:] + 188
10  Flurry_iOS_SDK                      0x0000000101bf1e58 -[FlurrySession recordCrashedRecordSet:] + 1020
11  Flurry_iOS_SDK                      0x0000000101bdbe80 __67-[FlurryImpl crashedFrameLogProcessingCompleteWithEntityRecordSet:]_block_invoke + 60
12  libdispatch.dylib                   0x00000001032c949c _dispatch_call_block_and_release + 24
13  libdispatch.dylib                   0x00000001032c945c _dispatch_client_callout + 16
14  libdispatch.dylib                   0x00000001032d8110 _dispatch_queue_serial_drain + 692
15  libdispatch.dylib                   0x00000001032cc9a4 _dispatch_queue_invoke + 332
16  libdispatch.dylib                   0x00000001032d9104 _dispatch_root_queue_drain_deferred_wlh + 424
17  libdispatch.dylib                   0x00000001032e0100 _dispatch_workloop_worker_thread + 652
18  libsystem_pthread.dylib             0x0000000182776fe0 _pthread_wqthread + 932
19  libsystem_pthread.dylib             0x0000000182776c30 start_wqthread + 4
@rollinsio

This comment has been minimized.

Show comment
Hide comment
@rollinsio

rollinsio Oct 18, 2017

Contributor

@agordeev was this on launch, or coming out of the background? However, I believe all other occurrences have been addressed.

Contributor

rollinsio commented Oct 18, 2017

@agordeev was this on launch, or coming out of the background? However, I believe all other occurrences have been addressed.

@agordeev

This comment has been minimized.

Show comment
Hide comment
@agordeev

agordeev Oct 18, 2017

On launch, as always

agordeev commented Oct 18, 2017

On launch, as always

@joshbernfeld

This comment has been minimized.

Show comment
Hide comment
@joshbernfeld

joshbernfeld Oct 18, 2017

Fixed for me as of 8.3.0

joshbernfeld commented Oct 18, 2017

Fixed for me as of 8.3.0

@abhandary

This comment has been minimized.

Show comment
Hide comment
@abhandary

abhandary Oct 18, 2017

Contributor

@agordeev looking at the routine getStatusBarOrientation() in our code, it's pretty unlikely that it's calling into [UIApplication statusBarOrientation] from a background thread, is it possible that you're still on an older SDK?

Contributor

abhandary commented Oct 18, 2017

@agordeev looking at the routine getStatusBarOrientation() in our code, it's pretty unlikely that it's calling into [UIApplication statusBarOrientation] from a background thread, is it possible that you're still on an older SDK?

@fbeeper

This comment has been minimized.

Show comment
Hide comment
@fbeeper

fbeeper Oct 18, 2017

I can confirm 8.3.0 fixed the issue on my end, including at launch.

fbeeper commented Oct 18, 2017

I can confirm 8.3.0 fixed the issue on my end, including at launch.

@agordeev

This comment has been minimized.

Show comment
Hide comment
@agordeev

agordeev Oct 19, 2017

Nevermind, I was switching between two branches, and one of them had 8.2.1. That caused a misunderstanding.

Thanks for trying to help!

agordeev commented Oct 19, 2017

Nevermind, I was switching between two branches, and one of them had 8.2.1. That caused a misunderstanding.

Thanks for trying to help!

@rollinsio

This comment has been minimized.

Show comment
Hide comment
@rollinsio

rollinsio Oct 19, 2017

Contributor

Alright folks, I'm going to close this thread down. If, for some reason, this raises its ugly head, don't hesitate to reopen this.

Contributor

rollinsio commented Oct 19, 2017

Alright folks, I'm going to close this thread down. If, for some reason, this raises its ugly head, don't hesitate to reopen this.

@rollinsio rollinsio closed this Oct 19, 2017

@eneko

This comment has been minimized.

Show comment
Hide comment
@eneko

eneko Nov 7, 2017

Hi there,

Just upgraded to Flurry 8.3.1 via CocoaPods, running Xcode 9.1. This is the error I am getting:

=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 34979, TID: 4320513, Thread name: (none), Queue name: MBFlurryLogger, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x00000001089d0540 +[Flurry startSession:] + 1275
5   Project-Gator                       0x0000000104ecec1a +[MBAnalytics initialize] + 74
6   libobjc.A.dylib                     0x000000010f2f6a14 CALLING_SOME_+initialize_METHOD + 19
7   libobjc.A.dylib                     0x000000010f2f6dae _class_initialize + 276
8   libobjc.A.dylib                     0x000000010f2fd5e7 lookUpImpOrForward + 225
9   libobjc.A.dylib                     0x000000010f30d3d4 _objc_msgSend_uncached + 68
10  Project-Gator                       0x0000000105041a65 -[MBFlurryLogger logMessage:] + 277
11  CocoaLumberjack                     0x000000010e335981 __16-[DDLog lt_log:]_block_invoke + 50
12  libdispatch.dylib                   0x00000001113d23f7 _dispatch_call_block_and_release + 12
13  libdispatch.dylib                   0x00000001113d343c _dispatch_client_callout + 8
14  libdispatch.dylib                   0x00000001113dbaf2 _dispatch_queue_serial_drain + 1569
15  libdispatch.dylib                   0x00000001113dc2df _dispatch_queue_invoke + 336
16  libdispatch.dylib                   0x00000001113d807d _dispatch_queue_override_invoke + 733
17  libdispatch.dylib                   0x00000001113df1f9 _dispatch_root_queue_drain + 772
18  libdispatch.dylib                   0x00000001113dee97 _dispatch_worker_thread3 + 132
19  libsystem_pthread.dylib             0x000000011189b1ca _pthread_wqthread + 1387
20  libsystem_pthread.dylib             0x000000011189ac4d start_wqthread + 13
Info      01:50:56 PM »  Timer began for process: App open
Debug     01:50:56 PM »  Beginning metrics tracking for: App open
Info      01:50:57 PM »  (AppDelegate) | applicationDidBecomeActive called
Info      01:50:58 PM »  Timer stopped for process: App open, Duration (in secs): 1.794122040271759
Debug     01:50:58 PM »  Ending metrics tracking for: App open

While Flurry might not be updating the UI from the background, any access to a UI class, like UIApplication, should be done from the main thread. Seems like this is still not the case.

eneko commented Nov 7, 2017

Hi there,

Just upgraded to Flurry 8.3.1 via CocoaPods, running Xcode 9.1. This is the error I am getting:

=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 34979, TID: 4320513, Thread name: (none), Queue name: MBFlurryLogger, QoS: 0
Backtrace:
4   Flurry_iOS_SDK                      0x00000001089d0540 +[Flurry startSession:] + 1275
5   Project-Gator                       0x0000000104ecec1a +[MBAnalytics initialize] + 74
6   libobjc.A.dylib                     0x000000010f2f6a14 CALLING_SOME_+initialize_METHOD + 19
7   libobjc.A.dylib                     0x000000010f2f6dae _class_initialize + 276
8   libobjc.A.dylib                     0x000000010f2fd5e7 lookUpImpOrForward + 225
9   libobjc.A.dylib                     0x000000010f30d3d4 _objc_msgSend_uncached + 68
10  Project-Gator                       0x0000000105041a65 -[MBFlurryLogger logMessage:] + 277
11  CocoaLumberjack                     0x000000010e335981 __16-[DDLog lt_log:]_block_invoke + 50
12  libdispatch.dylib                   0x00000001113d23f7 _dispatch_call_block_and_release + 12
13  libdispatch.dylib                   0x00000001113d343c _dispatch_client_callout + 8
14  libdispatch.dylib                   0x00000001113dbaf2 _dispatch_queue_serial_drain + 1569
15  libdispatch.dylib                   0x00000001113dc2df _dispatch_queue_invoke + 336
16  libdispatch.dylib                   0x00000001113d807d _dispatch_queue_override_invoke + 733
17  libdispatch.dylib                   0x00000001113df1f9 _dispatch_root_queue_drain + 772
18  libdispatch.dylib                   0x00000001113dee97 _dispatch_worker_thread3 + 132
19  libsystem_pthread.dylib             0x000000011189b1ca _pthread_wqthread + 1387
20  libsystem_pthread.dylib             0x000000011189ac4d start_wqthread + 13
Info      01:50:56 PM »  Timer began for process: App open
Debug     01:50:56 PM »  Beginning metrics tracking for: App open
Info      01:50:57 PM »  (AppDelegate) | applicationDidBecomeActive called
Info      01:50:58 PM »  Timer stopped for process: App open, Duration (in secs): 1.794122040271759
Debug     01:50:58 PM »  Ending metrics tracking for: App open

While Flurry might not be updating the UI from the background, any access to a UI class, like UIApplication, should be done from the main thread. Seems like this is still not the case.

@eneko

This comment has been minimized.

Show comment
Hide comment
@eneko

eneko Nov 7, 2017

From the Podfile.lock:

PODS:
  - Flurry-iOS-SDK (8.3.1):
    - Flurry-iOS-SDK/FlurrySDK (= 8.3.1)
  - Flurry-iOS-SDK/FlurrySDK (8.3.1)
DEPENDENCIES:
  - Flurry-iOS-SDK (~> 8.3.0)
SPEC CHECKSUMS:
  Flurry-iOS-SDK: 912b3eb78bee559883feb3b13263437b185e8fe9

COCOAPODS: 1.3.1

eneko commented Nov 7, 2017

From the Podfile.lock:

PODS:
  - Flurry-iOS-SDK (8.3.1):
    - Flurry-iOS-SDK/FlurrySDK (= 8.3.1)
  - Flurry-iOS-SDK/FlurrySDK (8.3.1)
DEPENDENCIES:
  - Flurry-iOS-SDK (~> 8.3.0)
SPEC CHECKSUMS:
  Flurry-iOS-SDK: 912b3eb78bee559883feb3b13263437b185e8fe9

COCOAPODS: 1.3.1

@abhandary

This comment has been minimized.

Show comment
Hide comment
@abhandary

abhandary Nov 7, 2017

Contributor

@eneko It is required to call [Flurry startSession:] in application:didFinishLaunchingWithOptions: https://developer.yahoo.com/flurry/docs/integrateflurry/ios/

Contributor

abhandary commented Nov 7, 2017

@eneko It is required to call [Flurry startSession:] in application:didFinishLaunchingWithOptions: https://developer.yahoo.com/flurry/docs/integrateflurry/ios/

@eneko

This comment has been minimized.

Show comment
Hide comment
@eneko

eneko Nov 7, 2017

Ok, just verified this was an issue in our code. Thanks for the reply!

eneko commented Nov 7, 2017

Ok, just verified this was an issue in our code. Thanks for the reply!

@iOS-altima

This comment has been minimized.

Show comment
Hide comment
@iOS-altima

iOS-altima Dec 20, 2017

This did a fix for me:

dispatch_async(dispatch_get_main_queue(), ^{
    FlurrySessionBuilder *sessionBuilder = [[FlurrySessionBuilder new] withCrashReporting:YES];
    [Flurry startSession:@"YOUR_ID" withSessionBuilder:sessionBuilder];
});

iOS-altima commented Dec 20, 2017

This did a fix for me:

dispatch_async(dispatch_get_main_queue(), ^{
    FlurrySessionBuilder *sessionBuilder = [[FlurrySessionBuilder new] withCrashReporting:YES];
    [Flurry startSession:@"YOUR_ID" withSessionBuilder:sessionBuilder];
});
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment