some error with recent update in bcc when accept (or give up) quest

3x ...ceQuestie\Modules\Tracker\QuestieTracker.lua:2213: attempt to index field 'collapsedQuests' (a nil value)
[string "@Questie\Modules\Tracker\QuestieTracker.lua"]:2213: in function RemoveQuest' [string "@Questie\Modules\Quest\QuestieQuest.lua"]:417: in function CompleteQuest'
[string "@Questie\Modules\QuestieEventHandler.lua"]:235: in function CompleteQuest' [string "@Questie\Modules\QuestieEventHandler.lua"]:209: in function <...rfaceQuestie\Modules\QuestieEventHandler.lua:203> [string "=[C]"]: ? [string "@Questie\Libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua"]:29: in function <...tie\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:25> [string "@Questie\Libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua"]:64: in function Fire'
[string "@Questie\Libs\AceEvent-3.0\AceEvent-3.0-4.lua"]:120: in function <...ceQuestie\Libs\AceEvent-3.0\AceEvent-3.0.lua:119>

3x Questie\Modules\Quest\QuestieQuest.lua:389: attempt to index field 'collapsedQuests' (a nil value)
[string "@Questie\Modules\Quest\QuestieQuest.lua"]:389: in function `val'
[string "@Questie\Modules\TaskQueue.lua"]:8: in function <Questie\Modules\TaskQueue.lua:6>

Locals:
(*temporary) = nil
(*temporary) = 9829
(*temporary) = "attempt to index field 'collapsedQuests' (a nil value)"
questId = 9829

Should be fixed with #3206 .

Couple questions:
You don't have Questie tracker enabled?
If not enabled, would error go away if you? :

1. enable Questie tracker on the character getting error
2. /reload
3. disable tracker as originally
4. test if helped

Should be fixed with #3206 .

Couple questions: You don't have Questie tracker enabled? If not enabled, would error go away if you? :

1. enable Questie tracker on the character getting error
2. /reload
3. disable tracker as originally
4. test if helped

enabled questie tracker no error by accept(give up or complete) quest

and then

no error after disable tracker & reload 'each character'

Perfect, thanks for coming back to this @SunnyJang38

The next release will contain the fix from #3206 for it.