Service Fabric Deploy failing with Service Fabric SDK 2.5

VSTS task failing after VS 2017 upgraded to the latest tooling and SDK 2.5

2017-04-06T11:24:08.0027632Z Searching for path: C:\a\r1\a\Service Fabric Cluster\sf-xml\PublishProfiles\Cloud.xml
 
2017-04-06T11:24:08.0307635Z Found path: C:\a\r1\a\Service Fabric Cluster\sf-xml\PublishProfiles\Cloud.xml
 
2017-04-06T11:24:08.1097652Z Searching for path: C:\a\r1\a\Service Fabric Cluster\sf-package
 
2017-04-06T11:24:08.2907697Z Found path: C:\a\r1\a\Service Fabric Cluster\sf-package
 
2017-04-06T11:24:12.0809854Z Successfully connected to cluster.
 
2017-04-06T11:24:12.1415166Z Searching for path: C:\a\r1\a
 
2017-04-06T11:24:12.2285248Z No items were found with search pattern C:\a\r1\a.
 
2017-04-06T11:24:12.2335243Z Overriding upgrade settings specified in publish profile with the settings specified in the VSTS Task.
 
2017-04-06T11:24:15.7001754Z ##[error]Exception while parsing XML file: C:\a\_temp\TestApplicationPackage_3147697723\fmdmafrq.0h0\sf-package\ApplicationManifest.xml
 
FileName: C:\a\_temp\TestApplicationPackage_3147697723\fmdmafrq.0h0\sf-package\ApplicationManifest.xml
 
2017-04-06T11:24:15.7501760Z ##[section]Finishing: Deploy to Unsecure Cluster

[aloneguid]

@Kwal @bishal-pdMSFT much appreciated, and the workaround mentioned resolves the issue immediately.

[kwal]

Disabling the generation of the IDs (as referenced in the issue over in the SF repo) does the trick.