1 of 1 people found this helpful
If your Azure Sphere OS has updated to 19.09, then you also need to install the new 19.09 SDK and rebuild the application.
In Visual Studio you will need to adjust the target API Set that's used in the build (previous 2+Beta1905 APIs are no longer applicable)
module is 188.8.131.52731, SDK is 2+Beta1905
updater say update
after update same version, same error...
More info on this topic is available here:
PS: Beta APIs can change. Builds with an older SDK that only made use of production APIs are not affected by OS updates
Latest 19.09 SDK reports as follows:
Azure Sphere Utility version 184.108.40.206479
To see the SDK version:
To see the OS version:
azsphere device show-ota-status
Command completed successfully in 00:00:00.1611137.
BTW: I test on Windows 10, 8 and 7 too
so 19.09 not work with Beta1905 ??
$ ./azsphere device show-ota-status
Your device is running Azure Sphere OS version 19.09.
The Azure Sphere Security Service is targeting this device with Azure Sphere OS version 19.09.
Your device has the expected version of the Azure Sphere OS: 19.09.
Command completed successfully in 00:00:04.9280898.
I haven't changed anything.
This came as a surprise today...
I find workaround for now: pack image as --sysroot 2 ( but is compiled with Beta1905 ) no errors, work ....
Nice !? .... tested on two PC
azsphere device sideload deploy --imagepackage PATH/app.image --verbose
Azure Sphere Utility version 220.127.116.11731
Copyright (C) Microsoft Corporation. All rights reserved.
Start time (UTC): Thursday, 10 October 2019 07:31:03
Deploying 'PATH\app.image' to the attached device.
verbose: No SerialSlipToTunService port is set in the registry; defaulting to 56665.
error: This app targets Beta APIs that may no longer be supported by this device. The app may fail to start or otherwise behave unexpectedly. Please upgrade your app
to target the API sets that this device supports. Use the '--force' flag to force this operation.
error: Command failed in 00:00:02.1843316.
Azure Sphere Utility version 18.104.22.168731 ( there is no new versions ) same error