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

macOS(tauri): Inject plist in the runtime for webRTC & al. #1570

Closed
lemarier opened this issue Apr 21, 2021 · 4 comments
Closed

macOS(tauri): Inject plist in the runtime for webRTC & al. #1570

lemarier opened this issue Apr 21, 2021 · 4 comments

Comments

@lemarier
Copy link
Member

lemarier commented Apr 21, 2021

Is your feature request related to a problem? Please describe.
Yes. We should allow an option to inject a plist in the runtime to ask permissions.

Describe the solution you'd like
Add a new configuration field in tauri.conf.json for macOS to customize the plist.

Option 1

We build a schema where they can define their own dict in tauri.json.conf (will require more works)

Option 2

Ask for a path but the user should take care of all aspects of the plist (app name etc..)

Another field should allow enabling or disabling the plist injection at the runtime (in dev mode), in prod it should never be injected as we use the bundler plist.

Will require some update in the bundler as well to make sure dev and prod reflect the same.

Describe alternatives you've considered
N/A

Additional context
Refer to tauri-apps/wry#85 (comment)

@nothingismagick
Copy link
Sponsor Member

I am all for option #1 & #2

#1 we keep it REALLY simple
#2 is if they want to break it themselves

@lemarier
Copy link
Member Author

@lucasfernog if you want i can do it, i would love to know how you see it and which option you prefer.

@lucasfernog
Copy link
Member

I think we should go with #2, writing a plist in JSON must be weird (and prevents someone to just copy a file from stackoverflow lol).

@lemarier
Copy link
Member Author

I think we should go with #2, writing a plist in JSON must be weird (and prevents someone to just copy a file from stackoverflow lol).

make sense lol!

gonna draft that quickly

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

3 participants