Install: Failed to activate the file-icons package, Cannot read property 'Symbol(Symbol.iterator)' of undefined #519
Comments
|
same issue atom 1.13.0 |
|
Same issue here Atom 1.14.0-beta0 |
|
Mine too. file-icons 2.0.9 |
|
Okay, I'm back in action now. Am in a position to actually fix this. |
Alhadis
added
the
bug
|
Atom 1.14-beta1 64bit |
|
Bug confirmed here. file-icons 2.0.9 Noticed before decativating and deactivating that in tree view no visible icons, but I think it's related - not fully activating. Thanks in advance for the fix, really appreciate this package. 👍 |
|
THIS JUST IN, AUSSIE INTERNET SUCKS A BOWL OF ARSE. Third time Vagrant's timed out while downloading an Ubuntu box. I was hoping of getting the spec-runner setup to test for an Ubuntu environment, but screw it, bugging you guys to clone and test locally might be easier. Sorry in advance. :( |
|
Might have to setup the Virtualbox VM manually. |
Having a same issuethis is with a fresh install of Atom, I believe the updates are causing the issue. |
|
To anybody wondering, I'm concentrating on fixing the package's spec-runner, which I recently noticed isn't working on Windows. Once the spec-runner's working properly across all platforms, I can fix this issue without worrying about introducing another unseen regression... :\ |
|
Also, our spec-runner is spiffy as fuck. Juuuust sayin'... 👼
Kicks the shit out of Atom's default spec-runner. |
|
bump |
|
... could you not. |
|
+1 file-icons 2.0.9 |
|
+1 file-icons 2.0.9 |
|
I was facing the Same issue but after restart it's working file-icons 2.0.9 |
|
Well, i'm completely re-install Atom.
And now all fine, plugin install without error 💃 |
|
I swear I read this instead: [
"Applications/Atom.app",
home + "/.atom",
"/usr/local/bin/atom tool",
"/usr/local/bin/apm tool",
"~/Library/Preferences/com.github.atom.plist file"
].map(value => delete value);The amount of JavaScript I write is beginning to have a psychological toll. (Ignore the meaningless use of the |
|
Error shows after install only. After restart the plugin works. |
|
Errors apears after install. |
|
I'm so sorry for the slow response, guys. :( Been preoccupied with trying to fix other issues (specifically, unemployment/money/real-world crap, etc). Fixed, and will cut a release shortly. |
|
Just noting it still happens after update to latest release. Maybe it's cause for issue #529? (just random thought) === Atom Version: 1.11.2 Stack TraceUncaught TypeError: document.styleSheets[Symbol.iterator] is not a function CommandsConfig{
"core": {
"packagesWithKeymapsDisabled": [
"autocomplete-plus"
],
"telemetryConsent": "no",
"themes": [
"atom-material-ui",
"one-dark-syntax"
]
}
}Installed Packages# User
atom-material-ui, v1.3.9 (active)
autoclose-html, v0.23.0 (active)
autocomplete-paths, v1.0.5 (active)
emmet, v2.4.3 (active)
file-icons, v2.0.13 (active)
git-plus, v7.0.7 (active)
gpp-compiler, v3.0.7 (active)
highlight-line, v0.11.2 (active)
language-latex, v1.0.0 (inactive)
language-lua, v0.9.11 (inactive)
latextools, v0.8.5 (active)
pdf-view, v0.54.0 (active)
pigments, v0.37.0 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.2.0 (inactive)
base16-tomorrow-light-theme, v1.2.0 (inactive)
one-dark-ui, v1.6.0 (inactive)
one-light-ui, v1.6.0 (inactive)
one-dark-syntax, v1.3.0 (active)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.7.0 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.201.1 (inactive)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.59.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2-hotfix1 (active)
snippets, v1.0.2 (active)
spell-check, v0.68.2 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.101.0 (active)
timecop, v0.33.2 (active)
tree-view, v0.209.3 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)
# Dev
No dev packages |
|
This right here is what's concerning me: That should NEVER not be an iterable; it's part of the DOM standard. The fact this error seems Ubuntu-specific leads me to believe the Of course, I'd be in a position to find out more about this if I had access to a working Ubuntu box... |
|
Well, Ubuntu-specificy rules this issue out as cause for the other. If you point me in a direction I could try helping...? No experience with Atom development though. |
|
File a new issue, please. It's clearly unrelated to this one. |
|
@jeyj0 The next time this happens, please open the devtools and run this snippet: console.log(document);
console.log(document.constructor);
console.log(document.styleSheets);
console.log(document.styleSheets.constructor);Then screencap the output, which should ideally look like this:
If either the I admit I'm clutching at straws, but I'm still in the dark as to how the hell this is happening, let alone why. |
|
I think i'm having the same issue, i'm using ubuntu 14.04 though. Output does not seem off in any way, could it be that the document just isn't ready yet? |
|
I settled on doing this the unintelligent way - checking |
|
Just installed PlatformIO from the main site and I'm seeing this error for every new window opened on OSX 10.11.6. I ran the snippet described above, but the output is the same as yours. I'm not sure my version has the committed changes you linked to above as I've installed from the main distribution from http://platformio.org. If I run the update tool, it shows I'm up-to-date. |
|
@ivankravets How often does PlatformIO update its copy of the I don't know how PlatformIO works, or how users go about upgrading their packages... |
|
@Alhadis We use "pre-cached" packages in PlatformIO IDE 1.0 installer. This logic will be improved in PIO IDE 2.0 (in progress). Nevertheless, I don't see here any problems. Users are able to update own packages manually, as they do that in a generic way. In any case, I've just removed that cache and all our dependencies are regenerated again. @cmenscher Are you sure that you don't see updates? Could you try to re-start Atom? Maybe they cache something. |
|
@ivankravets I've tried restarting it several times. Each time it gives me the error. Checking for updates from the menu returns nothing. Is there a way to force delete the cache? |
That is not "PlatformIO" package. You should check for Atom updates, not PlatformIO. Also, you should have notification located in bottom right corner (N updates...). Or click on Settings ⚙️ > Updates |
|
@ivankravets Ah! Right. Alas, it says "All of your installed packages are up to date", even after a manual check. |
|
@cmenscher and what do you see in |
|
@ivankravets initial installation was version 2.0.13. I uninstalled and the Install dialog for file-icons presented me with 1.7.25, stating "Version 1.7.25 is not the latest version available for this package, but it's the latest that is compatible with your version of Atom." I installed that, and the error now no longer appears! So, it seems that the version of Atom+PlatformIO that is downloadable from platformio.org has incompatible versions in the bundle. |
|
@cmenscher I got the problem. You have an old version of Atom. What is your OS? Atom version? |
|
@ivankravets I'm using Atom version 1.9.9, on OSX 10.11.6. This version of Atom is what was distributed via the download link on platformio.org. As I mentioned before, when I use Atom's "check for update" menu item, nothing happens. What version should I be using? |
|
@cmenscher I didn't know that auto-updater is broken in 1.9.9 for macOS. I'll rebuild all our distribution. Temporary, please download Atom from https://atom.io |
|
@ivankravets SUCCESS! Updated Atom, ran the updater in settings. Everything fully up-to-date and no errors. Thanks for the help. |
|
@ivankravets Just an FYI...installing the most recent version of Atom (v1.12.3) and PlatformIO separately results in inoperative Terminal and Serial Monitor windows,with "Path must be a string. Received null" errors like this platformio/platformio-atom-ide-terminal#131. I wasn't able to debug, so I'm going back to Atom version 1.9.9 for now and will install file-icons 1.7.25. |
Where did you find this info? |
|
@ivankravets In the developer tools console. The result of the error is a completely blank (black) pane for both the terminal and the serial monitor. |
|
I've just deployed new PlatformIO IDE bundle based on Atom 1.3.1. Could you try it from our site? Thanks! |
|
OK just tried it...same result as when I installed manually. Here's a dump of the console after I launch Atom and bring up the Terminal. The first 6 lines are warnings and info...the "Path must be a string" is the error that is triggered when the Terminal is opened. I'm including the warnings as they may be related...
|
|
@cmenscher Please open Developer Console and type |
|
@ivankravets It returns "49". |
|
@cmenscher Let's don't flood in this thread. Please mail me@ikravets.com |
|
Thanks for your help, @ivankravets! Really appreciate it. =) To everybody else: I'm locking this so users will file new issues instead of commenting on old ones. The last few posts have dealt with unrelated bugs, with similar-looking error messages. It's clear Atom's becoming confused with linking to correct issues. Any users who are still experiencing problems are strongly encouraged to file a new issue. If anybody here has questions, please e-mail me directly. |
Atom thinks this is the same as #476, but discussion there suggests a separate issue. Filing separately, just to be safe.
Atom Version: 1.13.0
Electron Version: 1.3.13
System: Microsoft Windows 10 Pro Insider Preview
Thrown From: file-icons package, v2.0.9
Stack Trace
Failed to activate the file-icons package
Commands
Config
{ "core": { "telemetryConsent": "limited", "themes": [ "one-light-ui", "solarized-light-syntax" ] } }Installed Packages
The text was updated successfully, but these errors were encountered: