> ## Documentation Index
> Fetch the complete documentation index at: https://moengage-sdk-docs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting and FAQs - Flutter

# Android - Why are notifications not working in the background or killed state?

Ensure that you are initializing MoEngage in the Application class and in the main thread.

Sample code link - [GitHub](https://github.com/moengage/Flutter-SDK/blob/dc4cac19fe9fc04ca4d187265544a6a1e9c04c9e/example/android/app/src/main/java/com/moengage/sampleapp/SampleApplication.kt#L37)

# Android - Why are callbacks not working in the background or killed state?

MoEngage callbacks must be registered in your application's root/App widget, and after setting them up, you must call the MoEngage Plugin's initialize () method. Read more about [it here](/developer-guide/flutter-sdk/push/basic/push-callback).

Sample code link - [GitHub](https://github.com/moengage/Flutter-SDK/blob/master/example/lib/main.dart)

# Android - Why are inapp/nudge deep links not working?

Unilke the push notification handling, MoEngage SDK doesn't handle inapp redirections by default (except for rich landing page), please refer to the [documentation here](/developer-guide/flutter-sdk/in-app-messages/inapp-nativ). You must implement inapp click callback methods in your root/app widget and call moengage plugin initialise() method after registering for callbacks. In these callbacks, you must handle the redirection for deeplink or screen-based redirection. Callback documentation [is given here](/developer-guide/flutter-sdk/in-app-messages/inapp-nativ).

# Android - Why are inapp callbacks not working?

Refer to [this documentation](/developer-guide/flutter-sdk/in-app-messages/inapp-nativ) to set up in-app callbacks. Additionally, you must register the callbacks in your application's root/App widget, and after setting them up, you must call the MoEngage Plugin's initialize () method.