Intl flavor throws exception when using Intl.NumberFormatter#format about jsc-android-buildscripts

[DanielZlotin]

Thanks for reporting, basically a duplicate of #36. closing to keep all discussions in 1 topic

[ericketts]

The plot thickens -- if I force resolve the non intl flavor of android-jsc in my build.gradle config, not only does the above code block execute fine, but it appears that the (more complex) language i18n functionality also works properly, at least with ru-RU as the locale.

I've confirmed that the build.gradle was being respected by inspecting the JSC related .so files in the generated apk, and comparing the sizes against the known configuration build sizes; so I know that the intl and non-intl flavors haven't somehow become reversed... very puzzling behavior!

[Kmakinator]

@ericketts is there any chance you can send me *.apk file where it actually works?

edit
Turning off intl just sets everything to en-US locale, instead of crashing with intl turned on...

[ericketts]

@Kmakinator you'd like me to send you an apk built with the non-intl flavour? That's the only case where it works presently...

I'm happy to do that, but would need to put together a minimal repro (since the actual APK contains IP I cannot release), so want to make sure I understand you properly before spending the time creating the minimal repro...

[ericketts]

So a bit more information, it turns out that unbeknownst to me, in the case of the non-intl flavored JSC being used, the Intl API was being polyfilled. If I prevent the polyfill from happening, everything is broken as you'd expect.

So this ticket now is solely about the intl flavor JSC failing when calling Intl.NumberFormat#format as outlined in the root comment.