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

Bug in macOSX ExpressLRS Configurator v1.4.2 #280

Closed
Martivip opened this issue Feb 15, 2022 · 10 comments
Closed

Bug in macOSX ExpressLRS Configurator v1.4.2 #280

Martivip opened this issue Feb 15, 2022 · 10 comments
Labels
bug Something isn't working

Comments

@Martivip
Copy link

Current Behavior

When I launch ExpressLRS Configurator everything works OK, but when i close the Configurator App by clicking red X on the left top corner of the App, the app is being active in background and when I click the App to launch again it displays this below message and the App is being automatically permanently closed.
Message

@Martivip Martivip added the bug Something isn't working label Feb 15, 2022
@schugabe schugabe transferred this issue from ExpressLRS/ExpressLRS Feb 16, 2022
@parkerbjur
Copy link
Contributor

parkerbjur commented Feb 24, 2022

I have been able to recreate this bug on macOS Monterey 12.2.1 on an m1 macbook air. After the error, relaunching the configurator worked. I will try to look into this soon.

Edit: it seems this issue may in part be caused by graphql. Others have also experienced a very similar issue.

@jaydenlawson
Copy link

I get that error when opening Configurator, after quitting the Configurator during a build. Opening a second time does not display the error.

@Martivip
Copy link
Author

with the new version 1.4.1 issue sill exist

@Martivip
Copy link
Author

Martivip commented Jul 4, 2022

the same with 1.4.2

@Martivip Martivip changed the title Bug in macOSX ExpressLRS Configurator v1.3.8 Bug in macOSX ExpressLRS Configurator v1.4.2 Jul 4, 2022
@Pairan
Copy link
Contributor

Pairan commented Jul 8, 2022

This bug has been there for a looong time but as Bryan already stated: restart it and its gone! ... But yes, it would be nice when it disappears by time :)

@jurgelenas
Copy link
Member

I have upgraded type-graphql to v1.2.0-RC1 which should solve the issue.

https://github.com/MichalLytek/type-graphql/releases/tag/v1.2.0-rc.1

@jurgelenas
Copy link
Member

It should be fixed in 1.4.3 release. Please test @Pairan, @parkerbjur, @Martivip.

@Pairan
Copy link
Contributor

Pairan commented Jul 8, 2022

will report back in

@Pairan
Copy link
Contributor

Pairan commented Jul 8, 2022

... hey wait ... where has v1.4.3 gone? ... now the new version is stated in V1.4.2 !? ... I didn't have that much beer by now to go wrong so badly already, did I?!

@Martivip
Copy link
Author

Martivip commented Jul 8, 2022

@jurgelenas I've tested with the latest nightly build and no... the issue is still there, where I find 1.4.3 ? :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants