ServiceDispatch | Automatically log emergency services like police and fire

Try change your dependencies in Facebook Dependencies from

This is a known issue and needs changes on the underlying androidx.browser library. The changes are in 1.4.0-rc1, which should go stable in the next weeks. Another change was required in android-browser-helper and once the change to androidx.browser is out, we'll release an update that will work well with targetSdk 31.

You could use the release-candidate version of android.browser and build your own android-browser-helper, but I'd recommend waiting for the production versions to upgrade to target SDK 31.

You must ensure that the following line will be there in your proguard rules. This will tell your application to ensure that the SpongyCastle encryption libraries can be used.

The first leaktrace shows that ShopFragment sets up a BillingClientStateListener in ShopFragment$setupBillingClient, probably by calling BillingClient#startConnection(). The BillingClientStateListener implementation in an anonymous class and has a reference to an instance of its outer class, ShopFragment. Looking at the Javadoc, it seems that you need to call BillingClient#endConnection() once you're done, i.e. when the fragment is destroyed. The billing documentation does not mention this at all so you might want to file a documentation bug.

The second leaktrace shows that the ViewDataBinding.LiveDataListener associated with the destroyed InventoryFragment is held in memory by ViewDataBinding.sReferenceQueue (see the sources here. The fact that ViewDataBinding$WeakListener is in the queue means that ViewDataBinding.WeakListener is not strongly reachable. ViewDataBinding. processReferenceQueue() is in charge of doing that, so it looks like it hasn't been called in a while. It's hard to say for sure without a heap dump, but this looks like a DataBinding library bug and you should file a ticket.

Do you by any change use PackageManager object? I've had the same issue and it turned out there's a weird bug using this object, if you are using it too much it may "die" and cause your app to also receive a "dead object exception". If not, I'd recommend you try to comment out lines that you might have added prior to this exception and try to figure out what is causing that issue. Also, if it's possible to provide us with code, that would help

Exact same issue with these versions. And yes they were functional before this "@react-native-firebase/app": "^6.7.1", "@react-native-firebase/messaging": "^6.7.1",

Issue Solved:

1. Go to react-native-push-notification/build.gradle
2. Change def firebaseVersion = safeExtGet('firebaseVersion', '+') to def firebaseVersion = safeExtGet('firebaseVersion', '20.2.1')

It was picking us the version 20.2.2 which is not stable and was causing all kind of weird issues.

You should destroy the speech recognizer when stopping the service.

The error is caused by invoking platform channels before calling runApp.

Since the last stable Flutter version, doing so requires you to call WidgetsFlutterBinding.ensureInitialized(); beforehand, which ensures that Flutter is bound to the platform it's running on before you actually try to communicate to it using platform channels.

Calling this before any other code that makes use of platform channels should fix your issue - I guess you could have it as the very first line of code in your main() function:

You can add like this: