What the developer wrote
Authored by Keeqler
Fix mobile screen transitions
What changed, and why it matters
This commit changes how screen transitions (animations) work in a mobile/desktop wallet app. It disables animated transitions on desktop entirely and keeps them only between navigation-bar screens on mobile. There is no security-relevant change visible in the diff.
No security action needed. Treat as a normal UI/UX fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch modifies lib/main.dart’s _onGenerateRoute so that _NoTransitionPageRoute is returned when isDesktop is true OR when the route is in _noTransitionRoutes. Previously it only checked _noTransitionRoutes. This is a UI/UX polish change for route transitions and does not touch cryptography, authentication, storage, networking, or permissions.
Changed components
lib/main.dart route generation logicInspect captured patch +3 / −1
### lib/main.dart
@@ -190,7 +190,9 @@ class _AppRootState extends State<_AppRoot> with WidgetsBindingObserver {
Route<dynamic>? _onGenerateRoute(RouteSettings settings) {
final builder = _routes[settings.name];
if (builder == null) return null;
- if (_noTransitionRoutes.contains(settings.name)) {
+ // Desktop: no transition anywhere. Mobile: only between the nav-bar screens;
+ // every other push/pop keeps its normal animation.
+ if (isDesktop || _noTransitionRoutes.contains(settings.name)) {
return _NoTransitionPageRoute(builder: builder, settings: settings);
}
return MaterialPageRoute(builder: builder, settings: settings);Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.