Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on 12-12-2017 09:24 AM - edited on 10-12-2018 02:09 PM by Nina.Wolinsky
If you are using v.4.4.0.x iOS agent with latest Xcode 9beta 6, you might see the following warning from Apple's Main Thread Checker.
AppDynamics crash ================================================================= Main Thread Checker: UI API called on a background thread: -[UIApplication isProtectedDataAvailable] PID: 16226, TID: 917031, Thread name: (none), Queue name: com.appdynamics.EumInstrumentation.BeaconDispatcher, QoS: 0 Backtrace: 4 Workplace 0x000000010a1386ea +[ADEumInstrumentation isProtectedDataAvailable] + 72 5 Workplace 0x000000010a12258a __40-[ADEumBeaconDispatcher flushBeaconsNow]_block_invoke + 40 6 libdispatch.dylib 0x00000001135353f7 _dispatch_call_block_and_release + 12 7 libdispatch.dylib 0x000000011353643c _dispatch_client_callout + 8 8 libdispatch.dylib 0x000000011353e95b _dispatch_queue_serial_drain + 1162 9 libdispatch.dylib 0x000000011353f2df _dispatch_queue_invoke + 336 10 libdispatch.dylib 0x000000011353b07d _dispatch_queue_override_invoke + 733 11 libdispatch.dylib 0x00000001135421f9 _dispatch_root_queue_drain + 772 12 libdispatch.dylib 0x0000000113541e97 _dispatch_worker_thread3 + 132 13 libsystem_pthread.dylib 0x00000001139fa5a2 _pthread_wqthread + 1299 14 libsystem_pthread.dylib 0x00000001139fa07d start_wqthread + 13
These types of issues are now displayed in Xcode 9 as purple issues - more than warnings but less than fatal errors.
In conversations with people that have had some knowledge of decisions at Apple, it appears that they were originally going to make these hard errors, but it appears that Flurry has the same problem and Apple seemed to be unwilling to stop apps containing Flurry - just too many. As people move to Xcode 9 they will start seeing these warnings as well and have questions.
As this is a warning this should not crash the application. This issue has been identified and has been worked on. The fix is going to be available in v4.4.1.
___________________________________________________________________________
Do you have a question or need clarification? [Post Your Comment] Below.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form