Skip to content
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: The file “Info.plist” couldn’t be opened #73

Closed
phimage opened this issue Jul 31, 2019 · 2 comments · Fixed by #77
Closed

Error: The file “Info.plist” couldn’t be opened #73

phimage opened this issue Jul 31, 2019 · 2 comments · Fixed by #77
Labels
help wanted Extra attention is needed question Further information is requested

Comments

@phimage
Copy link

phimage commented Jul 31, 2019

I have an issue with #69, #70
in added verifyBundleVersion function
I have plistURL value "file:///XXXX/Dependencies/macOS/Result.framework/Info.plist"
and there is no "Info.plist" at all here so reading the file launch an error

I have one into "file:///XXXX/Dependencies/macOS/Result.framework/Versions/A/Resources/Info.plist"

only have symbolic link and Versions

Headers -> Versions/Current/Headers
Modules -> Versions/Current/Modules
Resources -> Versions/Current/Resources
Result -> Versions/Current/Result

The framework has been build using carthage 0.33.0 as I see in the log after removing accio cache

I use Xcode 10.3 so maybe something change, because I have old carthage build by me with command line, with an Info.plist at framework root folder

So to reproduce accio cache must be removed

Maybe it is a carthage issue if the Info.plist must be at root, but if not mandatory this is an accio issue

@Jeehut
Copy link
Contributor

Jeehut commented Aug 5, 2019

@mrylmz Do you know more about this? Sounds like it has to do with something we talked about recently ...

@Jeehut Jeehut added help wanted Extra attention is needed question Further information is requested labels Aug 5, 2019
@mrylmz
Copy link
Contributor

mrylmz commented Aug 22, 2019

Making the Bundle verification optional could be a short term solution here, the carthage builds should always include the correct bundle version for deployment. For a reasonable stable solution we should investigate some time in inspecting the framework specification from apple.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants