Handbook Version
v2026.04.17.1
Released 2026-04-17
Download PDF
Known Limitations¶
Goal¶
Clarify what the current version actually implements and which behaviors are product boundaries rather than regression bugs.
Current Known Limits¶
1. 3D only supports KiCad board files¶
- the current 3D loader first checks whether the source is
.kicad_pcb - non-KiCad sources show an unsupported message directly
2. Export can only start from 2D¶
- the export button is unavailable in
3DandData - there is no direct 3D image export path in the current version
3. Export is currently gated behind a separate unlock¶
- if export access has not been unlocked yet, the workspace does not start export directly
- tapping export opens the purchase center first
- after purchase or restore succeeds, export becomes available again
4. SES cannot create a standalone new document¶
- it must be launched from an existing document menu
- a base revision must be chosen first
5. iOS Photos export only supports PNG¶
PDF, original-source export, and converted export do not go to Photos
6. macOS export only saves to files¶
- there is no macOS
Other Apps / Photosexport path right now
7. Original-source export depends on the current revision being library-managed¶
- the original-source export option only appears when the currently open revision is managed by the library
- original-source export does not read directly back from a temporary external path
8. AI capability depends on external provider configuration¶
- the settings page can configure multiple providers
- actual usability depends on API keys, network access, and provider response
9. The language page is not an in-app instant language switcher¶
- it mainly explains the system-level language path
- after changing it, the app may need to be relaunched
10. Directory-style manufacturing inputs still depend on importer recognition¶
- the fact that a source is a folder or archive does not guarantee that it will be recognized as a supported manufacturing input
How to Use This Page¶
- Before filing a bug, check whether the case falls inside one of these boundaries.
- If product behavior conflicts with this page, report it as a documentation-vs-implementation mismatch first.
- If a limitation is removed in the future, update the handbook and QA pages together.
What Does Not Count as a “Known Limitation”¶
- reproducible crashes
- blocking failures in a clearly supported path
- regressions from previously stable behavior