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

Protoc & macOS Catalina #1

Closed
Volcore opened this issue Aug 22, 2020 · 6 comments
Closed

Protoc & macOS Catalina #1

Volcore opened this issue Aug 22, 2020 · 6 comments

Comments

@Volcore
Copy link

Volcore commented Aug 22, 2020

When using macOS Catalina, I'm getting the following error:

image

I was able to resolve it by running Cmd + Clicking the package. But this is something that everyone on our team has to do now when building for the first time.

Is it necessary to include the protoc compiler? We usually pre-build our protocol buffers files, maybe that's possible here as well (and only include the built files, but not the protoc compiler).

@ktaraymovich
Copy link
Contributor

Yes, it is necessary to include protoc as plugin regenerates protocol buffer files depends on the settings you are using. I've added additional message about it the UI.

@cgydev
Copy link

cgydev commented Jul 20, 2021

Am getting the same Box on MacMini with Big Sur. Since I have pressed cancel, it is showing the following note in the Tuner window.

Screenshot 2021-07-20 at 12 50 41 PM

Any information as to how to move from here ?

Update:
Seems to have started functioning once I restarted Unity

@ktaraymovich
Copy link
Contributor

If you still seeing this message - open protoc binary location in Finder -> right click -> choose Open -> it should show the dialog again.

@biralpucar
Copy link

Days I get these bugs. All google searches yielded no results. Please help me.

Screenshot_1

@ifraud
Copy link
Collaborator

ifraud commented Jun 9, 2023

@biralpucar Could you share the contents of your dev_tuningfork.proto? It sounds like the file got corrupted with unrecognized characters. Have you tried to just compile it separately to see if you encounter the same issue?

@biralpucar
Copy link

@ifraud yes, I change it as in the image and compile it again, I remove the package and install it again, but the result is always the same..

fail
Screenshot_1

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

5 participants