![]() In my case I'm debugging a problem that occurs for people doing updates :-(Ĭhanges to resources are being detected and propagated to the app but old code was still being invoked.Īs you can see from the screenshot below, the runtime type of the object being created is different - it's an older version of the class. Uninstalling is not always an option - it's normally my first point of uninstalling on the device. ![]() The problem still occurs Xamarin Studio 6.2 build 1829. But this will have to do for me right now. I suppose you "should" be able to pick up the path to adb through properties defined in the build, and perhaps even the device you are deploying to as well as your package name. ![]() This works if you have adb in your path and only one device connected. In the project properties, under build events, I added a post-build event like this:Īdb shell am force-stop my. If I kill the app through the task switcher and restart it, the changes will appear.Īs an addition to this post, this is how I solved my problem for now. The problem is that the changes aren't picked up during the app restart on the emulator. The code is properly built and the result is deployed into the. It turns out though that it has nothing to do with the build. I've been looking at the build process trying to figure out if there is something wrong there. If I redeploy/run once more, the changes will appear. The symptom is that if I change a code file and redeploy/run the app without debugging, I will not see my latest change. I'm on Visual Studio 2015 with the current latest stable release of Xamarin. I'm running fast deployment and shared runtimes during development. So I've been having this issue, or at least I thought this was the issue, for a long while.
0 Comments
Leave a Reply. |