fix: handle progress being infinite

[matthieuMay]

📜 Description

Add a numerical safety test to keyboard animation progress

💡 Motivation and Context

It solves a random crash in production where progress is infinite

Fixes #739 #737 #735

📢 Changelog

Android

• added isInfinite check along with isNaN;

🤔 How Has This Been Tested?

Releasing it to production via a patch package the error report disappeared

📝 Checklist

• CI successfully passed
• I added new mocks and corresponding unit-tests if library API was changed

[github-actions]

📊 Package size report

Current size	Target Size	Difference
164437 bytes	164428 bytes	9 bytes 📈

[kirillzyusko]

A small note from the author of this lib - such check will lead to UI inconsistency (because we are trying to divide non-zero height by 0, so with this fix we'll send something like { height: 40, progress: 0 }). If you depend on height value, you may see a "ghost" keyboard animations (when there is actually no keyboard on a screen, but you see the part of the animation).

I understand, that it may be hard to prepare a reproduction, because it seems like the error is very flaky and it can be present only in heavy prod apps with reach functionality (i. e. it can be a race conditions and it's hard to reproduce it in simple reproduction example).

To deliver a better user experience and don't crash app (in case if value can not be serialized) - you convinced me guys to have that check in the codebase. It's better to show fake/ghost animation rather than crash the app and totally block user interaction with the app.

Still hope that at some point of time someone will prepare a reproduction example and we can figure out what exactly causes this problem. For now - let's have this fix in a codebase to avoid app crashes 🙂

[kirillzyusko]

And yes, seems like this problem affects many users, so i'll merge a fix and will publish 1.15.1 version straight away 😊