Blizzard UI - Trade Skill Errors

I actually found it VERY easy to reproduce. Once Decursive started reporting the error I downloaded BugSack and BugGrabber and proceeded to disable my addons one at a time. Decursive was SO sure it was an addon that was causing the issue.

However after removing ALL of my addons except for the two bug reporting ones and resetting my UI, I could STILL reproduce this error quite easily. Simply open one profession window and then click on another profession to open a different window. Cooking, First Aide, Alchemy, Archaeology all produce the error. It does seem to occur more when one profession window is open and then another is clicked, but it is QUITE easy to reproduce with relative ease.

I’m not sure if it is related to the Archaeology bug that has been reported since May that stops progression due to not showing solves correctly, but it might be.

Thanks.

WHILE FISHING (no other Interface open)

Message: …lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:71: attempt to index field ‘SubClassDropdown’ (a nil value)
Time: Wed Jan 1 12:38:27 2025
Count: 10
Stack: …lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:71: attempt to index field ‘SubClassDropdown’ (a nil value)
[string “@Interface/AddOns/Blizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua”]:71: in function `TradeSkillFrame_SetupSubClassDropdown’
[string “@Interface/AddOns/Blizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua”]:160: in function <…lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:151>

Locals: self = TradeSkillRankFrame {
}
tbl =

{
1 = “Elixir”
2 = “Other”
3 = “Potion”
4 = “Miscellaneous”
5 = “Metal & Stone”
6 = “Other”
}
(*temporary) = nil
(*temporary) = nil
(*temporary) = “Metal & Stone”
(*temporary) = “attempt to index field ‘SubClassDropdown’ (a nil value)”

USING HEARTHSTONE to EVERLOOK (no other Interface open)

Message: …lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:71: attempt to index field ‘SubClassDropdown’ (a nil value)
Time: Wed Jan 1 15:26:52 2025
Count: 71
Stack: …lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:71: attempt to index field ‘SubClassDropdown’ (a nil value)
[string “@Interface/AddOns/Blizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua”]:71: in function `TradeSkillFrame_SetupSubClassDropdown’
[string “@Interface/AddOns/Blizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua”]:160: in function <…lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:151>

Locals: self = TradeSkillRankFrame {
}
tbl =

{
1 = “Bandage”
2 = “Other”
}
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = “attempt to index field ‘SubClassDropdown’ (a nil value)”

I’m honestly not sure why it reproduces so easily for you all and not for us, but the engineer working on it did manage to start reliably reproducing it before the break.

3 Likes

Thanks for replying Kehtryllia and giving some hope on this one. It does occur annoyingly often :slight_smile: Looking forward to your bug patch.

1 Like

ON TELEPORT TO ORGRIMMAR (no other Interface open)

Message: …lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:71: attempt to index field ‘SubClassDropdown’ (a nil value)
Time: Tue Jan 7 06:24:52 2025
Count: 1
Stack: …lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:71: attempt to index field ‘SubClassDropdown’ (a nil value)
[string “@Interface/AddOns/Blizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua”]:71: in function `TradeSkillFrame_SetupSubClassDropdown’
[string “@Interface/AddOns/Blizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua”]:160: in function <…lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:151>

Locals: self = TradeSkillRankFrame {
}
tbl =

{
1 = “Food & Drink”
}
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = “attempt to index field ‘SubClassDropdown’ (a nil value)”

ON “THE EYE OF THE STORM” WITNESS THE FARSEER’S VISION CINEMATIC (no other Interface open)

Message: …lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:71: attempt to index field ‘SubClassDropdown’ (a nil value)
Time: Tue Jan 7 06:27:36 2025
Count: 2
Stack: …lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:71: attempt to index field ‘SubClassDropdown’ (a nil value)
[string “@Interface/AddOns/Blizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua”]:71: in function `TradeSkillFrame_SetupSubClassDropdown’
[string “@Interface/AddOns/Blizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua”]:160: in function <…lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:151>

Locals: self = TradeSkillRankFrame {
}
tbl =

{
1 = “Food & Drink”
}
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = “attempt to index field ‘SubClassDropdown’ (a nil value)”

leatherworking trainer produces all these errors:

134x …lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:71: attempt to index field ‘SubClassDropdown’ (a nil value)
[string “@Blizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua”]:71: in function `TradeSkillFrame_SetupSubClassDropdown’
[string “@Blizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua”]:160: in function <…lizzard_TradeSkillUI/Wrath/Blizzard_TradeSkillUI.lua:151>

Locals:
self = TradeSkillRankFrame {
}
tbl =

{
1 = “Elemental”
2 = “Metal & Stone”
}
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = “attempt to index field ‘SubClassDropdown’ (a nil value)”

Okay, with the client build that we deployed yesterday, we’ve fixed a number of these errors. Please let us know about any that still crop up if you’re on the latest build!

As of 1/14/25, the latest build is 58558. You can check the client build under the Play button in the Battle.net Desktop app. If your build number is 58558 or higher, then you have the fixes.

2 Likes

I have tested opening my profession windows now over three different sessions. No report of bug or C stack overflow error observed thus far.

This still has not fixed the Archaeology display bug, so I am guessing they are not related.

Thanks.

1 Like

Thanks! I’m very busy for the rest of today, but I’ll try to look into it tomorrow. :heart:

I’m not personally familiar with this issue, so if you could describe what you mean by “not showing solves correctly”, that would be fantastic.

Edit: Disregard that last request. One of my meetings today wrapped up a little early and I found your thread and grabbed it down here. Taking a peek now. Since that is definitely an unrelated issue, I’ll post any updates in that thread if I have any.

1 Like

KK, over the long weekend here in New Zealand I have not encountered this bug again. Unless others have, I believe you can put this one down as resolved with my many thanks!! :slight_smile: