AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Xamarin studio for visual studio11/27/2023 ![]() When I update the new project to the latest version it actually works. All newer versions up to 1.8 have the same error. It is also using that library but in version 1.0.0.1. I checked how it looks like for a new app. ![]() Et voila - app is not starting anymore like before. So I made the class MainActivity abstract. When updateing to Version 1.8.0 (1.2.1.1 before) the following compile error occurs: error: MainActivity is not abstract and does not override abstract method onNavigationItemSelected(MenuItem) in OnItemSelectedListener Updated 3rd party libraries step by step. The app builds and starts but crashes because of outdated 3rd party libaries - but this OK, because it actually starts! : Got new device list from adb with 1 devicesĪfter this issue cost me a lot of time, here is what solved the issue for me:Ĭhecked out the last working version from the repository.Ĭhanged Target Version to Android 13 - Api 33. ![]() The output of "Xamarin Diagnostics" is just this three lines : Tracking android devices started Starting a new Project with the default template works. When I check with the adb devices via cmd, the emulator is connected.Ĭleaning the project and delete bin and obj folder also doesn't help. Visual Studio stops debugging and the App is not deployed to the emulated device. = Deploy: 1 succeeded, 0 failed, 0 skipped =Īnd that's it. The output of the Output pane in Visual Studio confirms this: Build succeeded.ĭeployment was successful to pixel_5_-_api_33. Visual Studio also build the project and states Deploy succeeded. After verify that I am using the Debug profile, I am clicking the "play" button. I start Visual Studio, load my project and wait until everything is loaded and also the background tasks are done (don't know if this is required). Make sure to run the emulator on the laptop screen. To change this setting, type: bcdedit /set hypervisorlaunchtype off. I also setup a device in the Android Device Manager with the current latest API (Android 13 - API 33), which can be started. On the last entry all the way down, make sure hypervisorlaunchtype is Off. Close all Visual Studio instances after downloading the extensions to begin the installation process. Click the Download button in the Xamarin Extensions - Syncfusion. On the left, click the Online tab and type Xamarin Extensions in the search box. I selected everything for this in the Visual Studio installer.ĭuring my research about the problem I also verified already that Hyper-V and the HypervisorPlatform-Feature and installed and enabled as well as the Android Emulator Hypervisor driver Tool/Extra is installed via the Android SDK and Tools program. In Visual Studio 2017 or lower, go to Tools -> Extensions and Updates. In earlier versions of Visual Studio 2015, if you used higher tiers of Visual Studio such as Visual Studio Enterprise, Xamarin came with the package so you. For this I need to test and debug my Android application in the Android Emulator. I am using Visual Studio 2022 with all updates installed (version 17.5.1) to create a Xamarin project on a fresh Windows 11 Pro System.
0 Comments
Read More
Leave a Reply. |