-
Notifications
You must be signed in to change notification settings - Fork 52
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
El-Maven will not open after upgrading MacOS to Big Sur #1376
Comments
Hi @tarateslaa. Since El-MAVEN v0.12 (our latest) was released before Big Sur, we did not get a chance to test it out on the new OS. The next release will address this problem. If you cannot wait that long, I can provide links to our development builds of El-MAVEN where we have tested it to be working on Big Sur but cannot guarantee general stability of the software (you might run into other annoying bugs). Let me know. |
@saiful-elucidata That would be great! It would help a lot to have something to use in the meantime (even if it is buggy) while I wait for the next release! |
@tarateslaa Alright. Then here's the installer for our unstable macOS build: https://elmaven-installers.s3-us-west-2.amazonaws.com/Mac/El-MAVEN-develop.zip Please feel free to report any issues you find! |
great it's working! |
@chubukov El-MAVEN v0.12.1-beta installer was built on BigSur. Let us know if that's giving you trouble? |
@shubhra-agrawal Thanks a lot, do you have an installer that you can paste a link for? The front page gave me 0.12.0, which gave the same error as the version I got from Saiful's link above. (I was hoping to avoid building from source) |
v0.12.1-beta |
Hi @shubhra-agrawal System: macOS Monterey Version 12.2.1 - Apple M1 chip |
Describe the bug
When I try to open El-Maven nothing happens. I click on the icon and it looks like it will open, but then night.
To Reproduce
n/a
Expected behavior
I expect ElMaven to open =)
Screenshots
n/a
System (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: