400 BadRequest when Publishing Azure App
See original GitHub issueWe have written th Issue Type: Bug
I haven’t opened VS Code in about a week. Previously I was able to easily publish to my Azure Function app. Now after the latest VS Code update, I am unable to publish my functions. I receive the following error each time I attempt it:
11:03:57 AM eqix-automation-dev: Starting deployment… 11:03:58 AM eqix-automation-dev: Creating zip package… 11:03:58 AM eqix-automation-dev: Zip package size: 48.6 kB 11:07:58 AM: Error: 400.0 BadRequest
Extension version: 1.6.1 VS Code version: Code 1.66.1 (8dfae7a5cd50421d10cd99cb873990460525a898, 2022-04-06T14:50:12.141Z) OS version: Windows_NT x64 10.0.19042 Restricted Mode: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel® Xeon® E-2276M CPU @ 2.80GHz (12 x 2808) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: unavailable_off vulkan: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 31.76GB (19.19GB free) |
| Process Argv | –crash-reporter-id f981abc5-56ff-448f-922b-3c168723e687 |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
pynewfile477:30463512
Issue Analytics
- State:
- Created a year ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
Azure app service some requests returns 400 Bad Request ...
Any ideas on what can cause this error? Bad Request. The request could not be understood by the server due to malformed syntax....
Read more >Web api azure 400 Bad Request - Microsoft Q&A
A 400 error means there is a problem with the client request. If the topic property of the MessageFirebaseRequest class is not a...
Read more >Problem Deploying the Site on Azure WebAPP using Devops ...
While deploying the web app on azure devops, it failed with reason Bad Request (Code:400) and there is no much detail behind it....
Read more >All of a sudden getting 400 Bad Request responses ... - Reddit
All of a sudden getting 400 Bad Request responses when using Zip Deploy (Azure Web App). So I was able to deploy just...
Read more >"func azure functionapp publish" gives error code 400 #778
HttpRequestException: Response status code does not indicate success: 400 (Bad Request). ... EDIT 2: I tried pushing an that does not exist, func ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Did a new VS Code install on a freshly imaged OS and was able to pull from GitHub and deploy. This leads me to believe the update of VS Code is not working on my PC. Potentially a disk or OS issue. I think the can be resolved for now. Could be the updater/installer but too many moving parts to say for sure.
@killinterpol Thanks so much for following up with a resolution. Yeah, this is very difficult for us to determine what the root issue is, but definitely something weird going on. It seemed like the zipping wasn’t even working at all anymore.
I’ll go ahead and close this issue. Thanks again for filing, using our extension, and working with us so much to try to figure this out!