PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding
'OnFrame' error on Build List with no builds
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 5.4k
- Forks
- 2.4k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 26
Description
Check version
- I'm running the latest version of Path of Building and I've verified this by checking the changelog
Check for duplicates
- I've checked for duplicate issues by using the search function of the issue tracker
What is the expected behaviour/value?
When navigating to the page that shows saved builds I expect to not receive an error after a fresh install with no saved builds.
What is the actual behaviour/value?
When navigating to the page that shows saved builds I receive an error. I am given the option to dismiss the error or restart the application. Restarting the application just brings the error immediately back. Dismissing the error lets me create a new build. After creating and saving any build and navigating back to the saved builds page I am shown no saved builds and receive the error again.
How to reproduce the issue
Open POB or return to the select a saved build screen.
Character build code
I have no imported builds. I reinstalled windows to remove bloatware 2 months ago and POB was one of the first things I reinstalled. It worked fine after reinstalling it, but I was done with Sentinel league so I didn't try importing characters or anything. I opened it to update POB so I'd be ready for 3.19 and was met with the error.
Screenshots

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the problem by opening Path of Building with no saved builds and navigating to the saved-build selection screen. Start by tracing the OnFrame error from that screen and compare fresh-install behavior with the state after saving a build. Done means the screen opens without an error when no builds exist and continues to work after a build is saved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100