Is it safe to (re-)use an (old) activity context?

[FrankEngler]

MainActivity gets an instance of GoogleMobileAdsConsentManager using its activity context via

googleMobileAdsConsentManager = GoogleMobileAdsConsentManager.getInstance(this)

GoogleMobileAdsConsentManager is a singleton:

companion object {
  @Volatile private var instance: GoogleMobileAdsConsentManager? = null

  fun getInstance(context: Context) =
    instance
      ?: synchronized(this) {
        instance ?: GoogleMobileAdsConsentManager(context).also { instance = it }
      }
}

If for any reason (e.g. configuration change) this or another activity try to get an instance of GoogleMobileAdsConsentManager they will ask for an instance with the actual context but will get an instance for the original activity context - of the now old and dead MainActivity. This might be the cause for #441. But even if it isn't this doesn't seem memory safe at all.

Can UserMessagingPlatform.getConsentInformation() work with an application context?
If so GoogleMobileAdsConsentManager.getInstance() should get an application context instead of an activity context.
If not GoogleMobileAdsConsentManager should not use singleton pattern.