· When i want turn back only one page for example from album to artist, after using navigation gesture "back" whole app closes. It appear after 2.70 update. Notifications is enabled. video showing issue: https://streamable.com/8g3pw7
Tell us about your home network
· router: ZTE MC888 Pro + mercusys 105g switch, server and client connected via RJ45 cable.
We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.
You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.
Thanks for confirming, and sorry to hear it’s still happening after the latest update.
QA is still actively working on reproducing this on our end. We’ll follow up here as soon as we have something concrete, whether that’s a fix in progress or questions that’ll help narrow it down further. Appreciate you sticking with us on this one.
Regarding the back gesture closing the app on Android in 2.70: since the migration to .NET 10, it looks like the app is falling victim to the deprecation of Activity.OnBackPressed() in recent Android versions (Predictive Back gestures). The gesture falls through to the OS, which minimizes the app instead of navigating down the inner page stack.
You might need to fully implement OnBackPressedDispatcher with OnBackPressedCallback. Also, please check the known .NET MAUI 10 bug (GitHub issue #34379), where HandleOnBackPressed stops firing on child pages. You may need a workaround to ensure the callback stays actively bound to your internal navigation stack when moving away from the MainPage."
Thanks for the update! We haven’t been successful in reproducing this in-house, unfortauntly.
With that, the detail in your last post is genuinely helpful, and it lines up with what we’re seeing on our end. We pulled the Android Remote logs and there’s no crash or exception at the point of closure; the log simply stops mid-activity with no shutdown sequence. That’s consistent with the process being minimized/terminated by the OS rather than the app throwing an error, which fits the Predictive Back / OnBackPressed behavior you described.
The catch is that the managed Roon logs can’t capture the moment itself, by the time the OS acts on the gesture, our logging is already gone. To confirm the cause, we’d like a native Android system log (logcat) captured during a fresh reproduction. If you’re able to grab one:
On the phone, enable Developer Options and turn on USB debugging, then connect it to a computer with ADB installed.
In a terminal, clear the buffer and start capturing to a file:
adb logcat -c
adb logcat > roon_back_gesture.txt
With capture running, open Roon Remote, navigate album → artist, and perform the back gesture that closes the app.
Stop the capture (Ctrl+C) right after it closes, and attach roon_back_gesture.txt here.
That capture should show the activity being minimized/killed at the OS level and let us tie it directly to the back-gesture handling. If getting ADB set up is awkward, let us know and we'll suggest an alternative.
Really appreciate you sticking with us and doing the legwork on this one.
Thank you, that logcat was exactly what we needed, and your read on the cause in your earlier post was on the money.
Here’s what the capture shows. Your phone is on Android 13 (API 33) with gesture navigation, and the log confirms there’s no crash at the point the app closes, the process is never killed, there’s no exception, and nothing in our own logs shows a shutdown. Instead, at the moment you swipe back, Android reports the gesture as “return to home” and hands it to its default handler, which sends the app to the launcher. In other words, the back never reaches Roon’s own page navigation, so instead of going album → artist, the whole app is minimized.
This is enough for us to open a bug and work on a fix for it. I’ll keep this thread updated as it moves through, and I really appreciate your patience and the legwork on the log, it made the difference here.
