iTerm Key Bindings Overwritten During Onboarding Configuration

Bug Description
When enabling the "\n" shift-enter binding for iTerm during onboarding, the binding was added to my iTerm config, but also all other key bindings (a large number of them) were removed. It was confusing because my iTerm tab navigation keys stopped working, for example. I was able to restore the defaults manually through iTerm settings, and keep the new shift-enter binding. You can just close this, but I figured I'd report it in case it can help improve. I don't have tons of customized bindings, but if I did, and I hadn't saved them as a preset, I'd have been sad/mad.

Environment Info

• Platform: darwin
• Terminal: iTerm.app
• Version: 1.0.59
• Feedback ID: f28ffe5c-952f-463e-bd5a-f0736f40a86f

Errors
No errors. Rather, my iTerm config was borked because all key bindings except for the new one had been removed.