-
Notifications
You must be signed in to change notification settings - Fork 29
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
Install Fails on MacOS Catalina #27
Comments
Same issue I'm having, emailed for help but no response yet, I'm wondering if I should try rollback OS to whatever was before Catalina? |
For anyone interested in WeMessage, I actually spent the afternoon rolling back my Mac mini to Mojave and finally got WeMessage server installed, it's up and running but the deal breaker for me is that the server doesn't stay connected all the time so when I'm not using my phone, the server disconnects until I open the app on my phone again and I believe that's how it was created, I don't think it's a bug or anything. So after all that, I'm going to use AirMessage, the server is always running so I get my messages in real-time, it's too bad, I wish AirMessage would do SMS messages too so I could just have one combined messaging app. I'd like to thank Roman Scott for great idea, seems like he's just moved on to other things. I hope now that it's become open source, some smart person can update for Mac Catalina and have server running all the time or another software company creates their own version and charge whatever they need to keep it updated and worth their time. |
I got around this by using "chmod u+x /dirTo/run.command" in terminal but unfortunately right after it actually executed I get an SQL error "An error occurred while connecting to the message chat database. Shutting down!" |
Running on Catalina simply required extending java "Full Disk Access" and Accessibility->computer control. IIRC, the former permission allows the script to start up and the latter allows for (a) opening sockets and (b) interaction with sqlite. |
Still failing. Even after I do what @edgar1016 and @cedarlug suggest, I get this:
` |
@jkmaxwell I'm getting the same problem. According to tcco it's because the Authenticator module checks whether you're using the default email/password/secret in config.json (so all of them need to be changed), but even changing them didn't get past that error for me. |
When running the run.command on Catalina I am getting the following error:
The file "run.command" could not be executed because you do not have appropriate access privileges.
To view or change access privileges, select the file in the Finder and choose File > Get Info.
All privileges are set to Read & Write and the file still will not open.
The text was updated successfully, but these errors were encountered: