-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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-rc1] Fix loading app local ICU #57992
[release/6.0-rc1] Fix loading app local ICU #57992
Conversation
Tagging subscribers to this area: @tarekgh, @safern |
CC @danmoseley @ericstj. I am asking to port it to RC 1 branch. Should I manually port it to RC 2 too? |
@tarekgh no if it goes into RC1 then it will flow to RC2 automatically. if we wanted to protect against future bugs like this using automation -- presumably we would need a test project to restore the nuget ICU package? is that a reasonable thing to do? |
wasm failure is xunit .. #11063 |
None of the staging failures are relevant (although, I can't root cause the tvOS crashes, not so many are crashing that it would look like a widespread failure in basic API, as if ICU wouldn't load) |
|
Backport of #57971 to release/6.0-rc1
Fixes #57942
/cc @tarekgh
Customer Impact
Customer reported that when the app opt-in using ICU app-local (feature which uses ICU NuGet package instead of using the system installed ICU libraries) the app crashes.
This regression happened because we have started using a new two ICU APIs and we loaded the pointers of these APIs from a specific ICU library
libicui18n
. This work with the installed system ICU libraries but didn't work with the ICU comes from the NuGet. Users using ICU app-local with this issue will not be able to start their app.The fix is just to use the library name
libicuuc
instead. That will make it work in all scenarios when using the ICU system libraries or when using ICU app-local.Testing
I have tested this manually with all scenarios when using ICU system libraries and when using ICU app-local. I tested this on Windows and Linux. Also, I have run the whole regression tests with the fix without any problem.
Risk
is very low. we are not changing any real code more than pointing at correct library and we have tested the fix in different environments with different settings.