Hot reload error
See original GitHub issueI use resources in page:
<ContentPage.Resources>
<Color x:Key="fgColor">#262626</Color>
<Color x:Key="bgColor">White</Color>
<Color x:Key="btnBgColor">Gray</Color>
</ContentPage.Resources>
and hot reload throw error: [1]HotReloadAgent: ERROR: A resource with the key ‘fgColor’ is already present in the ResourceDictionary. [ArgumentException]
Am I doing something wrong or is it a bug? I use 1.4 version for Rider 2020.2
Issue Analytics
- State:
- Created 3 years ago
- Comments:19 (11 by maintainers)
Top Results From Across the Web
hot reload and hot restart not working in flutter
When using the terminal to run flutter run , it won't automatically hot reload and hot restart on save. You need to press...
Read more >Troubleshooting XAML Hot Reload - Visual Studio
Error indicates that the change you're attempting isn't supported by XAML Hot Reload. Stop the debugging session, make the change, and then ...
Read more >Hot reload
Hot reload loads code changes into the VM and re-builds the widget tree, preserving the app state; it doesn't rerun main() or initState()...
Read more >Hot Reload - General Exception any time I save a file.
I have "Hot Reload on File Save" enabled. Anytime I save any file while debugging (razor, cs, etc), I get the following error...
Read more >Error when hot reloading and hot restart. · Issue #22964
Hello, Here is my code that I am trying to run: my code Here is my post on stackoverflow stackoverflow Looks like it...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fixed 😃 @lightway82 plugin v.1.4.4. will be available for downloading/update in Rider in 1-2 days.
Feel free to reopen if the bug still exists once a new version is released