On Mon, Oct 17, 2016 at 8:17 AM, Bastien Mayard wrote:
> I reproduced the issue on my Nexus 6P/Android N.
>
> It seems to be linked to InstantRun. When I disable it, code works fine.
>
Can you add this info to the issue tracker:
https://github.com/google/protobuf/issues/2217 ?
I filed a bug report https://github.com/google/protobuf/issues/2217.
And it happens on ARM as well. Nexus 6P, Android 7
Regards
On Wednesday, March 11, 2015 at 2:09:30 AM UTC+1, Patrick Linehan wrote:
>
> Nearly 5 years later, I found myself having the same problem.
> Perfectly-valid
@Patrick: Wow, what a great, great find. Congratulations.
Out of the sudden my very old project came up with the same exception,
without any small changed in the code made by me. But as usual Android
Studio has changed nearly every day: Updates, deprecations, changes
everywhere.
I tried to
On Tue, Mar 10, 2015 at 5:09 PM, Patrick Linehan pline...@gmail.com wrote:
A simple workaround is to modify the compiler output to make both
memoizedIsInitialized and isInitalized into ints. This avoids any need for
casting or sign extension.
Wait what? If this is really the problem, why not
Nearly 5 years later, I found myself having the same problem.
Perfectly-valid serialized protobufs generated in C++ for message types
with no required fields suddenly started throwing
InvalidProtocolBufferException: Message was missing required fields.
exceptions in Java.
The problem is, as
If Henner's answer didn't help, you'll need to provide a small,
self-contained example which reproduces the problem.
On Fri, Apr 16, 2010 at 11:05 AM, SyRenity stas.os...@gmail.com wrote:
Hi.
I'm getting occasionally the following error below in my Java app:
On Fri, Apr 16, 2010 at 11:05, SyRenity stas.os...@gmail.com wrote:
Hi.
I'm getting occasionally the following error below in my Java app:
com.google.protobuf.InvalidProtocolBufferException: Message was
missing required fields. (Lite runtime could not determine which
fields were missing).