Medis.app launched with no interface

[lyqeyes]

system: MBP, OS X EI Capitan version 10.11.6 (15G31)

I download zip package from github and run deploy commands following the README.md

npm install npm run deploy

then the Medis.app generated successfully.
But when I run it, there is only an icon in docker with no User Interface.

What's the problem?
Who can help me...

[srarcbrsent]

i got the same problem

[pherrymason]

Same here, I'm on macOS Sierra

[keenen]

I too had the same issue.

[motiejunas]

For me as well... (macOS High Sierra 10.13)

[joshuatalb]

I'm also bumping into this issue. I'm running MacOS High Sierra too (npm v5.5.1 & node v8.7.0). The only way I could get it to work is by running npm run dev, and then running npm run start (in another tab) after Webpack had finished building. This brings up the UI and allows you to start using it. Not ideal, but it's a workaround at least.

The one thing I did find when running npm run start was that I get a few errors in my terminal. Not sure if it's specific to me though.

rm: Medis.app/Contents/Resources/app.asar: No such file or directory [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0

[pingcheng]

same here and also [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0 this error msg

[RaMin0]

+1

[fortis]

+1

[vladlavrik]

+1

[SethStalley]

+1

[romikzo]

+1

[wakaryry]

+1

[JulianTenschert]

+1

[Enoooch]

+1

[RyanKlann]

+1

[daniesy]

I'm also bumping into this issue. I'm running MacOS High Sierra too (npm v5.5.1 & node v8.7.0). The only way I could get it to work is by running npm run dev, and then running npm run start (in another tab) after Webpack had finished building. This brings up the UI and allows you to start using it. Not ideal, but it's a workaround at least.

The one thing I did find when running npm run start was that I get a few errors in my terminal. Not sure if it's specific to me though.

rm: Medis.app/Contents/Resources/app.asar: No such file or directory [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0

It works with npm run dev, and then running npm run start

[dejurin]

Catalina: I got the same problem

[hao830103]

Catalina +1 Same problem

[avillegas]

Catalina +1 Any update ?

[lyqeyes]

Why does there still has so much +1? I opened the issue 3 years ago... Some months ago, I cloned the repo and run those commands(updated as 3 years ago) follow the README.md. I remember that it can work as expected now.

Assuming U really has this problem,

~~U can give a try to the app I packaged as follow.~~

aha, the .zip is so big that I can not upload it as an attachment. so U can

1. try to package it by youself. u can use some utils like electron-packager
2. email me (lyq#oureda.cn) then I will send u the app package. Tip: I have MAC app only.

[phuoc-insignia]

I'm also bumping into this issue. I'm running MacOS High Sierra too (npm v5.5.1 & node v8.7.0). The only way I could get it to work is by running npm run dev, and then running npm run start (in another tab) after Webpack had finished building. This brings up the UI and allows you to start using it. Not ideal, but it's a workaround at least. The one thing I did find when running npm run start was that I get a few errors in my terminal. Not sure if it's specific to me though. rm: Medis.app/Contents/Resources/app.asar: No such file or directory [warn] kq_init: detected broken kqueue; not using.: Undefined error: 0

It works with npm run dev, and then running npm run start

works for me

[luin]

Hello 👋

Our development focus has now shifted to the next generation of Medis: Medis 2. Compared to its predecessor, Medis 2 offers enhanced performance, more powerful features, and a more delightful interface. If you encounter any problems with Medis 2, feel free to reopen this issue, and together, we can explore possible solutions.

Download Medis 2 for free: https://getmedis.com/. Thanks for using and supporting Medis 1!