FcmTokenListenerService & InAppNotificationActivity in AndroidManifest.xml shows linter error when migrated to AndroidX

[mochadwi]

My setup:

CleverTap: 3.7.2
Firebase Messaging: 19.0.0

please mention me if you need more setup configuration or provide more error/output logs

Linter error:
Registered class is not instantiatable correctly

My Approach:

• This Didn't find class "com.clevertap.android.sdk.FcmTokenListenerService" crash on Coolpad devices #43 has workaround for the issue with FcmTokenListenerService as stated in this docs
• I've also stated my workaround when migrating using AndroidX here Migrate to androidx #38 by manually jetified the clevertap-3.7.2.aar and add the .aar to the our codebase locally with flatDirs
• The above issue won't happened when using flatDirs approach, but I've recently remove it and using jetifier default approach, seems doesn't works: Feature Request: Migrate to androidx facebook/facebook-android-sdk#591 (comment)
• I don't wanna silence my linter error as warning (this is not a fix) because I need InAppNotificationActivity to function correctly

[suggested]
An open function to extends the InAppNotificationActivity so we can use correct androidx imports & place it in our AndroidManifest.xml

or any workaround/alternative currently to solve this issue?

P.S: But if the milestone for androidx migration still far away, maybe I just have to add locally the clevertap then T_T

[darshanclevertap]

There are two separate issues here -

1. The InAppNotificationActivity is now a part of the CleverTap SDK's AndroidManifest.xml and you don't need to add it in your AndroidManifest.xml file. That should solve the lint issue.

2. As for the FCMMessageListener class, you can follow Didn't find class "com.clevertap.android.sdk.FcmTokenListenerService" crash on Coolpad devices #43 and easily avoid any issues.

You don't need to add the AAR file manually if you follow the above 2 steps.

[mochadwi]

Now that's great, so it is safe to remove the InAppNotification activity? Did you guys already mentioned this feature in official docs somewhere (the others might not found it too)

I assume, because AppsFlyer SDK manifest will be merged to our apps manifest (that is safe to remove InAppNotification activity from apps manifest) @darshanclevertap

[darshanclevertap]

Yes, @mochadwi CleverTap's manifest gets merged with your app's manifest file at compile time. So you don't need to add it in your manifest separately. I'll check our official documentation as well, and update it if its not. Thanks!