ArrayIndexOutOfBoundsException at okio.Base64.encode(Base64.java:137)
See original GitHub issueOS:
Android 5.1 100%
Devices:
Archos 36% condor 27% Meizu 23% HUAWEI 14%
Stacktrace:
Fatal Exception: java.lang.ArrayIndexOutOfBoundsException: length=1840; index=320371712
at okio.Base64.encode(Base64.java:137)
at okio.Base64.encode(Base64.java:125)
at okio.ByteString.base64(ByteString.java:131)
at okhttp3.Cache$Entry.writeCertList(Cache.java:683)
at okhttp3.Cache$Entry.writeTo(Cache.java:646)
at okhttp3.Cache.put(Cache.java:250)
at okhttp3.Cache$1.put(Cache.java:149)
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:131)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:125)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.logging.HttpLoggingInterceptor.intercept(HttpLoggingInterceptor.java:143)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200)
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:147)
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
Many Picasso-related tasks in the other threads.
Can provide further info if needed
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:46 (7 by maintainers)
Top Results From Across the Web
okio.Base64.encode ArrayIndexOutOfBoundsException why is ...
It is probably bug in VM at particular devices starting from 8 of November only on Android 5.1. We have found out that...
Read more >Base64 ArrayIndexOutOfBoundsException while trying to ...
It seems like it gets this exception while trying at setting the admin password - but the same directory XML configuration with the...
Read more >Dexer seems to generate code that is not compiled properly on ...
ArrayIndexOutOfBoundsException : length=2114; index=320500560 at okio.Base64.encode(Base64.java:137) at okio.Base64.encode(Base64.java:125) at okio.
Read more >ArrayIndexOutofBoundException in Base64 conversation in java
I am getting attachment body from salesforce data base. I have checked in DB that this attachment have body content in data base....
Read more >RFC 4648: The Base16, Base32, and Base64 Data Encodings
Abstract This document describes the commonly used base 64, base 32, and base 16 encoding schemes. It also discusses the use of line-feeds...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
ok, guys, AND SOLUTION IS…
wait for it…
… just disable D8…
gradle.properties >
android.enableD8=false
.Now let’s go to pub and drink a lot of beers, because I spend on this shit all 2 DAYS 😕.
Tested for you on our big project and on some small demo project just with one library (okhttp3).
@pavlus @anupdey99 As far as we (the D8 team) knows, we have worked around all the VM bugs that were uncovered by D8 generated code for okio. So, yes, this issue has been worked around and should no longer happen. We were able to reproduce using 5.1 devices as well as 4.4 devices and our workarounds make our examples run without issues.
If anyone are still seeing issues with android studio 3.1.3 please do file bug reports at: https://issuetracker.google.com/issues/new?component=317603&template=1018721
Thanks! Mads