-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Android][Test] Failed to install mobile app #89567
Comments
@premun Are you aware of any known issue which could call the Android app failing to be installed? |
@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] |
@SamMonoRT Not all warnings are treated as errors - only the missing prototype warnings are treated as errors. However the compiler now emits more warnings ( Also @akoeplinger fixed the |
Yes I think that specific error should be fixed now. Let's close this. |
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
Fill the error message using step by step known issues guidance.
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
The text was updated successfully, but these errors were encountered: