BetterBags

BetterBags

Addons
2M Downloads

Can't open bank, Lua error

LenweSaralonde opened this issue ยท 1 comments

commented

Addon Version

0.3.31

World of Warcraft Version

Retail

Describe the bug

I can't use the bank (nothing shows up but the backpack) and I get LUA error instead.

Steps to reproduce

  1. Click bank NPC to open bank

More information

  • Reproduced even with other addons disabled
  • Only reproduced on a specific character. I guess it could be caused by my configuration or a specific item.
  • 6 bank tabs

Bank contents

Tabs 3 and 6 are empty.
No warband bank

Image Image Image Image

Bag contents

Image

Error trace

Message: Interface/AddOns/BetterBags/frames/tabs.lua:227: attempt to index field '?' (a nil value)
Time: Fri Sep 19 20:03:25 2025
Count: 1
Stack:
[Interface/AddOns/BetterBags/frames/tabs.lua]:227: in function 'ShowTabByIndex'
[Interface/AddOns/BetterBags/frames/bag.lua]:180: in function 'ShowBankAndReagentTabs'
[Interface/AddOns/BetterBags/frames/bag.lua]:197: in function 'Show'
[Interface/AddOns/BetterBags/core/init.lua]:302: in function 'cb'
[Interface/AddOns/BetterBags/core/events.lua]:49: in function <Interface/AddOns/BetterBags/core/events.lua:47>
[C]: ?
[Interface/AddOns/BetterBags/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua]:19: in function <...ags/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua:15>
[Interface/AddOns/BetterBags/libs/CallbackHandler-1.0/CallbackHandler-1.0.lua]:54: in function 'SendMessage'
[Interface/AddOns/BetterBags/core/events.lua]:206: in function 'SendMessage'
[Interface/AddOns/BetterBags/core/events.lua]:224: in function <Interface/AddOns/BetterBags/core/events.lua:223>

Locals:
self = <table> {
 buttonToName = <table> {
 }
 tabs = <table> {
 }
 tabCount = 1
 tabIndex = <table> {
 }
 frame = BetterBagsBagBankTabContainer {
 }
 selectedTab = 1
 width = 76.999985
}
index = 2
(*temporary) = nil
(*temporary) = nil
(*temporary) = "attempt to index field '?' (a nil value)"
commented

Tried to reproduce using the latest version from main (commit 802a59b) and the problem does not occur anymore.
I keep it open in case someone else encounters the bug but it seems that it will be fixed in a next release.