gRPC - Sending Incorrect Requests

[ellgreen]

Is there an existing issue for this?

• [x] I have searched the tracker for existing similar issues and I know that duplicates will be closed

Describe the Issue

We have encountered an issue where Postman will send a different gRPC request body from the tab that is currently selected.

For example, I have an example gRPC server with two requests: SayHello, and SayGoodbye. If I open SayHello in a tab, and then visit SayGoodbye and send the request, Postman will send the body from the previously selected tab.

This has been reproduced on both MacOS and Windows.

Steps To Reproduce

1. Run a gRPC server that has a service with methods that share a proto message, for example I have a demo repo where two requests share a Person message: service.proto
2. Create a tab for each method: SayHello, and SayGoodbye
3. Populate the body for SayHello with {"person":{"name":"Mr. Hello"}}
4. Populate the body for SayGoodbye with {"person":{"name":"Mr. Goodbye"}}
5. Invoke SayGoodbye, you should receive: { "message": "Goodbye, Mr. Goodbye" }
6. Switch to SayHello tab and invoke. You should receive: { "message": "Hello, Mr. Goodbye" } - This is incorrect, you should see Mr. Hello as the name here. Invoke again and it should fix itself.

Screenshots or Videos

Operating System

macOS

Postman Version

11.37.5

Postman Platform

Postman App

User Account Type

Signed In User

Additional Context?

No response

[parthverma1]

Hi @ellgreen

Thank you for reporting the issue.

I was able to reproduce the issue and will provide an update once a fix has been implemented.

[glebselyukov]

In the latest versions of the app, server reflection keeps breaking, forcing users to manually refresh reflection before each request. Otherwise, the proto structure from a different method gets used instead of the correct one.

[apoorvgupta03]

Hey @glebselyukov, thanks for reporting this. Can you please elaborate on the steps that you are taking in this workflow to understand the issue better? A screen recording would be really helpful. 1 - what error exactly do you face? Do you face any abrupt error related to server reflection or your methods list disappear? 2 - If you are using a server with all methods reflected, and you sent request with method 1, then you switch to method 2, does the server reflection break?
 3 - Or when you change the method, the example messages are generated with previous selected method’s structure? 

 4 - are you changing the service definition in between sending requests, and facing any kind of error?


[apoorvgupta03]

Hey @ellgreen, We have released a fix for this in the latest version of Postman, please let us know if you're still facing this issue after updating the app.

[ellgreen]

This looks like it's working correctly now, thanks for the speedy fix @apoorvgupta03!