-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"GenericArguments[0], 'SystemMessageTest', on 'Google.ProtocolBuffers.IBuilderLite`2[TMessage,TBuilder]' violates the constraint of type parameter 'TMessage'." #100
Comments
I manage to get the full stack trace here
|
Without knowing anything about (I've never advertised Unity as a supported platform for Protocol Buffers, and I've never used it myself. I'm not going to install it just to chase down this problem - particularly not right now, as I'm on holiday at the moment.) As mentioned elsewhere, you could try applying ironhidegames/protobuf@83bcfef - but it's not clear that it's the same issue that that one fixes. I suggest you contact Unity support about this - they're more likely to know about the quirks of Mono at that particular version and running on iOS than I do. |
Ok I had fix this via Unity side , it is not because of Protocol buffer . Thanks a lot. |
What steps will reproduce the problem?
1.Build a simple .proto file then convert into .cs file ( simple .proto file can just be a simple class with single data )
2.Import into Unity project ( with .cs file and .dll file for windows phone 8 ) - Unity v5.0.2p1
3.Build Unity project into Windows phone 8 project
4.Run on device in RELEASE mode => see it crashed.
I cant see the whole stack trace since everything is "Null" the only message I got from debug data is this
"GenericArguments[0], 'SystemMessageTest', on 'Google.ProtocolBuffers.IBuilderLite`2[TMessage,TBuilder]' violates the constraint of type parameter 'TMessage'."
But by doing exactly my step will get you guys there . ( dont run in Debug mode since it will be ok , run in Release mode instead )
Thanks.
The text was updated successfully, but these errors were encountered: