-
Notifications
You must be signed in to change notification settings - Fork 5k
[release/7.0] Allow interop resolvers to return self handle #78779
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
Conversation
/azp run runtime-android |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Approved by tactics in email |
Only things left are a code review sign off from @vargaz or @lambdageek or @thaystg, and verifying the CI results when they're done. |
/azp run runtime-androidemulator |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
/azp run runtime-extra-platforms |
Azure Pipelines successfully started running 1 pipeline(s). |
Any concerns about the CI failures, @lambdageek? |
failures look unrelated: some hardware flakiness |
Branding has been done. Milestone is 7.0.2. Signed-off by area owners. Approved by Tactics. No OOB package authoring changes needed. CI failures unrelated. |
Backport of #78004 to release/7.0
/cc @lambdageek @am11
(Note this an update of #78018 which we had to revert because it broke on Android)
Customer Impact
Customers using the new
GetMainProgramHandle
API to create custom NativeLibrary resolvers in mobile apps are unable to resolve statically linked symbols in their apps.Testing
New CI test, including Android
Risk
Low
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.