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][Android] Backport fix NetworkInterface.GetAllNetworkInterfaces #77260

Conversation

simonrozsival
Copy link
Member

@simonrozsival simonrozsival commented Oct 20, 2022

Backport of #76370 and #76541 to release/6.0

Fixes #75809
Fixes #76493
Fixes dotnet/android#6973

/cc @steveisok @akoeplinger

Customer impact

Note: This change was also previously backported to release/7.0 (#76565). It was an oversight that it did not come back to release/6.0 as well.

Several MAUI customers reported problems with the current implementation in #75809 and #76493

Testing

  • unit tests in CI
  • locally on physical device (Android API 31) and Android emulator (API level 21)

Risk

Low. The change is inspired by an existing implementation in Xamarin.Android.

simonrozsival and others added 2 commits October 20, 2022 12:18
* Revert "[Android] Port getifaddrs implementation from Xamarin.Android (dotnet#71943)"

This reverts commit 1de4a5c.

* Fix allocating memory block for interfaces and addresses on recent Android SDKs

* Detect loopback interface on Android

* Add comment with explanation

* Simplify the changes to be closer to the original code

* Fix build

* Fix typos

Co-authored-by: Alexander Köplinger <[email protected]>

* Improve comment

* Indent using spaces instead of tabs

* Remove check for ifaddrs.h

* Add ANDROID_GETIFADDRS_WORKAROUND

* Update comment

Co-authored-by: Alexander Köplinger <[email protected]>
@simonrozsival simonrozsival added Servicing-consider Issue for next servicing release review area-System.Net os-android labels Oct 20, 2022
@ghost ghost assigned simonrozsival Oct 20, 2022
@ghost
Copy link

ghost commented Oct 20, 2022

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

Issue Details

Backport of #76370 and #76541 to release/6.0

/cc @steveisok @akoeplinger

Customer impact

Several customers reported problems with the current implementation in #75809 and #76493

Testing

  • unit tests in CI
  • locally on physical device (Android API 31) and Android emulator (API level 21)

Risk

Low. The change is inspired by an existing implementation in Xamarin.Android. This change was also previously backported to release/7.0 (#76565)

Author: simonrozsival
Assignees: -
Labels:

Servicing-consider, area-System.Net, os-android

Milestone: -

@simonrozsival
Copy link
Member Author

/azp run runtime-manual

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@simonrozsival
Copy link
Member Author

/azp list

@azure-pipelines

This comment was marked as resolved.

@marek-safar marek-safar added this to the 6.0.x milestone Oct 20, 2022
@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Oct 20, 2022
@rbhanda rbhanda modified the milestones: 6.0.x, 6.0.12 Oct 20, 2022
@carlossanlop
Copy link
Member

@akoeplinger can you please provide a code review sign-off?

@carlossanlop
Copy link
Member

Failures are old and logs are gone. Need to rebase and re-run since there were several failures. Closing and reopening.

@carlossanlop carlossanlop reopened this Nov 3, 2022
@carlossanlop
Copy link
Member

CI failures unrelated:

Approved by Tactics. Signed off by code reviewer. No OOB package authoring changes needed. Ready to merge. :shipit:

@carlossanlop carlossanlop merged commit 6376e01 into dotnet:release/6.0 Nov 3, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants