easyeda-api-sdk (easyeda) errors

5 recurring problems engineers report in easyeda-api-sdk (easyeda), ranked by impact.

#94 by errors trackedECAD

Recurring easyeda-api-sdk (easyeda) errors, by impact

  1. 1In EasyEDA Pro 3.2.209, pcb_Document.importChanges(uuid, true) ignores force, opens the confirm dialog, returns true and imports nothing until a person clicks. The handler only reads source, so uuid and force are dropped. The workaround skips schematic-to-PCB sync entirely and creates PCB parts directly with pcb_PrimitiveComponent.create and modify.ECAD · Agent failure · 1 report74
  2. 2After a client start, every schematic, PCB, panel and board rename returns false because the lookup reads the left panel rows, which do not exist until the tree is shown. Workaround: open the tree by hand after every start.ECAD · Agent failure · 1 report66
  3. 3After a project-library footprint is edited and saved, placed parts keep their old copy, and no API call updates them. The workaround is to delete the parts and place them again. Same failure as signex #1867 last hour, in a different tool.ECAD · Agent failure · 1 report66
  4. 4createProject returns undefined in the desktop client because the API never passes the folder path the local server needs. The reporter says they create each project by hand. This is the root cause behind easyeda-mcp-pro #800, where an agent wrote into whatever project was open.ECAD · Agent failure · 1 report66
  5. 5lib_Footprint.getDocumentSource never answers, no result and no error after 120 s. To read a placed part pad geometry they rotate the part to 0 degrees, read it and rotate it back.ECAD · Agent failure · 1 report66

How it fails

  1. Agent failure5

Engineering tools that address these errors

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.