-
Notifications
You must be signed in to change notification settings - Fork 412
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
Fails to open on macOS #128
Comments
^ This appears to have been a conflict with Electron and a third-party virtual camera/mic app I had installed which had some outdated/unsupported install/loading method related to newer policies for kexts in mac. The conflict likely would have broken other Electron apps which tried to request the system's media I/O devices and so it seems as if my issue had no relation to this project, closing... 😇 |
@ev-dev how did you fix it or found which mic / camera third party app was it? |
TBH I was less systematic about it than I should've been but my first searches citing similar Electron log messages (posted above) all seemed to involve some problems with virtual cam/mic drivers like this issue involving an OBS project. I had several of these apps (including Iriun & Camtwist) installed leftover from an early pandemic rush to improve my cam quality, and seeing as I have since stopped using them, I opted to just remove all traces of them from my system, after which I was able to launch the dist release of the assistant desktop client. Apologies for the less-than-ideal process, if any related issues come up I'd be happy to chime in with more |
Thanks, I'll do some more digging
…On Sun, Feb 14, 2021 at 9:53 PM Evan Reed ***@***.***> wrote:
TBH I was less systematic about it than I should've been but my first
searches citing similar Electron log messages (posted above) all seemed to
involve some problems with virtual cam/mic drivers like this issue
involving an OBS project
<johnboiles/obs-mac-virtualcam#206>.
I had several of these apps (including Iriun <https://iriun.com> &
Camtwist <http://camtwiststudio.com/>) installed leftover from an early
pandemic rush to improve my cam quality, and seeing as I have since stopped
using them, I opted to just remove all traces of them from my system, after
which I was able to launch the dist release of the assistant desktop client.
Apologies for the less-than-ideal process, if any related issues come up
I'd be happy to chime in with more
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACPYHFULWPTI6P3EUNZOJTS7CZGNANCNFSM4XTEUGSA>
.
|
I am now experiencing the same issue, while other Electron apps do work (Slack). |
Describe the bug
App fails to load UI when launching via
npm start
, running from dist build, or trying to open via downloaded/installed release build. Also unable to open dev tools in Electron to inspect runtime errors.To Reproduce
Steps to reproduce the behavior:
npm start
Expected behavior
A visible UI window should be initialized from App
Desktop (please complete the following information):
Additional context
The Electron process does clearly launch and is visible in the dock but no app shell or any window is opened and no error info is visible either.
Not at all sure if this is relevant, but when running via
npm start
or launching the dist from terminal, the logs show repeated messages forElectron Helper (Plugin)[31133:3009778] OBSDAL: ...
The repeated logs for this are:
Device unhandled setPropertyDataWithAddress for kCMIOObjectPropertyListenerAdded
HardwarePlugIn_ObjectSetPropertyData Device(40) kCMIOObjectPropertyListenerAdded self=0x10df66e00 data(int)= ...
Device unhandled hasPropertyWithAddress for kCMIOObjectPropertyOwnedObjects
The text was updated successfully, but these errors were encountered: