-
Notifications
You must be signed in to change notification settings - Fork 30
Uncaught TypeError: Cannot read property 'apiClient' of undefined #212
Comments
Hi Shaun, sorry for keeping you waiting. Is this error happens every time you try to select a device after opening a new Atom window? Do you see target platform and current build target selectors in the status bar? |
Hi having same issue after updating new package. Let me know how to resolve this. |
@sohil4932 are you using standalone Particle Dev App or Atom? |
Standalone Particle Dev App. I downloaded it for Mac. I was using Particle Dev since long, but yesterday I updated a couple of Particle packages and after that, it stops working and giving me this error. |
@sohil4932 can you check if you have any |
Hi sorry I haven't had time to participate in this right now I ended up getting the build tools working on the command line and used that, I still had whatever problem with the linker when I was trying to divvy up my project into different cpp and .h files but it's been a long time since I really worked with C++ so likely something silly I did or something in the makefile that wasn't working out. Seemed I could get it to compile everything but during the linking it failed to find things defined in files outside the application.cpp (since I was just toying with this I decided to just dump all the code in there). Hopefully you all can get this issue sorted out though I did have to jump through some hoops to get compiling at the command line (think mostly just needed gcc arm build tools), good luck! |
[Enter steps to reproduce:]
Atom: 1.18.0 x64
Electron: 1.3.15
OS: Ubuntu 16.04.2
Thrown From: particle-dev package 0.1.22
Stack Trace
Uncaught TypeError: Cannot read property 'apiClient' of undefined
Commands
Non-Core Packages
Attempting to just get things installed for compiling locally since I'm having some troubles with the linking on the web ide and wanted to see if local compiling helped but ran into a couple of errors, this one and the querySelector issue.
The text was updated successfully, but these errors were encountered: