-
Notifications
You must be signed in to change notification settings - Fork 578
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
transformClassesWithFirebasePerformancePlugin gradle task results in ArrayIndexOutOfBoundsException #1556
Comments
I found a few problems with this issue:
|
Initial UnderstandingFrom the stack trace it looks like there was a problem when ASM (the library we use for bytecode instrumentation) trying to instrument the below class file:
MultiPartFormDataContent is an API for Ktor which is an asynchronous Web framework for Kotlin. Next StepsI would have to reproduce the problem at my end to debug this further. @eightx2 If you have a sample project where issue is always reproducible can you share that? |
After debugging further I figured out the factors that cause the issue are:
I have created a ticket with ASM Team for this - https://gitlab.ow2.org/asm/asm/issues/317904 @eightx2 Meanwhile please be assure that if the build is succeeding (which should be the case) and you are only getting this exception for Impact: If that class uses @AddTrace annotation we will not process it and if there is any Network call being made in that class we won't automatically capture it. Regarding the exception, we log it as an error because it shouldn't be overlooked and may sometimes require an attention (like a fix from |
We have reverted back to the ASM Team with the information they requested for further debugging on their side. Will keep this thread updated. |
ASM Team have a PR ready to fix this. Once they rollout a new version (with this fix integrated), we'll upgrade our ASM dependency to that version and rollout a new version of Firebase Performance Plugin which should fix this issue. Thanks for your patience :) |
Hi! |
Hi @jsilva05 , Thanks for reaching out~ Can you please attach the full stack trace and all the gradle configurations (i.e all your If you have a sample app on which you are able to reproduce this issue always ( |
Hi @ramanpreetSinghKhinda ! |
As per the recent comment by the ASM Team, the fix from their side will go in Once this is fixed from ASM side, we'll incorporate the changes in Fireperf plugin. Note: We'll test the changes with the beta version of ASM (to confirm if this issue is fixed) however, we might wait for the stable version to come in before actually shipping the changes in Fireperf. |
ASM have released v9.0 beta. We'll test our plugin against it and update the thread. |
Hi @gosr Just to keep the thread active, letting you know that I am still on it. Because of other priorities I am not yet able to spend time on validating this. But I'll keep posted on updates as we have them. |
Hi @gosr, The fix have been merged to master. It will be available in the upcoming release of Closing the thread for now but please don't hesitate to reopen if the issue persists with the new release as well. Thanks :) |
Hi @ramanpreetSinghKhinda Do you mean this issue would be fixed in |
Hi @anticafe The issue should be fixed in perf-plugin v1.3.2. |
Steps to reproduce:
Run the gradle task 'transformClassesWithFirebasePerformancePluginForYourBuildFlavor'.
Output:
The text was updated successfully, but these errors were encountered: