[Webassembly] dotnet/runtime update broke the aspnetcore build #88250

Activity

1. ghost added

   needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area ownersAn area label is needed to ensure this gets routed to the appropriate area owners

   on Jun 30, 2023
2. ghost added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Jun 30, 2023
3. ilonatommy commented on Jun 30, 2023

   

   ilonatommy

   on Jun 30, 2023

   Member

   More actions

   It might be this line:

   - const applicationCulture = resourceLoader.startOptions.applicationCulture || (navigator.languages && navigator.languages[0]);
   + const applicationCulture = resourceLoader.startOptions.applicationCulture || ENVIRONMENT_IS_WEB ? (navigator.languages && navigator.languages[0]) : Intl.DateTimeFormat().resolvedOptions().locale;
   

   because we apparently load en-US instead of cultures we would like to test. It means the applicationCulture is recognized incorrectly. The change to that line was done between the last successful update and the one that is failing, in #86255. I will try to test if this theory is correct.
4. ghost added

   in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

   on Jun 30, 2023
5. maraf

   added

   arch-wasmWebAssembly architectureWebAssembly architecture

   area-System.Runtime.InteropServices.JavaScript

   os-browserBrowser variant of arch-wasmBrowser variant of arch-wasm

   and removed

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Jun 30, 2023
7. maraf

   removed

   needs-area-labelAn area label is needed to ensure this gets routed to the appropriate area ownersAn area label is needed to ensure this gets routed to the appropriate area owners

   on Jun 30, 2023
8. maraf

   closed this as completedin #88264on Jun 30, 2023
9. ghost removed

   in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

   on Jun 30, 2023
10. ghost locked as resolved and limited conversation to collaborators on Jul 31, 2023