Even after importing protobuf schema, the message type isn't found

[heijink]

Description

I've imported the *.desc files that I generated from the *.proto files using protoc. I can see the responses, but the requests keep telling me that it can't find the relevant message type, even though I can select it. See screenshots.

Steps to Reproduce

See screenshots:

The request message type isn't found:

But I'm able to select it here.

Moreover, if I restart, all the proto.api.* messages are gone. If I then re-import api.desc in the schema, all the proto.api.* message types are back.

It's possible there's something wrong with api.desc, but I'm getting no error messages when importing it, so it's hard to know what's going on.

Environment

• App version: Proxyman 5.12.2 (51202)
• macOS version: macOS Sequoia 15.2

[NghiaTranUIT]

May I ask: When it loads proto.api.CheckSumRequest successfully, can Proxyman decode your Request Protobuf Body? Just to verify that this feature is working fine, and the bug is how it loads at launch

[jaroslavas]

I have very similar issue with protobuf. One of the fields is following:
repeated int32 start_time_offsets = 20;

If I add int values that are small, like 1 or 5, message is decoded fine, with or without the desc file loaded. But if a number higher than 127 is added to array, I get missing message type error as on the screenshot in the first message.
For testing sake I've tried changing type to double, and with double it works fine.

Let me know if you need more info for debugging.