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
ART Runtime ArrayIndexOutOfBoundsException when instantiating Call object #1486
Comments
What's on line 46 of |
@JakeWharton Line 46 is: |
@JakeWharton Like I said in my original message, I really don't think it has to do with retrofit either...but this stack trace only appears when I instantiate my Call object. Ultimately, I feel like I am doing something wrong with the call object. But I'm just not seeing it...its unfortunate that the logcat is so unhelpful. |
Perhaps it will help. |
I love the open source community...so helpful. @letos What version did you change yours to? |
I have same issue. After downgrade gradle version to alpha3 it fixed. |
danmikita, |
@letos @sergeyfitis You guys rock! Thank you! Is there a place to file an issue with alpha-5? |
I don't know. |
Same here. |
I created a bug in the AOSP bug tracker. Thanks for your help! https://code.google.com/p/android/issues/detail?id=199105 |
Cool, thanks |
Seeing same issue that points to retrofit. Using alpha 3 did not help. We only see this issue when instant run in enabled. I also removed the api call causing crash for funsies.. No crash and all other calls Perplexed. |
…e build to 2.0.0-beta3. This is needed or compiled APKs that are installed on API 23 devices will crash when Retrofit is utilized. See issue here: - square/retrofit#1486 - https://code.google.com/p/android/issues/detail?id=199105 * Removed AsyncTasks, as they are not needed. Using Retrofit's enqueue method instead. * Removed API 23 workaround and IssuesUtil class.
I'm seeing the same problem (crash on instantiating the Call object) using gradle:2.1.0. Disabling instant run makes it work again. So looks like an interaction between Call and Instant run |
I use gradle 2.1.0. The problem only appear on my marshmallow device. But when I use emulator, the problem doesn't appear |
Try to disable Instant run. |
I was having this same problem. I upgraded the gradle plugin to The 2.2.x line of development might fix this. Not sure. I know alpha2 works for me in my situation. https://bintray.com/android/android-tools/com.android.tools.build.gradle/
I'd recommend folks give that a try. And you can keep using instant run. |
This is insane. I was having this similar problem and thought that it was the Facebook Graph API error. For me, downgrading gradle version didn't solve the problem too. I had to disable
|
Hi everyone, I have fixed this bug disabling "Instant Run", but: Is there any solution that doesn't means disable a good feature of Android Studio, or using a workarround? It happens with MarshMallow devices. Could it be a permissions problem? Thank for your comments, It was a huge help. |
Same error here ! Any solution yet ? |
The same issue... |
This is a build system problem, not a Retrofit problem. There is a bug filed in the appropriate place. |
This is a crazy error I am getting that I am having an incredibly difficult time debugging. I have determined that it is thrown when trying to instantiate the Call object itself, and not when calling enqueue.
This error also doesn't occur on all of my Calls either, just on one in particular. This is what made me think it was something I was personally doing wrong, but I can't find the problem, which leads me to believe there might just be a problem with Call? If I'm crazy let me know.
Thank you in advance!
The error:
Retrofit API:
Where I am calling it:
The text was updated successfully, but these errors were encountered: