Physical back Button or slide doesnt go to previous page

Today i experienced a strange problem in my Flutter application. After installing the Firebase messaging and the Flutter local notifications packages, and made the adjustments on iOS and Android, i saw that the back button on emulator and on physical device and the slide back, didnt go to previous page, instead they were pushing the app to the background.

I tried almost everything i found on the web, like change the flutter channel or run some flutter clean etc. Nothing worked.

The FCM works correct

This is some code of my main.dart:

 Future<void> main() async {
WidgetsFlutterBinding.ensureInitialized();
await Firebase.initializeApp();
await FirebaseApi().initNotifications();
SystemChrome.setSystemUIOverlayStyle(SystemUiOverlayStyle.dark);
prefs = await SharedPreferences.getInstance();
Constants.pref = await SharedPreferences.getInstance();
runApp(MyApp());
}

And this is my FirebaseApi file:

Future<void> _handleBackgroundNotificationMessage(RemoteMessage message) async {
if (message.notification != null) return;
await   App.materialKey.currentState?.pushNamed('/appoinments');
}
class FirebaseApi {
final _firebaseMessaging = FirebaseMessaging.instance;
final _localNotifications = FlutterLocalNotificationsPlugin();
final _androidChannel = AndroidNotificationChannel(
'high_importance_channel',
'High Importance Notifications',
description: 'This channel is used for important   Notifications',
importance: Importance.high,
);
Future<void> initPushNotifications() async {
await FirebaseMessaging.instance
.setForegroundNotificationPresentationOptions(
alert: true,
sound: true,
badge: true,
);
FirebaseMessaging.instance.getInitialMessage().then(_handleMessage);
FirebaseMessaging.onMessageOpenedApp.listen(_handleMessage);
FirebaseMessaging.onBackgroundMessage(_handleBackgroundNotificationMessage);
FirebaseMessaging.onMessage.listen((RemoteMessage message) {
// final notification = message.notification;
RemoteNotification? notification = message.notification;
AndroidNotification? android = message.notification?.android;
// if (notification == null) return;
if (notification != null && android != null) {
_localNotifications.show(
notification.hashCode,
notification.title,
notification.body,
NotificationDetails(
android: AndroidNotificationDetails(
_androidChannel.id,
_androidChannel.name,
channelDescription: _androidChannel.description,
icon: '@drawable/ic_launcher',
// other properties...
),
),
payload: jsonEncode(message.toMap()),
);
}
});
}
void _handleMessage(RemoteMessage? message) {
if (message == null) return;
App.materialKey.currentState?.pushNamed('/appoinments');
}
onClickNotification(payload) async {
Map<String, dynamic> dat = json.decode(payload);
// if (dat['type'] == 'appointment') {
//   print('TRIED TO CALL UPDATE');
// }
App.materialKey.currentState?.pushNamed('/appoinments');
}
Future initLocalNotifications() async {
const iOS = DarwinInitializationSettings();
const android = AndroidInitializationSettings('@drawable/ic_launcher');
const settings = InitializationSettings(android: android, iOS: iOS);
await _localNotifications.initialize(
settings,
onDidReceiveNotificationResponse:
(NotificationResponse notificationResponse) {
final String? payload = notificationResponse.payload;
final message = RemoteMessage.fromMap(jsonDecode(payload!));
_handleMessage(message);
// onNotifications.add(payload as String?);
},
);
final platform = _localNotifications.resolvePlatformSpecificImplementation<
AndroidFlutterLocalNotificationsPlugin>();
await platform?.createNotificationChannel(_androidChannel);
// onNotifications.stream.listen(onClickNotification);
}
Future initNotifications() async {
NotificationSettings settings = await _firebaseMessaging.requestPermission(
alert: true,
badge: true,
sound: true,
);
final fcmToken = await FirebaseMessaging.instance.getToken();
print(fcmToken);
print('User granted permission: ${settings.authorizationStatus}');
initPushNotifications();
initLocalNotifications();
}
}

I found a temporary solution. The problem was with Android 13 gesture and the communication between Flutter framework, on which of them is gonna handle first the gestures. By default is ok but I added FlutterFragmentActivity in the MainActiviry.kt file for the FCM integration. FlutterFragmentActivity and enableOnBackInvokedCallback:true (in AndroidManifest) aren't working well together. So I added false as a temporary solution and it works.