All you need to do to fix this is to run “ dotnet build” again. Move this file to a directory with a valid Android ABI name such as 'libs/armeabi-v7a/'. If you scroll back through the list of errors to the first error, it’s something like “ packages\.21-arm64\11.0.200-ci.master.85\runtimes\android.21-arm64\native\ : error XA4301: Cannot determine ABI of native library 'packages\.21-arm64\11.0.200-ci.master.85\runtimes\android.21-arm64\native\'. In fact you get pages and pages of errors, enough to make you think that you’ve done something wrong. Unfortunately whilst this fixes the issues restoring packages, it still doesn’t fix the build. To fix this we need to specify a nfig with the following content. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages, “ Unfortunately this didn’t work for me, giving an error stating “ error NU1101: Unable to find package .21-arm64. The next step is to navigate to the directory where the Android app was created and run dotnet build. New Projectįor Android, there’s a new dotnet project template, making it easy to create a new Android application from the command prompt by typing “dotnet new Android -o ”. Open the Android SDK Manager from the Tools, Android menu.įollow any prompts to update or repair your Android SDK. I’m not saying this will happen to everyone but it’s worth taking an opportunity to open the Android SDK Manager and confirm everything is installed correctly. Luckily the Android SDK Manager is able to detect this and will prompt to repair your installation if required. Now, somewhere along the line my Android SDK installation got all messed up. Execute the followingĬd "C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\Current\Bin\SdkResolvers\" echo > ntinel ![]()
0 Comments
Leave a Reply. |