* Adapt Richard's work on code signing app bundles (nrach code-signing) with latest master changes
* Small fixes
jsonwebtoken update to newer version
Remove redundant cli.ts, launch.json
Add missing slash package in sdk
Add missing yazl package in cli
* Add more accurate processing of deletion of prevous signature
Tweak hash utils to correct normalizePath behaviour on windows machines
* Extract release hooks into separated modules
* Remove ? from IReleaseHook function parameters
Add default exports for hooks
* Add notice about limitation of code signing feature usage for general release command
* Fix commentary
* Change option name for consistensy with plugins
* Fix unfinished refactoring after signingKey renaming
* Add confirmation dialog in case of using code signing
change to match the corresponding server change deployed
a couple days back.
Here are details of the issue:
// IIS and Azure web apps have this annoying behavior where %2F (URL encoded slashes) in the URL are URL decoded
// BEFORE the requests reach node. That essentially means there's no good way to encode a "/" in the app name--
// URL encodeing will work when running locally but when running on Azure it gets decoded before express sees it,
// so app names with slashes don't get routed properly. See https://github.com/tjanczuk/iisnode/issues/343 (or other sites
// that complain about the same) for some more info. I explored some IIS config based workarounds, but the previous
// link seems to say they won't work, so I eventually gave up on that.
// Anyway, to workaround this issue, we now allow the client to encode / characters as ~~ (two tildes, URL encoded).
// The CLI now converts / to ~~ if / appears in an app name, before passing that as part of the URL. This code below
// does the encoding. It's hack, but seems like the least bad option here.
// Eventually, this service will go away & we'll all be on Max's new service. That's hosted in docker, no more IIS,
// so this issue should go away then.
Use \"code-push deployment list\" to view any existing deployments and \"code-push deployment add\" to add deployment(s) to the app
if the app doesn't exist. We only show it now if the deployment doesn't exist.
* Removed these features deprecated post Mobile Center integration: (#431)
code-push app transfer
code-push collaborator
code-push session
access key rename / change TTL
showing auth types for whoami
* Added OS and platform arguments for the app add command (#432)
* Updated deployment defaults. Now... (#437)
* "code-push add add" does NOT add any default deployments
* "code-push deployment add" has a --default option to add default deployments
* "code-push release" outputs a more descriptive error if no deployments exists
* Updated CLI text around login/register/link. Also fixed... (#439)
link to go directly to mobile.azure.com, in order to not show the token at the end.
* Added .vscode settings file, to exclude generated bin directories (#440)
* Added back the collabor CLI command since the... (#441)
proxy service now supports it. It was commented out before, but I just undid that.