LogicalOperator Parse errors flood our logs

[sirivanleo]

We have had this issue for months now. In the past while debugging an issue with the sdk I attached our logger to the ErrorMetrics Listener so we can see apptentive errors in our logging backend but we see many superfluous errors.

apptentive-android/apptentive/src/main/java/com/apptentive/android/sdk/module/engagement/logic/LogicalOperator.java

Line 27 in a3e4b9f

logException(e);

Mainly the following
Apptentive Error Thread java.lang.IllegalArgumentException: No enum constant com.apptentive.android.sdk.module.engagement.logic.LogicalOperator.code_point/local#app#engage_event/invokes/total

When tracing the code I see that it would be more beneficial to treat this like warning or not logException at all. This line point is expected once the client has parsed the server engagement logic and reached the most inner clause. I think I'm going to either filter this error or disable the logger altogether as it hasn't really brought much benefit to our code. I would also like some feedback regarding using the error listener, should I not be using it?

[CaseyApptentive]

Hi @sirivanleo!

Thanks for letting us know. This likely means that the manifest contains invalid values, and we'd like to take a deeper look.

Can you email me at [email protected] and let me know the name of the specific app you're working on? Once we have that we can dive in.

[sirivanleo]

Done

[CaseyApptentive]

Thank you. I saw your message and will coordinate with my colleague to get back to you asap.