@@ -432,16 +432,16 @@ and should not be used. A fix for these issues was released on
432432 be aware of the following:
433433
434434 - The [ messaging] registration tokens of installed instances of your apps might change once after
435- updating dependencies to their latest versions. To learn if your apps are affected, review the
436- <a href="//github.com/firebase/firebase-android-sdk/blob/main/firebase-installations/FCM_TOKENS_CHANGE.md"
437- class="external">[firebase_installations] documentation</a>. Also, make sure to
438- <a href="/docs/cloud-messaging/android/client#monitor-token-generation">monitor [messaging]
439- registration token generation</a> using the <code>#onNewToken</code> implementation.
435+ updating dependencies to their latest versions. To learn if your apps are affected, review the
436+ <a href="//github.com/firebase/firebase-android-sdk/blob/main/firebase-installations/FCM_TOKENS_CHANGE.md"
437+ class="external">[ firebase_installations] documentation</a >. Also, make sure to
438+ <a href =" /docs/cloud-messaging/android/client#monitor-token-generation " >monitor [ messaging]
439+ registration token generation</a > using the <code >#onNewToken</code > implementation.
440440
441441 - Apps that use the Firebase auto-initialization process and the Gradle plugin to convert
442- `google-services.json` into resources are unaffected. However, apps that create their own
443- `FirebaseOptions` instances must provide a valid API key, Firebase project ID, and application
444- ID.
442+ ` google-services.json ` into resources are unaffected. However, apps that create their own
443+ ` FirebaseOptions ` instances must provide a valid API key, Firebase project ID, and application
444+ ID.
445445
446446# 20.1.0
447447
0 commit comments