mirror of
https://github.com/ProxymanApp/Proxyman.git
synced 2026-04-27 09:05:54 +03:00
[GH-ISSUE #849] protobuf .proto added Successfully , unable to resolve message type... #843
Labels
No labels
Discussion
Feature request
In Progress...
Plugins
Waiting response
Windows
Windows
bug
duplicate
enhancement
feature
good first issue
iOS
macOS 10.11
question
wontfix
✅ Done
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Proxyman#843
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Tawenxd on GitHub (Apr 6, 2021).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/849
Originally assigned to: @NghiaTranUIT on GitHub.
Proxyman version? (Ex. Proxyman 1.4.3)
macOS Version? (Ex. mac 10.14)
Steps to reproduce
Expected behavior
Screenshots (optional)
@NghiaTranUIT commented on GitHub (Apr 6, 2021):
@Tawenxd can you share with me the name of your message in the proto file?
Maybe there is a message that Proxyman hasn't supported yet.
and what proto version are you using? 🤔
@Tawenxd commented on GitHub (Apr 6, 2021):
@NghiaTranUIT proto 3
@florentmorin commented on GitHub (Oct 24, 2021):
Same problem here.
My sample code
category.prototask.prototasksresponse.proto@NghiaTranUIT commented on GitHub (Oct 25, 2021):
Thanks for the file @florentmorin I will check out this week 👍
@basic1aw commented on GitHub (Nov 15, 2021):
I just encountered the same problem, any interim solution or update here
@NghiaTranUIT commented on GitHub (Nov 17, 2021):
@florentmorin I found there are multiple issues from your proto files:
When adding the
task.proto, Proxyman prints this log (Sorry that Proxyman didn't display any error alert)Here is the correct version:
category.prototask.prototaskresponse.protoThe difference from your original proto files:
syntax = "proto3";must be located on the top of the filegoogle.protobuf.Timestampinstead ofTimestampimport "google.common.proto";category.proto->task.proto->taskresponse.proto(It's a bug from Proxyman)Then Proxyman can capture and parse it properly.
Conclusion
I agree that it's a huge challenge issue from Proxyman 😿
I suppose that I should display the error and instruct the user to generate a proper proto file.
@NghiaTranUIT commented on GitHub (Nov 17, 2021):
To fix it, I will write an auto-correction when you guys import the protobuf file. It will automatically fix it 👍
@florentmorin commented on GitHub (Nov 17, 2021):
My bad. Thank you! 🙏
@NghiaTranUIT commented on GitHub (Nov 17, 2021):
it's not your fault @florentmorin. Just wondering: Are your proto files automatically generated? If yes, which tool is it? 🤔
@NghiaTranUIT commented on GitHub (Nov 20, 2021):
Hey @florentmorin @basic1aw and @Tawenxd, if you don't mind, please try this Beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_2.35.0_Fix_protobuf_issue.dmg
Proxyman now can automatically fix the issue on your imported Proto file 👍
However, you have to import in the correct order of dependency (Take a look at this example: https://github.com/ProxymanApp/Proxyman/issues/849#issuecomment-971176920)
Additionally, it will display the error when importing the file.
@florentmorin commented on GitHub (Nov 27, 2021):
@NghiaTranUIT Sorry, but I have a problem with timestamp import.
With this syntax, it works with Node / Swift, but don't work with Proxyman:
While it's the opposite with: