When I press Command + S, hot reload is not working

[khusantoy]

When I press Command + S, hot reload is not working. But when I press the hot reload button in the top bar, it works

screen-recording-2026-04-13-at-163642_xQwk7Dwl.mp4

[helin24]

Can you post more information, like the output of flutter doctor -v? Is this reproducing on all projects or in a specific one?

[khusantoy]

[✓] Flutter (Channel stable, 3.41.6, on macOS 26.4.1 25E253 darwin-arm64, locale en-UZ) [527ms]
• Flutter version 3.41.6 on channel stable at /Users/xusanboy/develop/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision db50e20168 (3 weeks ago), 2026-03-25 16:21:00 -0700
• Engine revision 425cfb54d0
• Dart version 3.11.4
• DevTools version 2.54.2
• Feature flags: enable-web, enable-linux-desktop, enable-macos-desktop, enable-windows-desktop, enable-android, enable-ios, cli-animations, enable-native-assets,
omit-legacy-version-file, enable-lldb-debugging, enable-uiscene-migration

[✓] Android toolchain - develop for Android devices (Android SDK version 36.1.0) [3.1s]
• Android SDK at /Users/xusanboy/Library/Android/sdk
• Emulator version 36.5.10.0 (build_id 15081367) (CL:N/A)
• Platform android-36.1, build-tools 36.1.0
• ANDROID_HOME = /Users/xusanboy/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
This is the JDK bundled with the latest Android Studio installation on this machine.
To manually set the JDK path, use: flutter config --jdk-dir="path/to/jdk".
• Java version OpenJDK Runtime Environment (build 21.0.10+-117844308-b1163.108)
• All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 26.4) [1,361ms]
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 17E192
• CocoaPods version 1.16.2

[✓] Chrome - develop for the web [4ms]
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Connected device (3 available) [6.3s]
• iPhone 13 mini (mobile) • 771E394B-6E0D-4F9A-A1A4-82DADCDB8B4C • ios • com.apple.CoreSimulator.SimRuntime.iOS-26-4 (simulator)
• macOS (desktop) • macos • darwin-arm64 • macOS 26.4.1 25E253 darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome 147.0.7727.56
! Error: Browsing on the local area network for Zoirbek’s iPhone. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this
Mac.
The device must be opted into Developer Mode to connect wirelessly. (code -27)
! Error: Browsing on the local area network for I.S.K.A.N.D.A.R. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this
Mac.
The device must be opted into Developer Mode to connect wirelessly. (code -27)

[✓] Network resources [781ms]
• All expected network resources are available.

• No issues found!

[khusantoy]

I only encountered this in this project

[helin24]

I only encountered this in this project

Are you able to share the project? Or reproduce in another small project?

[khusantoy]

I can't share the project. I haven't encountered this issue in other projects.

[helin24]

Hmmm... any related logs in dash.log? (from Help > Show log in finder) Otherwise I don't see any differences in your project or environment that would lead to this problem, so it's hard to know where to start fixing this. A reproduction in another project or finding something that causes hot reload on Cmd+S to work in the failing one would help us here.

[khusantoy]

I’ll try to check the logs and reproduce this issue in another project

[khusantoy]

This is idea.log file

idea.log @helin24

[khusantoy]

try_flutter.zip

This is the project which is cmd+s is not working @helin24

Bonus: First I removed random line from the code. I made linter error after I put the code back. Then shortcut didn't work

[khusantoy]

@helin24 I have an additional question that’s been on my mind: is it normal that hot reload runs every time I press CMD+S after each code change, or is it designed to work that way? But cmd+\ makes hot reload without code change. If this not related this issue should I have to create new one?