PathOfBuildingCommunity / PathOfBuildingCommunity/PathOfBuilding

Error on start up

Open
#2,479 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug crash
Dominant language
Lua
Stars
5.4k
Forks
2.4k
Avg merge
1d 12h
Merged PRs (30d)
26

Description

Thank you for reporting an issue.

Before reporting a bug, please make sure that you are running the latest version.
You can get the latest version number from CHANGELOG.md

Please try to fill in as much of the template below as you're able.

  • What happened?
    Getting an error after pob checks for updates, if i use it the moment it finishes checking it crashes, otherwise it only writes an error
  • What were you trying to do?
    Nothing.
  • What steps will reproduce the bug?
    Check for updates.
  • Does it reproduce every time?
    If you do something(like allocating skills, creating items) while it checks it crashes pob, otherwise it only gives out an error
  • Provide a build code:
    Always provide a build code that exhibits the bug you want to report, even if it is not specific to a particular build. This helps us greatly to reproduce bugs faster. Otherwise, we will have to ask you for the code first before investigating, which would delay any possible fixes.
  • Screenshots:
    image

If you receive an error or experience graphical bugs, include one or multiple screenshots. GIFs or short videos are also okay, if the bug cannot be displayed in a still image.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported behavior with the application's update check, both while performing another action and while idle. Use the attached screenshot and resulting error as the investigation starting point; done means the update check no longer crashes the application or produces the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.