You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once I kill the 14100 process, the next extraction will finally begin.
1> TaskRun (Xamarin.Build.Download.XamarinDownloadArchives) 中にアセンブリが読み込まれました: Microsoft.Win32.Registry, Version=4.1.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a (場所: E:\DataFromC\NuGet\packages\xamarin.build.download\0.11.4\buildTransitive\Microsoft.Win32.Registry.dll、MVID: f165d2aa-905d-4dd4-8e4a-317d747f8224、AppDomain: [Default])
1> Extracting C:\Users\wangyk\AppData\Local\XamarinBuildDownloadCache\GAppM-10.28.0.tgz to C:\Users\wangyk\AppData\Local\XamarinBuildDownloadCache\GAppM-10.28.0
1> E:\DataFromC\NuGet\packages\xamarin.build.download\0.11.4\buildTransitive\Xamarin.Build.Download.targets(51,3): error XBD002: Unpacking failed. Please download 'https://dl.google.com/firebase/ios/analytics/4d5ec9a36b6d4fd4/GoogleAppMeasurement-10.28.0.tar.gz' and extract it to the 'C:\Users\wangyk\AppData\Local\XamarinBuildDownloadCache\GAppM-10.28.0' directory and create an empty file called 'C:\Users\wangyk\AppData\Local\XamarinBuildDownloadCache\GAppM-10.28.0.unpacked'.
1> Unpacking failure reason:
1> 7-Zip 18.05 (x86) : Copyright (c) 1999-2018 Igor Pavlov : 2018-04-30
1>
1> Scanning the drive for archives:
1> 1 file, 10038515 bytes (9804 KiB)
1>
1> Extracting archive: C:\Users\wangyk\AppData\Local\XamarinBuildDownloadCache\GAppM-10.28.0.tgz
1> --
1> Path = C:\Users\wangyk\AppData\Local\XamarinBuildDownloadCache\GAppM-10.28.0.tgz
1> Type = gzip
1> Headers Size = 10
1>
1>
1> Would you like to replace the existing file:
1> Path: C:\Users\wangyk\AppData\Local\XamarinBuildDownloadCache\GAppM-10.28.0\GAppM-10.28.0.tar
1> Size: 40711680 bytes (39 MiB)
1> Modified: 2024-06-12 13:37:33
1> with the file from archive:
1> Path: GAppM-10.28.0.tar
1> Size: 40711680 bytes (39 MiB)
1> Modified: 2024-06-12 13:37:33
1> ? (Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit?
1> Downloading https://dl.google.com/dl/cpdc/85bda285a1954024/MLKitCommon-11.0.0.tar.gz to C:\Users\wangyk\AppData\Local\XamarinBuildDownloadCache\MLKCommon-11.0.0.tgz
1> (2272/2400715b), total 0.0%
1> (240320/2400715b), total 10.0%
1> (480928/2400715b), total 20.0%
1> (721056/2400715b), total 30.0%
1> (960480/2400715b), total 40.0%
1> (1212416/2400715b), total 50.0%
1> (1441792/2400715b), total 60.0%
1> (1687552/2400715b), total 70.0%
1> (1933312/2400715b), total 80.0%
1> (2162672/2400715b), total 90.0%
1> (2400715/2400715b), total 100.0%
1> Downloading Complete
1> Extracting C:\Users\wangyk\AppData\Local\XamarinBuildDownloadCache\MLKCommon-11.0.0.tgz to C:\Users\wangyk\AppData\Local\XamarinBuildDownloadCache\MLKCommon-11.0.0
4.Look, what have we found? It wants us to agree to whether to overwrite. ? (Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit?
Obviously, the extraction has been waiting for a response.
So, the fix is quite simple.
Relevant log output
The text was updated successfully, but these errors were encountered:
You should see a file called "GAppM-8.9.1.unpacked" in the XamarinBuildDownloadCache directory. Make a copy of that and rename the file to "GAppM-10.28.0.unpacked".
VS should now recognize that the folder now exists and shouldn't prompt for the Overwrite of the folder in the background, which was the cause of the build hang.
Android framework version
Other
Affected platform version
It should have started a long time ago.
Description
Currently, I am using the latest VS2022 17.12.0, and when building an iOS application on Windows, the build task hangs forever.
And through diagnostics, I had found that the process was stuck in the state of extracting GAppM-10.28.0.tgz.
4.Look, what have we found? It wants us to agree to whether to overwrite.
? (Y)es / (N)o / (A)lways / (S)kip all / A(u)to rename all / (Q)uit?
Obviously, the extraction has been waiting for a response.
So, the fix is quite simple.
Relevant log output
The text was updated successfully, but these errors were encountered: