onAnimatedValueUpdate WARN

[Bardreamaster]

Describe the bug

Run /fronted locally, with prose server deployed on server which is deployed by Docker from kodefox/prose:latest. And Test APP on iOS(16.6.1) latest Expo. And no plugins installed.

There is a warning while click Notifications in Profile page, shown as below(RCTLog.js 36:5). Others looks good.

 WARN  Sending `onAnimatedValueUpdate` with no listeners registered.
 WARN  Sending `onAnimatedValueUpdate` with no listeners registered.
 WARN  Sending `onAnimatedValueUpdate` with no listeners registered.

REQUIRED: answer the following questions:

• If this is related to your mobile app:
  • Are you running it through Expo, or did you build it?
  • Is it running on your mobile device or on a simulator?

To Reproduce

Steps to reproduce the behavior:

1. Run api and fronted app
2. Click Notifications in Profile page, or refresh post page, click like button.
3. See warrning.

Environments

Desktop (please complete the following information):

• OS: Debian 10

Smartphone (please complete the following information):

• Device: iPhone
• OS: iOS 16.6.1

GraphQL API (please complete the following information):

Please indicate where the Prose GraphQL API is running.

• On my development machine.

Have you deployed it somewhere? If so, what domain or IP address did you deploy it at?

• prose.robook.org

How specifically did you configure the mobile app to connect to the API?

• Only make fronted app point to ProseUrl.

[starjustice]

Hey @Bardreamaster, thank you for opening this issue.

I want to clarify that this warning is not a critical bug that will break the app or render any feature non-functional. However, after conducting our investigation, we suspect that this warning originates from the React Navigation package, as indicated in this issue: https://github.com/react-navigation/react-navigation/issues/7839.

we will try implementing a fix for this warning.

[Bardreamaster]

Thanks for help!

[starjustice]

I want to inform you that we have already addressed this issue in the v2.0.0-beta branch with the following commit: Commit Link. If you encounter any other issues, please feel free to create a new one.