So 17.4 takes VS to a new low. So many problems even old projects don't work any more

Lloyd Sheen 1,476

So I updated to 17.4 hoping that this would help.

So I created a new Maui project and the errors far exceeded the 17.3 screwup. So new projects are farther from being created than before.

Then I open a old working project. It gets

Severity Code Description Project File Line Suppression State
Error APT2144 invalid file path 'C:\Visual Stuido Stuff\Maui\NHLMauiApp\obj\Debug\net6.0-android\resizetizer\sp\maui_colors.xml'. NHLMauiApp C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Aapt2.targets 123

Severity Code Description Project File Line Suppression State
Error APT2144 invalid file path 'C:\Visual Stuido Stuff\Maui\NHLMauiApp\obj\Debug\net6.0-android\resizetizer\sp\maui_splash_image.xml'. NHLMauiApp C:\Program Files\dotnet\packs\Microsoft.Android.Sdk.Windows\32.0.476\tools\Xamarin.Android.Aapt2.targets 123

Now I have a non usable VS and with every attempt to fix it , it gets worse.

THIS IS PATHETIC. In over 30 years of dev on MS platforms this is so far the worst that if anyone looked at the way it screws up no one would use it.

I really need to talk with someone. RIGHT NOW!!!!!

Lloyd Sheen 1,476 Reputation points

2022-11-09T21:47:35.42+00:00

And to top it off the two errors above are just plain stupid. If I do a text search in the entire project for maui_colors.xml it does not exist as the error shows but there is nothing in the code that indicates the use of this file. The same for maui_splash_image.xml.

And to make it even better , lets click on the error APT2144. Oops! No F1 help match was found.

The incompetence of this release and the previous problems are incredible. I guess my evaluation that I presented last week was even more right than I thought. I had to tell them that VS was on its way down and Maui was not ready for prime time.

YES I NEED TO TALK (NOT MESSAGE) WITH SOMEONE THAT HAS SOME PULL AT MS.
Rob Caplan - MSFT 5,437 Reputation points Microsoft Employee

2022-11-10T18:11:28.65+00:00

Hi Lloyd,

As discussed previously, it sounds like you have a corrupted install causing multiple symptoms, but we don't have details to know what specifically. It's likely that the same issues you have with your 17.3 install will continue to corrupt the 17.4 upgrade if not cleaned up.

For help, and to talk to somebody directly, please open a support ticket at https://support.serviceshub.microsoft.com/supportforbusiness/create?sapId=27261ac1-649d-6bd3-6b8f-427ac125ade8 and choose Developer Tools / .NET / .NET 6.0 / Tools and Compilers / Multi-platform App UI (.NET MAUI) Tools

--Rob
balintn 16 Reputation points

2022-12-28T16:09:07.143+00:00

I thought this comment was way over the top, until I hit the same issue myself - and I'm stuck.
Upgraded to latest version of VS 2022. Cleaned, re-built, exited, restarted, I still get the error.
In my case it is a migration from Xamarin to Maui, VS 2022 17.4.3.
Error messages are:
APT2144 invalid file path 'C:...\obj\Debug\net6.0-android\res\resources\styles\styles.xaml'
APT2144 invalid file path 'C:...\obj\Debug\net6.0-android\res\resources\styles\colors.xaml'
No community information anywhere, no help, no search results in code.

My guess is that Maui changed the way styles and colors are specified and the migrated project does not macth new build expectations.
balintn 16 Reputation points

2022-12-29T13:42:26.5+00:00

ie I decided to start creating community conten after resolving the issue: thttps://stackoverflow.com/questions/74951852/how-to-resolve-vs-2022-maui-invalid-file-path-error/74951853#74951853

1 answer

Shawn Bowen 1 Reputation point

2022-11-17T01:13:46.957+00:00

I had the same issue. When I ran a Clean and Rebuild it resolved it for me. Have you given that a try?
Please sign in to rate this answer.
Lloyd Sheen 1,476 Reputation points

2022-11-18T19:33:18.867+00:00

I've pretty much done everything. Sometimes a simple Clean and Rebuild works, sometimes not.

Today I tried using my phone rather than the emulator (Android). This showed me some of the screwy things that are happening that you don't see with the emulator. At one point I was asked if phone could deal with info transfer. This happened about 5 times and then the phone disappeared from the list of emulators/phones.

At present I am waiting to see if VS will ever figure out that I had closed the emulator. It has been about 30 mins that it is "Ready". Does no one at MS give a damm about VS? Do they do any QA???

Lloyd Sheen 1,476 Reputation points

2022-11-18T19:36:16.817+00:00

To get anywhere I had to reboot. If VS cannot figure out that there is no emulator running and deal with it then I have little hope for VS in the future.

MD YASIR ARAFAT 1 Reputation point

2022-12-02T21:47:53.337+00:00

Thanks! My solution was also built successfully after cleaning and rebuilding!

Lloyd Sheen 1,476 Reputation points

2022-12-02T23:09:36.347+00:00

I have stopped using an emulator and am using my phone. I have tried 3 different emulators and they all fail quickly.

I had an MS person on Teams looking at what was happening and he sugested to run VS in Admin mode. This did not make much difference at least in a positive way.

My dev is consitantly a couple of mins of edititng (editor is not really good) and then try to execute. At that point it is a toss up. After a few problems I stop VS and emulator. Then after that fails I reboot. I was reading a post that many Maui devs are not happy with Maui and VS. It was made GA long before it should have been and is a reason to ditch MS at this point.

Lloyd Sheen 1,476 Reputation points

2022-12-28T16:12:21.807+00:00

I have cleaned ,Rebuilt, rebooted. At present this dev app is in horrible shape when trying to do Maui. The Android emulator is horrible and just spent an hour trying to get an emulator to stop showing another app. Finnaly found the Factory Reset option in Tools Android Device Manager

Lloyd Sheen 1,476 Reputation points

2022-12-28T17:18:03.113+00:00

And this pile of crap known as Visual Studio and Maui brings more delight:

Severity Code Description Project File Line Suppression State
Error ADB0060: Mono.AndroidTools.InsufficientSpaceException: There is not enough storage space on the device to store package: /data/local/tmp/com.companyname.NHLMauiApp-Signed.apk. Free up some space and try again.
at Mono.AndroidTools.Internal.AdbOutputParsing.CheckInstallSuccess(String output, String packageName) in /Users/runner/work/1/s/xamarin-android/external/monodroid/tools/msbuild/external/androidtools/Mono.AndroidTools/Internal/AdbOutputParsing.cs:line 325
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at AndroidDeviceExtensions.<PushAndInstallPackageAsync>d__12.MoveNext() in /Users/runner/work/1/s/xamarin-android/external/monodroid/tools/msbuild/external/androidtools/Xa

There was alot more but this horrible posting site does not allow to show it.

MS GET YOUR ACT TOGETHER , DO YOU EVEN CARE A LITTLE ABOUT THE DEVELOPERS????
Sign in to comment

Share via

So 17.4 takes VS to a new low. So many problems even old projects don't work any more

1 answer