You sure wouldn't want to be a newbie starting with Xamarin.Android!! It still uses that was deprecated ages ago. As an example, just look at the template for creating a new fragment. It would be nice if all that could be done automatically, but it is not something you do every day, so you put up with out of date templates. I'm sure others would do it differently, but that is my minimum setup when starting a new test app. If it runs ok without errors got on with whatever I need to do for the test app. Change the project to Android 11 (or whatever ) set the min SDK to say 7.0 Then update and to the latest versions. I then remove any reference to Xamarin.Essentials, change the default namespace to "", edit to match the namespace for the global attribute and its namespace. Whenever I create a new test app, I invariably use the Blank template. I really can't remember what template I used when I first created the app, a couple of years ago. Your app has entered a break state, but there is no code to show because all threads were executing external code (typically system or framework code). The debugger is telling me it is not my code e.g. Hence, that was why I tried to debug it and got the error. If I start the app via Start Without Debugging - it just hangs on the splash screen. No, I can't reproduce it when I create say a Blank app from the templates.
0 kommentar(er)
