Cannot read property 'split' of undefined
See original GitHub issueDescription
When I clone repo from GitHub and use Kactus to open it, shows the Cannot read property ‘split’ of undefined alert.
Version
Kactus version: 0.2.4
OS version: 10.12.6 (16G29)
Steps to Reproduce
- Clone Repository from GitHub in Kactus
- Create a Sketch file in Kactus
- Kactus shows the ERROR ALERT
Logs
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:13 (3 by maintainers)
Top Results From Across the Web
How to prevent cannot read property split of undefined
If different values are assigned to a variable several times, calling the split() method on the variable when it is set to undefined...
Read more >How to Prevent cannot read property split of ... - Gopi Gorantala
The "cannot read property 'split' of undefined" error occurs when trying to call split() method on a variable that stores an undefined value....
Read more >Cannot Read Property 'split' of Undefined - freeCodeCamp
Calling array[i].split(""); to split each string into substrings of characters is a valid approach, but it will throw TypeError: Cannot read ...
Read more >Uncaught TypeError: Cannot read property 'split' of undefined
If og_date contains the date, it's probably a string, so og_date.value is undefined. Simply use og_date.split('-') instead of og_date.value.
Read more >TypeError: Cannot read property 'split' of undefined - JavaScript
So the argument word is coming in as undefined and therefore you can't run split() on it. You can either make sure it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah definitely need to fix this. I’m on holiday this week, will look at it on Monday.
Well, as this can happen not only when messing with the
.gitignore
but when cloning an existing repo I guess this is indeed important. (But this is of course for @mathieudutour to decide)