You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One is not able to run the po command in LLDB when linked to recent versions of mParticle.
Environment
Xcode 14.2.0
mParticle-Apple-SDK 8.14.1
Steps to reproduce
Integrate mParticle 8.14.1 via SPM in your project (8.13.0 and above should be affected as well)
Add a breakpoint somewhere
Launch your project in an iOS simulator
Make sure it reaches the breakpoint
Use the po command in the debugger. For example po foo to print the description of foo
Actual Result:
The debugger command fails:
(lldb) po foo
error: expression failed to parse:
error: virtual filesystem overlay file '/Users/runner/Library/Developer/Xcode/DerivedData/mParticle-Apple-SDK-bqixaejagpemcucwbbovvcavmgpa/Build/Intermediates.noindex/ArchiveIntermediates/mParticle-Apple-SDK/IntermediateBuildFilesPath/mParticle-Apple-SDK.build/Release-iphonesimulator/mParticle-Apple-SDK.build/all-product-headers.yaml' not found
error: virtual filesystem overlay file '/Users/runner/Library/Developer/Xcode/DerivedData/mParticle-Apple-SDK-bqixaejagpemcucwbbovvcavmgpa/Build/Intermediates.noindex/ArchiveIntermediates/mParticle-Apple-SDK/IntermediateBuildFilesPath/mParticle-Apple-SDK.build/Release-iphonesimulator/mParticle-Apple-SDK.build/all-product-headers.yaml' not found
error: couldn't IRGen expression. Please check the above error messages for possible root causes.
Expected result
The debugger command should be executed without any error.
One is not able to run the
po
command in LLDB when linked to recent versions of mParticle.Environment
Steps to reproduce
po
command in the debugger. For examplepo foo
to print the description offoo
Actual Result:
The debugger command fails:
Expected result
The debugger command should be executed without any error.
Sample project
mParticleAbsolutePathDemo.zip
mParticleAbsolutePathDemoTests.testExample()
po foo
in the debuggerNotes
-no-serialize-debugging-options
could resolve this issue.The text was updated successfully, but these errors were encountered: