5,381 questions
VS 2022 and Android emulator are not playing well together
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 84%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELS%3C/text%3E%3C/svg%3E)
Lloyd Sheen
1,486
Reputation points
The problem is that after a while I can make simple changes to the XAML or the C# and the changes will not show on the first execution of the new code.
If I run , quit the app and then rerun the changes are shown.
This seems to happen more as I tend to leave VS 2022 running overnight with PC on sleep mode.
To help with this I am closing VS when I am done with it for a while. I also have cleaned the solution and the deployment seems to happen ok for a while. It looks to me as if there is a cache problem. The first execution does not use the new code but the second does. I have not created a new Android emulator as it took me some time to get it working.
The other thing that has changed on my PC is that I have given up on trying to get Hot Reload to work. Changing that setting is the only thing that I can think of that I have changed in the development environment in the last few months.
Developer technologies | .NET | Xamarin
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 40%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYL%3C/text%3E%3C/svg%3E)
Yonglun Liu (Shanghai Wicresoft Co,.Ltd.) 50,126 Reputation points Microsoft External Staff2022-08-02T05:24:22.95+00:00 You could try to delete
/binand/objfolders in your project.If it doesn't work, could you please provide more detailed information about how to reproduce this issue, and how did you change the development environment ? It would be helpful for us to find the real reason.
-
Lloyd Sheen 1,486 Reputation points
2022-08-02T16:18:56.743+00:00 The unfortunate answer to your reply is that testing is the answer. There is nothing I have done that is new or weird. I simply in testing change something in the XAML and it takes two (sometimes and that is the key) to have the problem.
The one consistent thing is that an execution that has the old code will be followed by an execution with the new code even though I did not change anything in between.
As I have conjectured it seems that in the first execution it uses the old code. Now I have watched the status changes in VS showing that it compiles, deploys the new code to the emulator but on occasion (and I have tried to see something that I do to cause it but no luck) it will use the old code. Stop the app and execute it again (status shows only the execution) and the new XAML (or C#) will be used.
-
Yonglun Liu (Shanghai Wicresoft Co,.Ltd.) 50,126 Reputation points Microsoft External Staff
2022-08-03T05:20:26.567+00:00 I've been testing for a long time, but can't reproduce your issue.
In my side, I used
Microsoft Visual Studio Community 2022 (64-bit) Version 17.1.6and Pixel 5 with Android API 30 for test. Could you please provide the information about your development environment?It would be helpful for us to find the real reason.
In addition, you could also report this problem to VS team. If you want to report it, you could refer to Report a problem with the Visual Studio product or installer.
-
Lloyd Sheen 1,486 Reputation points
2022-08-03T16:05:10.353+00:00 VS is Microsoft Visual Studio Community 2022 (64-bit) - Current
Version 17.2.5Emulator is Pixel 5 (Android).
The problem with telling exactly what the problem is that it is not consistent. As I stated above I have cleaned the solution and rebooted. As of the last 2 days I have not had a problem so I again suggest that caching seems to be the problem as when I clear the solution the problem does not show up for a couple of days, and also because I have not put my PC on sleep with VS still running.
-
Yonglun Liu (Shanghai Wicresoft Co,.Ltd.) 50,126 Reputation points Microsoft External Staff
2022-08-04T05:12:38.73+00:00 Thanks for your feedback.:)
I'll give feedback to VS team about caching causing this issue.
In addition, it's not recommended to run VS during your PC is sleep mode, because any open documents and applications are put in memory while the computer goes into a low-power state.
Sign in to comment
Sign in to answer