Closed GoogleCodeExporter closed 9 years ago
Guava 17.0
Original comment by smrtprj...@gmail.com
on 17 Jul 2014 at 10:45
String parameters aren't null.
Original comment by smrtprj...@gmail.com
on 17 Jul 2014 at 2:34
That's pretty strange. The UOE is clearly coming from here:
public static final CharMatcher JAVA_ISO_CONTROL =
inRange('\u0000', '\u001f')
.or(inRange('\u007f', '\u009f'))
.withToString("CharMatcher.JAVA_ISO_CONTROL");
(https://code.google.com/p/guava-libraries/source/browse/guava/src/com/google/co
mmon/base/CharMatcher.java?name=v17.0#212)
But withToString is being called on a CharMatcher returned by or(...), and the
Or CharMatcher definitely overrides withToString and doesn't throw UOE from it.
Is there another version of Guava on your classpath somehow? Seems unlikely to
cause this issue given that the problem here seems to be constrained to just 1
class, but probably worth checking. I also wonder if the obfuscation that
appears to have been done could be causing it somehow. This obviously doesn't
normally happen, as it would cause CharMatcher and anything that uses it to
never work.
Original comment by cgdecker@google.com
on 17 Jul 2014 at 3:53
Hi,
I have on guava lib in the project, but I use proguard.
Original comment by smrtprj...@gmail.com
on 17 Jul 2014 at 4:55
one guava
Original comment by smrtprj...@gmail.com
on 17 Jul 2014 at 4:55
I have to think this is somehow caused by proguard. I wonder if it's for some
reason stripping out the override of withToString from CharMatcher.Or, causing
the default implementation of withToString on CharMatcher to be called?
Original comment by cgdecker@google.com
on 17 Jul 2014 at 5:09
I'm no an expert, I cannot help you :D
But if it's a proguard thing why this comes in one device? Is it possibe?
Why one device? Or it's a rare bug and it was just an accident?
Original comment by smrtprj...@gmail.com
on 17 Jul 2014 at 5:59
I really have no idea... I don't know much about proguard myself. For Guava
17's original source code, what happened should be impossible. So at the very
least I don't think this is a problem with Guava itself. What exactly is
causing it, though, I'm not sure.
Original comment by cgdecker@google.com
on 17 Jul 2014 at 6:05
Is it uptodate? Seems to be a bit old
https://code.google.com/p/guava-libraries/wiki/UsingProGuardWithGuava
Original comment by smrtprj...@gmail.com
on 21 Jul 2014 at 4:42
This issue has been migrated to GitHub.
It can be found at https://github.com/google/guava/issues/<issue id>
Original comment by cgdecker@google.com
on 1 Nov 2014 at 4:08
Original comment by cgdecker@google.com
on 1 Nov 2014 at 4:17
Original comment by cgdecker@google.com
on 3 Nov 2014 at 9:07
Original issue reported on code.google.com by
smrtprj...@gmail.com
on 17 Jul 2014 at 10:44