[TIMOB-24147] Windows: Unable to "new" EasClientDeviceInformation
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Medium |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2016-11-17T00:32:09.000+0000 |
| Affected Version/s | Release 6.1.0 |
| Fix Version/s | Release 6.1.0, Hyperloop 2.1.0 |
| Components | Windows |
| Labels | n/a |
| Reporter | Kota Iguchi |
| Assignee | Kota Iguchi |
| Created | 2016-11-15T13:00:52.000+0000 |
| Updated | 2017-04-19T02:07:49.000+0000 |
Description
Following up from initial Hyperloop PR, originally reported by [~gmathews].
Attempt to create instance from constructor for
Windows.Security.ExchangeActiveSyncProvisioning.EasClientDeviceInformation fails. It ends up throwing null is not a constructor error.
var EasClientDeviceInformation = require('Windows.Security.ExchangeActiveSyncProvisioning.EasClientDeviceInformation'),
deviceInfo = new EasClientDeviceInformation();
alert('SystemFirmwareVersion: ' + JSON.stringify(deviceInfo.SystemFirmwareVersion));
https://github.com/appcelerator/titanium_mobile_windows/pull/894
Validated fix with this environment: Node Version: 6.10.1 NPM Version: 4.4.4 Appc CLI: 6.2.0 Appc CLI NPM: 4.2.9 Titanium SDK version: 6.1.0v20170417190415 Appcelerator Studio, build: 4.8.1.201612050850 OS: Windows 10.0.14393 Targets: Windows 8.1 & 10 Devices. Windows 10 Emulator Hyperloop 2.1.0 I installed and executed the demo code above on both emulator and Windows Devices 8.1 and 10. No errors were thrown. On the devices, an alert popped up displaying the phone's system firmware version. Checking the settings, the firmware version matched.