Qt project fails to import cleanly

We're experiencing two issues with the new plugin release as follows, whereas the previous version was working for project import without issue:

1. When we import a component from our large application, a .sln file is generated but we are presented with a dialog that states "Object reference not set to an instance of an object.". The Output window shows:
   (Import): Success: 55
   (qmake) : Exit Code: 0
   If we subsequently open the generated .sln file, that loads fine which makes me think it's a post-conversion step that has an issue when trying to auto load the generated solution.
2. Whilst investigating this issue, I found that it got further by removing one of our CONFIG definitions. This may be odd, but the way our build is configured, for cross platform building, we turn off the debug_and_release configuration by specifying CONFIG -= debug_and_release, and then we set the configuration based off how the developers have launched it, by calling either CONFIG += release or CONFIG += debug. This worked fine in the previous addin. I've managed to produce similar behaviour with the attached simple project. However, in this instance, it does actually auto load, but reports a message that says "Could not convert project file QtVsTest.vcxproj to Qt/MSBuild."

Fundamentally I think something is amiss if the project removes the debug_and_release configuration, which for us would be a sizable change to our build config. Since we can at least load the project subsequently it's not stopping us working completely with the plugin.

Would it be possible in a future version to be able to turn on some verbose logging during the import to help attempt to diagnose whether the problem is within the plugin or with our build definition?

In the attached file are two files, with a .bad and .good extension, which the .bad generated when debug_and_release is removed from the config.

 This is using VS2015 with QT 5.9.4.