Skip to content

Conversation

@simonrozsival
Copy link
Member

@simonrozsival simonrozsival commented Jan 20, 2023

We should run our tests targeting API 31 which is currently the Google Play's requirement.

It will be necessary to use Android SDK 31+ for local builds. The build process will show an error message instructing the developer to install newer build tools it they're out of date. The CI already uses SDK version 33 (dotnet/dotnet-buildtools-prereqs-docker#713).

@ghost
Copy link

ghost commented Jan 20, 2023

Tagging subscribers to 'arch-android': @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.

Issue Details

We should run our tests targeting API 31 which is currently the Google Play's requirement.

Author: simonrozsival
Assignees: -
Labels:

os-android

Milestone: -

@simonrozsival
Copy link
Member Author

/azp run runtime-android

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@simonrozsival simonrozsival force-pushed the android-bump-manifest-target-sdk-version branch from 67a19ba to cd8f5b9 Compare January 23, 2023 13:27
@simonrozsival
Copy link
Member Author

/azp run runtime-android

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@simonrozsival
Copy link
Member Author

simonrozsival commented Jan 24, 2023

The test System.Net.Security.Tests.CertificateValidationRemoteServer.ConnectWithRevocation_WithCallback(checkRevocation: True) consistently fails on physical devices but passes on emulators after the bump. That's quite interesting. I'm going to disable the test for now.

@simonrozsival
Copy link
Member Author

/azp run runtime-android,runtime-androidemulator

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@simonrozsival
Copy link
Member Author

The remaining failing tests on Android are related to #80909.

@simonrozsival simonrozsival marked this pull request as ready for review January 24, 2023 12:42
@simonrozsival simonrozsival merged commit 828edfb into dotnet:main Jan 24, 2023
@simonrozsival simonrozsival deleted the android-bump-manifest-target-sdk-version branch January 24, 2023 18:51
@ghost ghost locked as resolved and limited conversation to collaborators Feb 23, 2023
@fanyang-mono
Copy link
Member

/backport to release/7.0-staging

@github-actions github-actions bot unlocked this conversation Dec 7, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Dec 7, 2023

Started backporting to release/7.0-staging: https://github.com/dotnet/runtime/actions/runs/7133508892

@github-actions
Copy link
Contributor

github-actions bot commented Dec 7, 2023

@fanyang-mono backporting to release/7.0-staging failed, the patch most likely resulted in conflicts:

$ git am --3way --ignore-whitespace --keep-non-patch changes.patch

Applying: Set target SDK version
Applying: Update Android docs
Applying: Disable tests that do not pass with target API 31
Applying: Check if the installed Android SDK is up-to-date
error: sha1 information is lacking or useless (src/tasks/AndroidAppBuilder/Templates/AndroidManifest.xml).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0004 Check if the installed Android SDK is up-to-date
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@github-actions
Copy link
Contributor

github-actions bot commented Dec 7, 2023

@fanyang-mono an error occurred while backporting to release/7.0-staging, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants