ProgressBar crashes app in new arch on android

[pnthach95]

Current behaviour

In new arch android, ProgressBar crashes app when long length float value is used in progress. It works with 1/2, 1/4 but not 1/3.

Error log: Warning: Error: Exception in HostFunction: Loss of precision during arithmetic conversion: (long) 33.33333333333333

It works on iOS but you have this error in xcode log, Error while converting prop 'accessibilityValue': Loss of precision during arithmetic conversion: (long long) 33.33333333333333

Expected behaviour

ProgressBar should work with long length float value in new arch on android

How to reproduce?

• Create new project and enable new arch
• Run this code and press buttons

const [progress, setProgress] = useState(1);

<ProgressBar progress={progress} />
<Button
  onPress={() => {
     setProgress(1 / 2);
  }}>
  1/2 work
</Button>
<Button
  onPress={() => {
     setProgress(1 / 3);
  }}>
  1/3 not work
</Button>

Preview

Screen_Recording_20241107_141459.mp4

What have you tried so far?

Your Environment

software	version
ios	18.1
android	14
react-native	0.76.1
react-native-paper	5.12.5
node	20.12.1
yarn	3.6.4
expo sdk	x.x.x

[lovegaoshi]

same problem as Sharcoux/slider#102. u can just patch package the accessibilityvalur with a math. round

[duanykruger]

Uppp, same problem! I tried the solution above, but still have the same problem.

[netdown]

@AlenMartinez ProgressBar expects progress value between 0 and 1.

[ThomasLaSalmonie]

Unfortunately I don't have a lot of time to investigate before next week but I face the same issue when I wanted to upgrade to expo 51 to 52. I'm using my iOS device (Iphone 14 Pro) iOS Beta 18.2

But I manage to make thing work using the props animatedValue instead of progress keep the same float (the fix using Math.round was not working for me either)
I know it's not exactly the same feature but At least the component work.

[BogiKay]

Currently, I'm working on a new arch support and this issue going to be fixed as part of the work

[mmuminovic]

Hi guys

Here is a fix: #4568

Please @BogiKay review it