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

Cannot read property 'some' of undefined #914

Closed
mcvicar opened this issue Aug 19, 2020 · 5 comments · Fixed by #915
Closed

Cannot read property 'some' of undefined #914

mcvicar opened this issue Aug 19, 2020 · 5 comments · Fixed by #915

Comments

@mcvicar
Copy link

mcvicar commented Aug 19, 2020

macOS version: 10.13.6
Kap version: v3.3.0

Steps to reproduce

Was a fresh install on a mac running OSX 10.13.6
Once OSX security allowed the app to run as an unsigned developer, start-up would fail with the following dialogue.
Screen Shot 2020-08-19 at 20 33 21

Current behaviour

Kap will not start, error dialogue box is broken and can not be interacted with (e.g. the buttons can not be pressed)

Expected behaviour

Kap to start up

Workaround

No workaround found.

Couldn't really spot how getAudioDevices() isn't returning an array.

const getAudioDevices = async () => {

Installed https://github.com/karaggeorge/macos-audio-devices locally and got the following;

apple$ audio-devices
dyld: Library not loaded: @rpath/libswiftCore.dylib
  Referenced from: /usr/local/bin/audio-devices
  Reason: image not found
Abort trap: 6
@karaggeorge
Copy link
Member

Sorry about that, fixed in #915

In the meantime you can get it to work by following this:

Requires macOS 10.12 or later. macOS 10.13 or earlier needs to download the Swift runtime support libraries.

@mcvicar
Copy link
Author

mcvicar commented Aug 19, 2020

That seemed to fix it. Thanks!

@mcvicar mcvicar closed this as completed Aug 19, 2020
@karaggeorge
Copy link
Member

@mcvicar just out of curiosity for a different feature we released:

When you got the error dialog, did you click on the collect & report? If so, how did it go?
Or did you just copy the error and create the issue manually?

@mcvicar
Copy link
Author

mcvicar commented Aug 19, 2020

I couldn't interact with the error dialog at all, and had to create the issue manually.
When the dialog appeared the cursor was "precision select", none of the buttons could be pressed and the text in the toolbar was all messed up.

@karaggeorge
Copy link
Member

Thank you for the info! We'll try to fix that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants