-
Notifications
You must be signed in to change notification settings - Fork 51
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
error: virtual filesystem overlay file 'xxx/all-product-headers.yaml' not found #172
Comments
Consumer Xcode Logs Showing All Messages |
Producer Xcode Logs Showing All Messages |
When I test the producer and consumer on the same project, which means it has the same project path and Xcode DerivedData path, after the above steps, the consumer also hit all caches certainly, and the So I guess the root cause is the debugging information in the binary contains absolute paths. Could you please reproduce the scene, and give me a solution? Thank you:) |
I submitted the issue to apple/swift about this. |
My integration setup
[✅] CocoaPods cocoapods-xcremotecache plugin
[ ] Automatic integration using
xcprepare integrate ...
[ ] Manual integration
[ ] Carthage
Expected/desired behavior
consumer can use
po
expression when debug in Xcode.Minimal reproduction of the problem with instructions
There has two same local git repo, with different folder path, one for producer, another for consumer.
STEPS:
producer
project. It runpo
expression well.consumer
project, it hit all caches and run well. However, when I runpo
expression, it log error.The folder name called
iOSTemplate-cdzlxgwuidvlmxbkkaadsgdulfkn
is producer's derivedData folder.Then I checked the XCRemoteCache artifacts caches using
grep -r iOSTemplate-cdzlxgwuidvlmxbkkaadsgdulfkn /Users/lyon/Library/Caches/XCRemoteCache/10.1.125.142/cache/iOSTemplate/file/4ffc488943069a16d3146f6e131d6e9c/RxSwift
, and found the absolute path contains in binary files.And I found nothing about
all-product-headers.yaml
in the cache, it makes me confused.Pods/Carthage file
Environment
The text was updated successfully, but these errors were encountered: