Profiler framework incompatible with RN 0.64.1 / Xcode 12.5
thibmaek opened this issue · 4 comments
Description
Just reproduced this on 2 machines. Trying to build a project with the profiler framework using RN 0.64.1 and Xcode 12.5 causes the app to pause on a breakpoint and crash later.
Steps to Reproduce
Steps to reproduce the behavior:
- Build an app with the profiler framework in Xcode 12.5 / RN 0.64.1
- Only way to fix is to remove profiler framework
Environment
- Model: Any MacBook
- OS: latest Big Sur
- Xcode: 12.5
iOS Device (please complete the following information):
- Model: Any simulator
- OS: 14.5
Hi, I'm facing the same problem, Macbook M1, Big Sure, RN 0.65.1...
Looks like DetoxInstruments don’t have support more..
Unable to run it on M1 at all
It looks like there are several issues in the current version.
The crash is probably related to this traceback:
* thread #3, queue = 'com.apple.activity.stream.78406', stop reason = EXC_BAD_ACCESS (code=1, address=0x70)
* frame #0: 0x00007ff833e2e6b2 libsystem_platform.dylib`_platform_strlen + 18
frame #1: 0x00007ff800c6b54e Foundation`+[NSString stringWithUTF8String:] + 29
frame #2: 0x0000000107bda65c DTXProfiler`__46-[DTXLiveLogStreamer startLoggingWithHandler:]_block_invoke(.block_descriptor=<unavailable>, entry=<unavailable>, error=<unavailable>) + 431 [opt]
frame #3: 0x00007ff816e4f1a4 LoggingSupport`___os_activity_stream_resume_with_filter_block_invoke + 235
frame #4: 0x00007ff8000859b4 libxpc.dylib`_xpc_connection_call_event_handler + 56
frame #5: 0x00007ff800085dd4 libxpc.dylib`_xpc_connection_mach_event + 1015
I've tried to troubleshoot the issue ending up with the final conclusion that latest/current versions of LoggingSupport.framework are buggy. Disabling the DTXLiveLogStreamer logic depending on ActivityStreamSPI.h fixes the crash, allowing the profiller to initialize.
Nevertheless, there is an apparently new -second- issue: the UI shows the application in the "Select application to profile" list only during some seconds in a disabled way before disappearing again, therefore, it definitively looks like there is additional work to be done in the UI for compatibility with current SDKs and Xcode.
I will try to troubleshoot this again when I have more some time.