Got the same error as sekitaka, it's kinda strange because there weren't any such problems earlier, maybe just an apple bug

Having the same issue, it's not fixed yet, unfortunately

Hi! I've been having the same problem for over a half a year now! It's very frustrating that everything was fine on iOS 14 and now we're having one more regression bug

Hey, everyone! I've been trying to fix this issue for months without any success, it just popped up after the new version of xcode was released and I was kinda hopeless. Fortunately, I've found a workaroud, it goes like this: Choose you target Build settings Optimization Level Debug Optimize for size [-Osize] It's been working well enough, but it was annoying that I couldn't look up any local variables in build time while debugging. Well, today I finally found the issue and managed to fix it. The code looked like that: switch item { case .a(var model), .b(var model), .c(var model): // cell dequeue here // model mutation here // cell configuration here from model // cell return here } The problem of that, I suppose, that we're fetching the mutable models from different cases and mutate them after that (by the way, all models are of the same struct, of course, it is legal to do so). I've changed it like that: switch item { case .a(let model), .b(let model), .c(let model): // cell dequeue here var configurationModel = model // configurationModel mutation here // cell configuration here from configurationModel // cell return here } Hope it could be useful for someone who encountered such unusual behaviour of xcode.