The only solution I have found is to bump the version number in the
.podspec for your proto files.
On Monday, November 9, 2015 at 12:14:34 PM UTC-5, Rob Cecil wrote:
>
> I'm using Cocoapods and my initial project build succeeds. Steps
>
> 1. Created .podspec referencing my .protos and output
I'm using the objective-c version Protobufs.
I have a .proto defined as
message RangeData {
int32 rows = 1;
int32 columns = 2;
bytes data = 3;
}
The server-side has been developed in C#/.Net. I'm able to successfully
send/receive and unpack the data from the 'data' field 3 above. In the c#
Hi Rob,
unfortunately Cocoapods wants to distance themselves from the use cases of
a build system, so the solution you've found is the only one that fits its
system.
Another, a bit more blunt, way to make Cocoapods rerun the
"prepare_command" commands is to delete your workspace and
I am using v3.0.0-beta-1
Based on a quick read of the code I thought
google/protobuf/util/internal/protostream_objectwriter.cc
was not doing error checks in method
ProtoStreamObjectWriter::AnyWriter::RenderDataPiece
There was a TODO to make attention to status which seem to have been fixed
[CC: Jon for the C# side and TVL for the ObjC side]
Hi Rob!
when you say:
> I am currently taking a object array in C# and packing that into the
ByteString.
How are you accomplishing that? I see from your example that the elements
of your array aren't proto messages, so maybe .Net has its
