[Question] androidx.fragment Version 1.0.0 is out of date.

[YonahaShota]

[REQUIRED] Please fill in the following fields:

• Unity editor version: 2020.3.38f1
• Firebase Unity SDK version: 11.3.0
• Source you installed the SDK: FirebaseMessaging.unitypackage
• Problematic Firebase Component:
• Other Firebase Components in use:
• Additional SDKs you are using:
• Platform you are using the Unity editor on: Mac
• Platform you are targeting: Android
• Scripting Runtime: IL2CPP
• Pre-built SDK from the website or open-source from this repo: website

[REQUIRED] Please describe the question here:

When uploading the AppBundle that uses FCM to Google Play Console, the following warning was displayed:

'The developer of androidx.fragment:fragment (androidx.fragment:fragment) has reported version 1.0.0 as outdated. Consider upgrading to one of the following versions before publishing a new release: 1.1.0+.'

After contacting Firebase Support, they responded that the latest varsion (currently 1.6.0) is available, so we are considering taking action to add this to the mainTemplate.gradle of the Unity project.

Regarding the warning about the androidx.fragment version, do you have any plans to address this in Firebase SDK, and if so, when can it be expected to be provided?

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[paulinon]

Hi @YonahaShota,

Thanks for bringing this to our attention. The cause of this version may lie within the External Dependency Manager for Unity (EDM4U) rather than the Firebase SDK. That said, I've relayed this to the team. I'm unable to provide a timeline as of writing, but you may refer to this thread for updates.

In the meantine, you made add the following lines of code in your Dependencies.xml file to override the older version:

<dependencies>
<androidPackages>
<androidPackage spec="androidx.fragment:fragment:1.1.0" />
</androidPackages>
</dependencies>

[a-maurice]

Hi all,

Investigating this further, the problem is that a handful of our dependencies, like Play Services (and the Firebase Android SDK) are currently set to use that version. They are working on updating them, but not sure when that will be available.

In the meantime, the suggestion above, adding that to the dependencies files (or if you are using a custom gradle file, you can likely do a similar change in that) is the best course of action if you want to get rid of the warning.

[Seanm07]

Could anyone confirm if the dependencies have been updated yet?

We're still using the manual dependency override from above in all our projects as a workaround and as this issue is 2 years old now was wondering if this is still needed or has it since been fixed?