You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the example shown above, the service com.localytics.android.FirebaseService will only be enabled in the manifest if ll_fcm_push_services_enabled is set to true.
However, this doesn't seem to be the case on the Xamarin version of the library, as the values set in the configuration don't seem to be used in the manifest at all.
The text was updated successfully, but these errors were encountered:
ernestoyaquello
changed the title
Potential issue:
Potential issue: Services not getting disabled when they aren't needed
Feb 4, 2021
ernestoyaquello
changed the title
Potential issue: Services not getting disabled when they aren't needed
Unneeded Firebase services and receivers are not being disabled
Feb 4, 2021
I've implemented a possible approach to this by switching from using the native library JAR to AAR which then supports manifest merging tomcurran#1 I did it using v6.2.0 of the native library so PR #60 needs to go through first before creating a PR for it
In the native version of the library, it seems like some Firebase services and receivers get disabled depending on the user configuration:
In the example shown above, the service
com.localytics.android.FirebaseService
will only be enabled in the manifest ifll_fcm_push_services_enabled
is set totrue
.However, this doesn't seem to be the case on the Xamarin version of the library, as the values set in the configuration don't seem to be used in the manifest at all.
The text was updated successfully, but these errors were encountered: