Closed avalanchas closed 2 years ago
Google removed firebase-iid around v21 of FCM. You can probably just add firebase-iid
package to your dependencies to resolve the issue.
This is an Accengage SDK issue not Airship SDK so it wont be in our migration guides. I will forward this on to the team though
Hi, that sounds reasonable and I will test in the coming days, but I wonder why the upgrade in the Airship SDK leads to this behaviour then. Maybe this dependency was transitively declared in the older Airship versions and is now missing, because it was fulfilled through previous Airship versions and is now not fulfilled anymore?
I am very hesitant to declare firebase-iid
myself as it has been deprecated since late 2020
Edit: firebase-installations
, the successor to firebase-iid
also might provide this class. Still seeing the crash now, I will do more testing.
As far as I can tell only adding firebase-iid
fixes the crash. Can you please comment on why this is the case, even in an app where - as mentioned above - nothing but the Airship SDK update changes?
The Airship SDK is keeping up with latest version of FCM, so when you use a new version of Airship it will force a newer version of FCM as a transitive dependency.
Accengage SDK is depending on an older version with firebase-iid, it needs to be updated but adding it is a quick workaround for now.
Preliminary Info
What Airship dependencies are you using?
Firebase dependencies (probably relevant for this issue):
Crash occurs in Airship version 15.0.0, 15.1.0 and 16.0.0 Crash does not occur in Airship version 14.0.0
What are the versions of any relevant development tools you are using?
System Info
Gradle
This crash is reproducible in debug and release builds, so it cannot be a Proguard problem
Report
What unexpected behavior are you seeing?
App crashes soon after start, because it tries to access the
FirebaseInstanceId
class and can't find it. This seems to be some kind of weird interaction between the Accengage A4S SDK and the firebase SDK. Since the behaviour appears only in 15.x upwards, I suspect this has something to do with the changes to the Firebase sender ID mentioned in the changelog for that versionI have read the Migration Guide but it does not address this issue and I do not use the
FEATURE_CONTACTS
What is the expected behavior?
No crashes, as in version 14.x.x
What are the steps to reproduce the unexpected behavior?
Do you have logging for the issue?