Backendless Warning in Android using Proguard.

Android
1

Hello,

I am using Proguard in Android and I have added below rules for Backendless-
-dontwarn com.backendless.**
-dontwarn weborb.**
-keep class weborb.** {;}
-keep class com.backendless.** {;}

But while creating release apk, I am getting below warning-

Warning:com.repairservice.ActivationActivity$2$1: can’t find enclosing method ‘void handleResponse(com.backendless.messaging.MessageStatus)’ in program class com.ketan.repairservice.ActivationActivity$2

Any idea on whats that error means?

2

Hello,

What version of Backendless SDK do you use in the project?

Regards,
Mark

3

I’m using Backendless v4

4

I have defined AsyncCallback instance in my class, if I do comment it then release apk is built.

5

Is there a method in the class you are getting the warning about?

6

Nope

7

I’m having below code in my class-
AsyncCallback<List<ServiceOrder>> serviceOrderCallback = new AsyncCallback<List<ServiceOrder>>() {
@Override
public void handleResponse(List<ServiceOrder> response) {

}

@Override
public void handleFault(BackendlessFault fault) {

}

};
if I do comment above code then the release apk is built successfully.

8

I do not understand where a reference to “void handleResponse(com.backendless.messaging.MessageStatus)” is coming from. Why does it refer to a callback with MessageStatus? Do you have any ideas?

9

I don’t know Mark, Do u need any other info? Have u tried defining AsyncCallback instance in class and creating a release build with proguard-rules?

10

I do not believe the problem is with Backendless. Does it compile if you remove the Proguard settings?

11

I am able to run my app in debug mode but while creating release build it give the warning -

Warning:com.ketan.repairservice.ActivationActivity$2$1: can’t find enclosing method ‘void handleResponse(com.backendless.messaging.MessageStatus)’ in program class com.ketan.repairservice.ActivationActivity$2

12

Try excluding from obfuscation the class(es) which generate the warning.

13

I’m not sure what the problem is but I managed it by specifying the AsyncCallback instance in method find(query, asyncCallback) itself.