Apigee Emulator v1.14.2 in VSCode Failed to deploy environment

Hello,

I am encountering an issue with the Apigee Emulator (v1.14.2) in Visual Studio Code. I am unable to deploy a simple environment with an echo proxy. When I attempt to deploy, the operation fails with a 500 error, and I see an error related to parsing the deployment report.

Interestingly, the same configuration and process work perfectly with an older version of the emulator (v1.9.2).

What I’ve already done:

  • I downloaded the newest version of the Apigee Emulator extension in Visual Studio Code, completely uninstalling and reinstalling.
  • I have configured the emulator to use version 1.14.2, and deleted the container and image multiple times, reinstalling later
  • I have created a simple echo API proxy, tried with other proxy presets but same result.
  • I have confirmed that the deployment is successful when I switch the emulator version back to 1.9.2 with no other changes.

Here are the error messages I’m seeing:

VSCode Console Output:

06/13/2025 6:45 PM EMULATOR INFO Deploying environment testenv, to Container apigee-1.14.2 (1.14.2)
06/13/2025 6:45 PM EMULATOR ERROR Error parsing deployment report as JSON
06/13/2025 6:45 PM EMULATOR ERROR null
06/13/2025 6:45 PM EMULATOR ERROR Environment testenv deployment, to Container apigee-1.14.2 (1.14.2) failed with Error: 500
06/13/2025 6:45 PM EMULATOR ERROR Deploy to Container apigee-1.14.2 (1.14.2), failed with Error: Environment testenv deployment, to Container apigee-1.14.2 (1.14.2) failed with Error: 500

Unfortunately, I’m unable to upload logs that appeared directly in the docker container as the forum won’t let me, probably due to their length. Truncated, these are the log lines that appear when I try to deploy the environment:

2025-06-13 23:58:35 {"level":"SEVERE","thread":"NIOThread@18","mdc":{},"className":"com.apigee.messaging.configuration.MessageProcessorServiceImpl","method":"loadContract","severity":"SEVERE","message":"Failed to load the contract null"
2025-06-13 23:58:35 {"level":"SEVERE","thread":"NIOThread@18","mdc":{},"className":"com.apigee.communication.rest.HandlerDetails","method":"process0","severity":"SEVERE","message":"failed to process request handler found for request com.apigee.protocol.http.msg.RequestURI@f2c1109"

Relevant Code and Configs

ECHO-proxy Endpoint (default.xml):

<ProxyEndpoint name="default">
  <HTTPProxyConnection>
    <BasePath>/echo</BasePath>
  </HTTPProxyConnection>
  <RouteRule name="echo"/>
</ProxyEndpoint>

Environment Deployment (deployment.json):

{
  "proxies": [
    {
      "name": "ECHO-proxy"
    }
  ],
  "sharedflows": []
}

Directory Tree of Apigee Workspace:

.
β”œβ”€β”€ src
β”‚      β”œβ”€β”€ main
β”‚      β”‚      └── apigee
β”‚      β”‚          β”œβ”€β”€ apiproxies
β”‚      β”‚          β”‚      └── test
β”‚      β”‚          β”‚          └── apiproxy
β”‚      β”‚          β”‚              └── proxies
β”‚      β”‚          β”‚                  └── default.xml
β”‚      β”‚          β”œβ”€β”€ environments
β”‚      β”‚          β”‚      └── testenv
β”‚      β”‚          β”‚          β”œβ”€β”€ debugmask.json
β”‚      β”‚          β”‚          β”œβ”€β”€ deployments.json
β”‚      β”‚          β”‚          β”œβ”€β”€ flowhooks.json
β”‚      β”‚          β”‚          β”œβ”€β”€ keystores.json
β”‚      β”‚          β”‚          └── targetservers.json
β”‚      β”‚          └── sharedflows
β”‚      └── tests
└── target
    └── emulator
        └── testdata
            β”œβ”€β”€ 5040f7b90fcf
            β”‚      └── analytics_results.json
            β”œβ”€β”€ 841ef454aabf
            β”‚      └── analytics_results.json
            └── b4d1e6ab8ac6
                └── analytics_results.json

Could someone please help me understand what might be causing this issue and how I can resolve it?

Thank you!

Hey @McCloudLovin ,

We’ve seen that your question hasn’t gotten a response yet. We’ll keep checking in on this thread and encourage other members to share their thoughts.

@McCloudLovin - while we look into this. Can you try with a previous version of the emulator. You can add that version in your VSCode settings.json

For example

β€œcloudcode.apigee.emulators”: [
β€œ1.12.0”
]

1 Like

I too see deployment fails for me using 1.14.2 with the following errors:

06/27/2025 11:48 AM EMULATOR INFO Deploying environment local, to Container 1.14.2 (1.14.2)
06/27/2025 11:48 AM EMULATOR ERROR Error parsing deployment report as JSON
06/27/2025 11:48 AM EMULATOR ERROR null
06/27/2025 11:48 AM EMULATOR ERROR Environment local deployment, to Container 1.14.2 (1.14.2) failed with Error: 500
06/27/2025 11:48 AM EMULATOR ERROR Deploy to Container 1.14.2 (1.14.2), failed with Error: Environment local deployment, to Container 1.14.2 (1.14.2) failed with Error: 500

Also fails in 1.13.3.
Works fine in 1.12.4.

Was the root cause for this ever figured out / fixed?

1 Like

We are seeking to migrate from Apigee Edge to X and this is a current blocker to our work, is there any indication when this will be looked into?

We tried 1.14.3 but this failed as described.

Version 1.12.4 is the latest version that works for us locally however there are syntax differences which fails when we proceed to deployment in an actual environment.

We use docker desktop during development.

Having the emulator available is essential for our SDLC both from a developer experience and test automation point of view and a major blocker to our aspirations to implement continuous deployment for our API gateway changes.

which version of docker are you using? there is a bug verified with docker latest versions

I had tried the older docker desktop version but still the same issue, I’ve also tried Colima but no luck. I’ve tested both on a Mac (ARM) and Windows PC with a simple hello world proxy but the same error persists.

This issue was caused by another internal issue of apigee-emulator image and it has been fixed in 1.15.1.

Please try the latest 1.15.1 image and let us know if you still see this issue or not.

Thanks!

1.15.1 image works on Docker Desktop 4.41.2, still broken on latest Docker Desktop but at least I’ve got something to work with now which is awesome. Thank you @felixryu !

1 Like