[TIMOB-20097] Windows: Windows 10 Mobile requires pfx
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2015-12-14T21:38:26.000+0000 |
| Affected Version/s | Release 5.2.0 |
| Fix Version/s | Release 5.3.0 |
| Components | Windows |
| Labels | notable, qe-5.3.0 |
| Reporter | Christopher Williams |
| Assignee | Christopher Williams |
| Created | 2015-12-03T15:10:24.000+0000 |
| Updated | 2016-04-28T22:43:09.000+0000 |
Description
When trying to deploy a Win 10 mobile app, they now require certs/keys like Windows Store apps do. We need to detect when there's no pfx and generate one like we do for store (or cheat and copy the temporary one from cmake's Templates/Windows folder for them to use).
We should probably just use the temporary key for dev, and have them generate an actual pfx for publishing/deploying.
Users now have to specify the pfx password and cert like we did for Windows Store apps (or will get prompted for the values). This is only for Windows 10.0 or Win 8.1 store targets.
Verified as fixed Tested on: Microsoft Lumia 640 (10) Windows Simulator (10) Windows 10 Studio: 4.6.0.201604210304 Ti SDK: 5.3.0.v20160421080259 Appc NPM: 4.2.5-3 App CLI: 5.3.0-36 Node v4.4.3 *Closing Ticket.*