Skip to content
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

[release/6.0-rc2] Work around for forbidden "Roslyn4.0" in test name on Android #59281

Merged

Conversation

directhex
Copy link
Member

@directhex directhex commented Sep 17, 2021

Backport of #59263 to release/6.0-rc2

/cc @steveisok

Customer Impact

This should fix failing tests, and additionally prevent users using AndroidAppBuilder from encountering defective APKs when their project name includes the forbidden \.\d sequence

Testing

Passed CI on main

Risk

Low

…#59263)

Android apk names must be valid Java class names, and It is forbidden in Java for a class name component to have a leading numeric digit. So whilst "net.dot.foo3_1" is legal, "net.dot.foo3.1" is illegal. Use a Regex to detect and rewrite all cases of this in AndroidAppBuilder
@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@lewing lewing added the Servicing-consider Issue for next servicing release review label Sep 17, 2021
@ghost
Copy link

ghost commented Sep 19, 2021

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of #59263 to release/6.0-rc2

/cc @steveisok

Customer Impact

This should fix failing tests, and additionally prevent users using AndroidAppBuilder from encountering defective APKs when their project name includes the forbidden \.\d sequence

Testing

Passed CI on main

Risk

Low

Author: directhex
Assignees: -
Labels:

Servicing-consider, area-Infrastructure-mono

Milestone: -

@Anipik Anipik merged commit f471fa4 into dotnet:release/6.0-rc2 Sep 21, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Nov 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-mono Servicing-consider Issue for next servicing release review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants