Repository navigation
[Android][Test] Failed to install mobile app #89567
Copy link
Copy link
Closed
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-Interop-monoblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Description
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=353048
Build error leg or test failing:
Pull request: #89467
Error Message
System.AggregateException : One or more errors occurred. (Failed to install mobile app.
Expected: True
Actual: False) (The following constructor parameters did not have matching fixture data: _Global globalVar)
---- Failed to install mobile app.
Expected: True
Actual: False
---- The following constructor parameters did not have matching fixture data: _Global globalVar
Stack Trace:
----- Inner Stack Trace #1 (Xunit.Sdk.TrueException) -----
at Interop_NativeLibrary._Global..ctor()
at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.ConstructorInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
----- Inner Stack Trace #2 (Xunit.Sdk.TestClassException) -----
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "Failed to install mobile app",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=353048
Error message validated: Failed to install mobile app
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/27/2023 2:36:55 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 3 | 26 | 35 |
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-Interop-monoblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Activity
fanyang-mono commentedon Jul 27, 2023
@premun Are you aware of any known issue which could call the Android app failing to be installed?
SamMonoRT commentedon Aug 3, 2023
@lambdageek - I'm seeing some logs failures indicating there were some warnings (I guess now treated as errors after https://github.com/dotnet/runtime/pull/89197/files ?) I'm not sure if these are related to the change though - https://dev.azure.com/dnceng-public/public/_build/results?buildId=353048&view=logs&j=11fc76eb-f2d5-5967-e9b4-f54329587f75&t=5d22afdd-fd55-5fd8-7ab1-37ebf23474bd
/__w/1/s/src/mono/msbuild/android/build/AndroidBuild.targets(259,5): error MSB4018: Scanning dependencies of target System.Threading.Channels.dll [/__w/1/s/src/tests/FunctionalTests/Android/Device_Emulator/AOT/Android.Device_Emulator.Aot.Test.csproj]
/__w/1/s/src/mono/msbuild/android/build/AndroidBuild.targets(259,5): error MSB4018: [ 65%] Building ASM object CMakeFiles/System.Threading.Channels.dll.dir/__w/1/s/artifacts/obj/Android.Device_Emulator.Aot.Test/Release/net8.0/android-arm64/mobile/System.Threading.Channels.dll.s.o [/__w/1/s/src/tests/FunctionalTests/Android/Device_Emulator/AOT/Android.Device_Emulator.Aot.Test.csproj]
/__w/1/s/src/mono/msbuild/android/build/AndroidBuild.targets(259,5): error MSB4018: clang: warning: argument unused during compilation: '-D FORCE_AOT=1' [-Wunused-command-line-argument] [/__w/1/s/src/tests/FunctionalTests/Android/Device_Emulator/AOT/Android.Device_Emulator.Aot.Test.csproj]
/__w/1/s/src/mono/msbuild/android/build/AndroidBuild.targets(259,5): error MSB4018: clang: warning: argument unused during compilation: '-D STATIC_AOT=1' [-Wunused-command-line-argument] [/__w/1/s/src/tests/FunctionalTests/Android/Device_Emulator/AOT/Android.Device_Emulator.Aot.Test.csproj]
/__w/1/s/src/mono/msbuild/android/build/AndroidBuild.targets(259,5): error MSB4018: clang: warning: argument unused during compilation: '-D ANDROID' [-Wunused-command-line-argument] [/__w/1/s/src/tests/FunctionalTests/Android/Device_Emulator/AOT/Android.Device_Emulator.Aot.Test.csproj]
/__w/1/s/src/mono/msbuild/android/build/AndroidBuild.targets(259,5): error MSB4018: clang: warning: argument unused during compilation: '-fdata-sections' [-Wunused-command-line-argument] [/__w/1/s/src/tests/FunctionalTests/Android/Device_Emulator/AOT/Android.Device_Emulator.Aot.Test.csproj]
/__w/1/s/src/mono/msbuild/android/build/AndroidBuild.targets(259,5): error MSB4018: clang: warning: argument unused during compilation: '-ffunction-sections' [-Wunused-command-line-argument] [/__w/1/s/src/tests/FunctionalTests/Android/Device_Emulator/AOT/Android.Device_Emulator.Aot.Test.csproj]
/__w/1/s/src/mono/msbuild/android/build/AndroidBuild.targets(259,5): error MSB4018: clang: warning: argument unused during compilation: '-funwind-tables' [-Wunused-command-line-argument] [/__w/1/s/src/tests/FunctionalTests/Android/Device_Emulator/AOT/Android.Device_Emulator.Aot.Test.csproj]
/__w/1/s/src/mono/msbuild/android/build/AndroidBuild.targets(259,5): error MSB4018: clang: warning: argument unused during compilation: '-fstack-protector-strong' [-Wunused-command-line-argument] [/__w/1/s/src/tests/FunctionalTests/Android/Device_Emulator/AOT/Android.Device_Emulator.Aot.Test.csproj]
/__w/1/s/src/mono/msbuild/android/build/AndroidBuild.targets(259,5): error MSB4018: clang: warning: argument unused during compilation: '-D _FORTIFY_SOURCE=2' [-Wunused-command-line-argument] [/__w/1/s/src/tests/FunctionalTests/Android/Device_Emulator/AOT/Android.Device_Emulator.Aot.Test.csproj]
lambdageek commentedon Aug 4, 2023
@SamMonoRT Not all warnings are treated as errors - only the missing prototype warnings are treated as errors. However the compiler now emits more warnings (
-Wallis new from #89197, also). So those other ones are harmless.Also @akoeplinger fixed the
register_aot_moduleserror which I guess is what is making the builds fail #89922akoeplinger commentedon Aug 4, 2023
Yes I think that specific error should be fixed now. Let's close this.