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

Build Tool Plugin has no permissions to write in the project directory #234

Open
nrgbodya opened this issue Jan 2, 2025 · 3 comments
Open

Comments

@nrgbodya
Copy link

nrgbodya commented Jan 2, 2025

I am trying to generate Markdown file with licenses using the Build Tool Plugin. It fails with no-permissions-error. HTML and CSV file generation also doesn't work. Disabling User Script Sandboxing didn't help.

My licenses_plist.yml:

options:
  markdownPath: acknowledgements.md
  force: true

I have created a test project and included it here. I'm using Xcode 16.2.
@vladvlasov256, could you help me with that one?

Screenshot 2025-01-02 at 17 14 18

license-plist-test-markdown.zip

@vladvlasov256
Copy link
Contributor

Hi @nrgbodya!

Please, check the SPM section in the docs:
https://github.com/mono0926/LicensePlist?tab=readme-ov-file#integrate-into-build---build-tool-plugin


A few notes regarding your config:

  1. The project path is mandatory. xcodeprojPath: "license-plist-test-markdown.xcodeproj" should work for you.

  2. I think I never tested markdownPath: ..., looks like it doesn't work. So please removemarkdownPath property from the config. I recommend using prefix: Acknowledgments to have a nice result file name.

The config:

options:
  xcodeprojPath: "license-plist-test-markdown.xcodeproj"
  prefix: Acknowledgments
  force: true

After building the project you can find the output files in the derived data folder:

Screenshot 2025-01-03 at 10 36 09

Plist generation is the first part. When it's done Xcode needs to copy the files to the app build folder. It's also mentioned in the docs.

Do you want to use the result plist in a Settings.bundle? Because I can't find one in your project.

@nrgbodya
Copy link
Author

nrgbodya commented Jan 6, 2025

Thanks for your response! Unfortunately removing the markdown path property doesn't help as my app relies on the markdown file

@vladvlasov256
Copy link
Contributor

my app relies on the markdown file

What exactly you are trying to achieve?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants