Android signed APK failure

BLE Beacons
1

I built a signed apk of my app, but the app don’t run.

uncaughtException found: java.lang.RuntimeException: Unable to bind to service com.estimote.sdk.service.BeaconService@260b2309 with Intent { cmp=zzzzzzzzzz/com.estimote.sdk.service.BeaconService }: java.lang.IllegalArgumentException: InternalEstimoteApi.getBeacons: Last parameter must be of type Callback<X> or Callback<? super X>.

at android.app.ActivityThread.handleBindService(ActivityThread.java:3035)
at android.app.ActivityThread.access$1900(ActivityThread.java:178)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1558)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:194)
at android.app.ActivityThread.main(ActivityThread.java:5637)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:959)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:754)
Caused by: java.lang.IllegalArgumentException: InternalEstimoteApi.getBeacons: Last parameter must be of type Callback<X> or Callback<? super X>.
at com.estimote.sdk.repackaged.retrofit_v1_9_0.retrofit.RestMethodInfo.methodError(Unknown Source)
at com.estimote.sdk.repackaged.retrofit_v1_9_0.retrofit.RestMethodInfo.parseResponseType(Unknown Source)
at com.estimote.sdk.repackaged.retrofit_v1_9_0.retrofit.RestMethodInfo.<init>(Unknown Source)
at com.estimote.sdk.repackaged.retrofit_v1_9_0.retrofit.RestAdapter.getMethodInfo(Unknown Source)
at com.estimote.sdk.repackaged.retrofit_v1_9_0.retrofit.RestAdapter$RestHandler.invoke(Unknown Source)
at java.lang.reflect.Proxy.invoke(Proxy.java:397)
at $Proxy1.getBeacons(Unknown Source)
at com.estimote.sdk.cloud.internal.InternalEstimoteCloud.getBeacons(Unknown Source)
at com.estimote.sdk.cloud.internal.AnalyticsManager.fetchOwnedDevicesIfEnabled(Unknown Source)
at com.estimote.sdk.service.BeaconService.onBind(Unknown Source)
at android.app.ActivityThread.handleBindService(ActivityThread.java:3022)
at android.app.ActivityThread.access$1900(ActivityThread.java:178) 
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1558) 
at android.os.Handler.dispatchMessage(Handler.java:111) 
at android.os.Looper.loop(Looper.java:194) 
at android.app.ActivityThread.main(ActivityThread.java:5637) 
at java.lang.reflect.Method.invoke(Native Method) 
at java.lang.reflect.Method.invoke(Method.java:372) 
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:959) 
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:754)

As debug version installed via cable, it runs very well.
proguard-rules are:

-keep class com.estimote.sdk.** { *; }
-keep interface com.estimote.sdk.** { *; }
-dontwarn com.estimote.sdk.**

Please help me to solve this problem

2

I found a temporary workaround.
I just removed two lines:

EstimoteSDK.initialize(App.getAppContext(), "XXXXXX", "XXXXXXX");
EstimoteCloud estimoteCloud = EstimoteCloud.getInstance();
3

Linking to the appropriate bug report on our GitHub, for completeness (: