-
Notifications
You must be signed in to change notification settings - Fork 19
FAQ
- The Firebase dependencies are outdated in the Emarsys SDK. When will you release a new version with up-to-date dependencies?
- The default EmarsysMessagingService that ships with the Emarsys SDK does not suite our requirements, we need extra features. How can these features be included in the service?
- I get a 'Could not find firebase-core' error in gradle when trying to integrate the SDK.
- Push messages don't arrive to the device
- Missing Push tokens
- Missing messageOpen events
The Firebase dependencies are outdated in the Emarsys SDK. When will you release a new version with up-to-date dependencies?
We are trying our best to keep our dependencies up-to-date by periodically releasing new SDK versions with updated dependency versions.
If it is urgent and you cannot wait till the new release, you can manually exclude the transitive dependencies in your module level gradle file and add the Firebase dependencies manually.
You should replace the + signs with the most recent concrete versions.
dependencies {
implementation('com.emarsys:emarsys-sdk:+', {
exclude group: 'com.google.firebase', module: 'firebase-core'
exclude group: 'com.google.firebase', module: 'firebase-messaging'
})
implementation 'com.google.firebase:firebase-core:+'
implementation 'com.google.firebase:firebase-messaging:+'
}
The default EmarsysMessagingService
that ships with the Emarsys SDK does not suite our requirements, we need extra features. How can these features be included in the service?
The main purpose of the default FCM services in the SDK is to provide an implementation that works for you out of the box when integrating the SDK. We try to keep the services generic so that they suite the default use cases of our customers. If you have special requirements, we suggest you to implement your own Firebase services based on our default implementation. When implementing your own FCM service, make sure to handle messageOpens correctly.
This is not a Emarsys, but a Firebase issue, consult the Firebase documentation to solve the problem.
Did you download google-services.json
? If not please follow the Firebase documentation to setup your app with Firebase first.
Make sure the connection to Firebase is not limited by company firewall rules.
Make sure you see push tokens in your SDK Logs inside Mobile Engage UI
Make sure you registered our EmarsysMessagingService
in your AndroidManifest.xml
.
Make sure you registered our EmarsysMessagingService
in your AndroidManifest.xml
.