ProxymanApp / ProxymanApp/Proxyman
Even after importing protobuf schema, the message type isn't found
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7k
- Forks
- 237
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce this on Proxyman 5.12.2 with macOS 15.2 by importing the generated .desc files, including api.desc. Compare request and response message-type lookup, then restart the app and check whether proto.api. types persist. Done means imported request types resolve consistently after import and restart, with useful errors when a descriptor cannot be used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- api, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100