-
Notifications
You must be signed in to change notification settings - Fork 25
Recent version always shows "setup incomplete" on macos #5
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
Comments
I'm assuming you installed the connector using brew. Can you run |
Yes. One important note I forgot to mention: I installed it before the new version was out, as I came across the thread in #1 and it worked fine for me for a period. I also tried reinstalling the connector from brew, symlinking again, and restarting firefox
and, the output from
|
Can you screenshot Also, can you:
|
@null-dev I'm running into the same issue, here's a screenshot:
Device is Mac Mini M1 |
I've fixed it with |
I just released a new version of the extension that should hopefully fix this issue. Can you try updating to it? Also make sure to update the additional software when asked. |
No luck, still looks broke... need to see any other logs? |
@asfaltboy Just to confirm, you are running regular Firefox, not a fork right? Can you send me the output of the following commands?
|
Heh, after restarting I see no such dir:
That's weird, before restart it was clearly there... (check the timestamps to the right) |
Just noticed I'm on (regular) firefox 90.0. Could be that the directory is deleted when firefox is upgraded? So I just symlinked and restarted again, but issue persists. I just ran the commands you gave me and it looks like the Here's the output:
|
@asfaltboy I'm completely stumped as everything looks just fine. The error you see with the program is actually because the connector software is expecting to be launched by Firefox however in this case I had you launch it through the terminal just to test that it's installed properly. The last idea I have is to make the manifest globally visible, which you can do by running this command:
|
The above step to make the manifest globally visible fixed things for me. I had to create the |
Huh, well that's good news, I'll instruct users to run that command as well. |
Yep that worked for me too, I'm on a work laptop, could be that is needed on certain setups? Is it something to do with permissions? |
I'm still not really sure why it solves the problem but since it seems to work I'm going to consider this issue solves, feel free to re-open if it comes up again! |
sorry, I wouldn't know where to start looking for debug logs 🤷
The text was updated successfully, but these errors were encountered: