Why are we using different Nonull annotations in ConfigUpdateListener?

[LeoAndo]

[REQUIRED] Step 2: Describe your environment

• Android Studio version: Android Studio Koala | 2024.1.1 Patch 1 Build #AI-241.18034.62.2411.12071903, built on July 11, 2024

• Firebase Component: firebase remote config

• Component version: 22.0.0 BoM(33.1.1)

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

There are no problems in the application, but why are different Nonnull annotations used in com/google/firebase/remoteconfig/ConfigUpdateListener.java?

Shouldn't they be unified to one of them? (androidx.annotation.NonNull or javax.annotation.Nonnull)

Android Studio will suggest androidx.annotation.NonNull.

Relevant Code:

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[lehcar09]

Hi @LeoAndo, thanks you for reaching out and raising this question. This could be due to historical reasons or inconsistencies in the codebase. Let me check this with our engineers. I’ll get back to you once I hear from them. Thanks!