wulkano/kap

"A JavaScript error occurred in the main process" error and app doesn't launch

Open

#1107 opened on Apr 4, 2022

View on GitHub
 (1 comment) (2 reactions) (0 assignees)JavaScript (11,043 stars) (548 forks)batch import
Help WantedType: Bug

Description

I did look at recent issues and haven't seen this one yet.

It may have something to do with my specific system as I've tried installing older version going back to July last year and I get the same issue every time.

macOS version: 12.2.1 (21D62) // Intel Kap version: 3.5.4

Steps to reproduce

Launch the app

Current behaviour

"A JavaScript error occurred in the main process" error. App doesn't launch.

Expected behaviour

Ability to use the app

Workaround

None found so far

Tried installing older versions and get similar errors with slightly different messages, in all cases the app doesn't launch

I checked the permissions and Kap does have access to screen recording

Screen Shot 2022-04-03 at 9 44 17 PM

Screen Shot 2022-04-03 at 9 45 13 PM

Contributor guide

Tech stack
javascriptelectron
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
macOSKap installation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue lacks a detailed error log or stack trace. The user should be asked to run Kap from the terminal to capture the full error output. Additionally, checking system logs or trying a fresh install without preserving user data might help isolate the problem. The maintainer should also verify if the issue is specific to certain macOS versions or Intel architecture.