[BUG] Failed to upload blob: Wrong number of arguments; expected 1, got 0 about azure-sdk-for-java HOT 6 CLOSED

@ibrahimrabab @ibrandes @seanmcc-msft

from azure-sdk-for-java.

Thank you for your feedback. Tagging and routing to the team member best able to assist.

from azure-sdk-for-java.

Thanks for filing this issue @peter6053.

Unassigning @ibrahimrabab as this is an issue with azure-core.

Looks like this is a case where a few locations within azure-core calls into the incorrect APIs for reflectively creating objects and calling static methods. Using invokeWithArguments rather than invokeStatic and the java.lang.invoke implementations worked as they need to handle Object target, Object... args differently than the java.lang.reflect implementations.

from azure-sdk-for-java.

from azure-sdk-for-java.

Hi @peter6053, the issue was with how we were performing reflective calls when in an environment that doesn't have the java.lang.invoke package, a common case for Android, and when we fall back to using java.lang.reflect. There was an issue where the arguments used to reflectively invoke constructors and static methods were being consumed incorrectly, leading to the exception you are seeing.

The fix will be available sometime in early July when we release our libraries again.

from azure-sdk-for-java.

from azure-sdk-for-java.