Failure to update screen after issue with submodule

Steps to reproduce:

1. Create a project with a submodule
2. The submodule should have some problem such that the remote can't be fetched
3. Change branches in the main project

Observed:

You get the expected error when SourceTree tries to fetch the submodule but the branch display panel on the left-hand side shows that the previously checked out branch is the current branch even though (via inspection with get CLI), the branch you tried to check out was checked out. 

So the checkout was successful, at least in that it became the current branch of the main repository, but the issue with the submodule seems to have circumvented update of the branch panel.

Expected:

 I would expect that what SourceTree indicates as the current branch would ALWAYS be the same as what the git command line (via "git status") says is the current branch