Unfortunately getting the same error :( Hope it gets updated soon.EDIT: Firmware 2.6.1 seems to fix it!
Looks to be an issue with the 2.6.0 SDK. Need a new build to solve.