You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 open and closed issues by using the search function of the issue tracker
What platform are you running Path of Building on?
Windows
How is Path of Building expected to behave?
Authorize not working, can't select the league and gets a pop up error
How does Path of Building behave?
Error:
In 'OnFrame': Classes/DropDownControl.lua:171: attempt to perform arithmetic on a nil value
stack traceback:
Classes/DropDownControl.lua:171: in function 'ScrollSelIntoView'
Classes/DropDownControl.lua:454: in function 'OnKeyDown'
Classes/ControlHost.lua:52: in function 'ProcessControlsInput'
Classes/ImportTab.lua:781: in function 'Draw'
Modules/Build.lua:1277: in function 'CallMode'
Modules/Main.lua:372: in function <Modules/Main.lua:342>
[C]: in function 'PCall'
Launch.lua:111: in function Launch.lua:108
v2.67.2 master
Press Enter/Escape to dismiss, F4 to return to build selection, or F5 to restart the application.
Press CTRL + C to copy error text.
How to reproduce the issue
Just logging in and trying to sign in with my POE account.
PoB for PoE1 build code
Error:
In 'OnFrame': Classes/DropDownControl.lua:171: attempt to perform arithmetic on a nil value
stack traceback:
Classes/DropDownControl.lua:171: infunction'ScrollSelIntoView'
Classes/DropDownControl.lua:454: infunction'OnKeyDown'
Classes/ControlHost.lua:52: infunction'ProcessControlsInput'
Classes/ImportTab.lua:781: infunction'Draw'
Modules/Build.lua:1277: infunction'CallMode'
Modules/Main.lua:372: infunction<Modules/Main.lua:342>
[C]: infunction'PCall'
Launch.lua:111: infunction<Launch.lua:108>
v2.67.2 master
Press Enter/Escape to dismiss, F4 to return to build selection, or F5 to restart the application.
Press CTRL + C to copy error text.
You may need to reinstall PoB. I'm using Rusty PoB on Linux, so idk how much that contributed to it, but it wouldn't pull the beta build and said 2.67.2 was the latest available. I uninstalled and reinstalled it, opted into the beta again, and now it pulls the beta build like it should, which fixed the issue for me.
Usually just making it pull PoB fresh works if it doesn't want to update, but this time it still kept pulling 2.67.2, and I had to reinstall to make it sync properly. Hopefully that fixes your issue as well!
I also had this problem with this version. It said no update, but did not have the new beta update, even though I had opted for beta updates a long time ago. I opted out. Checked for update. Let it check. Opted in again and checked for update. Finally it pulled the beta update.
Account importing now working.
If you are as desperate as I am, this is a quick fix to use while the developer updates PoB for 3.30.
Go to ImportTab.lua in "Classes" folder
Go to line 116; between lines 116 and 124 you will find this code:
-- if main.lastLeague then
-- for i, v in ipairs(self.controls.charSelectLeague.list) do
-- if v == main.lastLeague then
-- self.controls.charSelectLeague:SetSel(i)
-- end
-- end
-- else
-- self.controls.charSelectLeague:SetSel(1)
-- end
Comment out the entire block using "--" and replace it with this one:
local foundLastLeague = false
if main.lastLeague then
for i, v in ipairs(self.controls.charSelectLeague.list) do
if v == main.lastLeague then
self.controls.charSelectLeague:SetSel(i)
foundLastLeague = true
break
end
end
end
if not foundLastLeague then
self.controls.charSelectLeague:SetSel(1)
end
The import feature is working now for me, but after making this change, PoB will detect that the version has been updated the next time you run it and will prompt you to install an update, do not do this, as it will undo your change.
That’s why I call it a "hacky fix" while waiting for an official update.
Activity
philtrumbull-byte commentedon Nov 14, 2026
Reinstalling has not done anything.
vaisest commentedon Nov 14, 2026
Try opting into the beta builds from the options menu
philtrumbull-byte commentedon Nov 14, 2026
That did not help.
AdamZ-8113 commentedon Nov 14, 2026
Can you add another screenshot showing you're running the beta version? I thought #10250 fixed this issue, which is on the beta.
schwaka0 commentedon Nov 15, 2026
You may need to reinstall PoB. I'm using Rusty PoB on Linux, so idk how much that contributed to it, but it wouldn't pull the beta build and said 2.67.2 was the latest available. I uninstalled and reinstalled it, opted into the beta again, and now it pulls the beta build like it should, which fixed the issue for me.
Usually just making it pull PoB fresh works if it doesn't want to update, but this time it still kept pulling 2.67.2, and I had to reinstall to make it sync properly. Hopefully that fixes your issue as well!
Keshr0 commentedon Nov 15, 2026
I also had this problem with this version. It said no update, but did not have the new beta update, even though I had opted for beta updates a long time ago. I opted out. Checked for update. Let it check. Opted in again and checked for update. Finally it pulled the beta update.
Account importing now working.
Mizerka commentedon Nov 16, 2026
opting out recheck and opting back in worked here also, version still 2.67.2 but now has the usual beta -hexwhatever and no lua errors
gomakejams commentedon Nov 17, 2026
If you are as desperate as I am, this is a quick fix to use while the developer updates PoB for 3.30.
Go to ImportTab.lua in "Classes" folder
Go to line 116; between lines 116 and 124 you will find this code:
Comment out the entire block using "--" and replace it with this one:
The import feature is working now for me, but after making this change, PoB will detect that the version has been updated the next time you run it and will prompt you to install an update, do not do this, as it will undo your change.
That’s why I call it a "hacky fix" while waiting for an official update.
Wires77 commentedon Nov 17, 2026
I'm assuming this is fixed by 2.68.0