Skip to content

Fix issue with IRGen #134

New issue

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

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

Already on GitHub? # to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

brendan-guegan-orange
Copy link

During debugging session, with the use of pods installed via Cocoapods-binary, the console in Xcode displays error messages while executing following expression:
po self

The error looks the following one:

Printing description of self:
expression produced error: error: virtual filesystem overlay file '/path/to/project/Pods/build/Pods.build/Release-iphoneos/Charts.build/all-product-headers.yaml' not found

error: couldn't IRGen expression. Please check the above error messages for possible root causes.

The issue is not related to Charts pod, but to every pod used.

To fix the issue, I just removed the line that delete the build folder generated during the precompiling of pods. This folder contains for each pod, the all-product-headers.yaml expected by Xcode.

During debugging session, with the use of pods installed via Cocoapods-binary, the console in Xcode displays error messages while executing following expression:
`po self`

The error looks the following one:
```
Printing description of self:
expression produced error: error: virtual filesystem overlay file '/path/to/project/Pods/build/Pods.build/Release-iphoneos/Charts.build/all-product-headers.yaml' not found

error: couldn't IRGen expression. Please check the above error messages for possible root causes.
```

The issue is not related to Charts pod, but to every pod used.

To fix the issue, I just removed the line that delete the build folder generated during the precompiling of pods. THis folder contains for each pod, the `all-product-headers.yaml` expected by Xcode.
@jamesdouble
Copy link

any update for this issue?

@brendan-guegan-orange
Copy link
Author

any update for this issue?

Hello @jamesdouble, I don't know how to add a reviewer to this pull request and how to restart the continuous integration job.

@jamesdouble
Copy link

@brendan-guegan-orange ,
I see. Seems this repo not maintain anymore.
Is there anyway to fix this bug without changing source code?
Like, change Xcode build settings..

@brendan-guegan-orange
Copy link
Author

@jamesdouble
I don't think so, cocoapods-binary seems to create its own Xcode project to build the frameworks, and the all-product-headers.yaml files are removed at the end of the prebuidling, so changing anything in Xcode won't have any effect.

@muukii
Copy link

muukii commented Dec 5, 2020

Is there any fork that continues maintaining?
This gem is really useful. if I could, I'd like to sponsor this maintainer.

@muukii
Copy link

muukii commented Dec 12, 2020

I thought this fixing does not work well.
Because we need to commit the files in the build directory to keep all-product-headers.yaml.
And also, LLDB uses an absolute path to run command such as po, this also makes us it can not share the binary.
I need to find another idea out.

@muukii
Copy link

muukii commented Dec 12, 2020

@muukii
Copy link

muukii commented Dec 12, 2020

I think SWIFT_SERIALIZE_DEBUGGING_OPTIONS = NO fixes this issue.

@jamesdouble
Copy link

I think SWIFT_SERIALIZE_DEBUGGING_OPTIONS = NO fixes this issue.

Where should I put this setting?
my target or pods Target?

@muukii
Copy link

muukii commented Dec 23, 2020

@jamesdouble
Pods Target that we make as binary.
but, I've tried that and it didn't work well.

This commit is a copy of the one made in this pull request : leavez#73 (reference).
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants