I have a Flutter app that already schedules and displays local notifications on Android, but tapping the notification (or any defined action button) is not firing the callback inside the app. The notification itself shows up fine; the problem is strictly with the action/intent side of things. Scope of work You’ll dive into the existing codebase, trace how the current local-notification flow is wired, and correct whatever is blocking the on-select / on-action handlers. The project targets Android only; no iOS work is required. I’m using the standard flutter_local_notifications package together with Android Studio for builds, so familiarity with that plugin, intents, and background isolates in Dart will help. Deliverables • Functional local notifications whose tap or action buttons reliably trigger the assigned Dart callback while the app is in foreground, background, or terminated state. • Clear notes (inline comments or a short markdown file) describing the changes so I can maintain the fix in future releases. • A quick walkthrough of the testing steps you used, preferably via a screen recording or concise text, so I can replicate the results with ADB or on-device. Acceptance criteria 1. Running `flutter run --release` on my end produces an APK where the notification tap opens the designated screen or executes the callback every time. 2. No new warning or error logs related to notifications appear in Logcat. 3. Existing notification appearance, scheduling, and sound behaviour remain unchanged. That’s the full task. Once the callbacks fire correctly, the job is done.