Some kinda of Sync issue only with 0.79.1

[MoamberRaza]

Description

to regenerate just go with this lib and see.

Steps to reproduce

https://www.npmjs.com/package/react-native-select-dropdown
it was working fine with 0.78.2

React Native Version

0.79.1

Affected Platforms

Runtime - iOS

Output of npx @react-native-community/cli info

System:
  OS: macOS 15.4
  CPU: (8) arm64 Apple M2
  Memory: 181.58 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.13.1
    path: ~/.nvm/versions/node/v22.13.1/bin/node
  Yarn:
    version: 1.22.22
    path: /opt/homebrew/bin/yarn
  npm:
    version: 11.1.0
    path: ~/.nvm/versions/node/v22.13.1/bin/npm
  Watchman:
    version: 2024.12.02.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.4
      - iOS 18.4
      - macOS 15.4
      - tvOS 18.4
      - visionOS 2.4
      - watchOS 11.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.3 AI-243.24978.46.2431.13208083
  Xcode:
    version: 16.3/16E140
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 22.0.2
    path: /Library/Java/JavaVirtualMachines/jdk-22.jdk/Contents/Home/bin/javac
  Ruby:
    version: 3.3.0
    path: /Users/m2/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 18.0.0
    wanted: ^18.0.0
  react:
    installed: 19.0.0
    wanted: 19.0.0
  react-native:
    installed: 0.79.1
    wanted: ^0.79.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: true

Stacktrace or Logs

--

Reproducer

nothingtoshow.com

Screenshots and Videos

i am using
https://www.npmjs.com/package/react-native-select-dropdown
it was working smooth with previous version 0.79.1 and now its been stop. i also reported to this lib communicators. please look in to and provide some helpful reply.

[react-native-bot]

Warning

Missing reproducer: We could not detect a reproducible example in your issue report. Please provide either:

• If your bug is UI related: a Snack
• If your bug is build/upgrade related: a project using our Reproducer Template
• Otherwise send us a Pull Request with the RNTesterPlayground.js edited to reproduce your bug.

[cipolleschi]

@MoamberRaza can you provide a proper reproducer? With so little information is impossible for us to under stand if the issue is in React Native or in the library.
You could also be hitting an edge case, so integrating the library directly in a sample app might not trigger the issue right away. That's why we need a reproducer for it.
Also consider opening the issue in the library repository, as library maintainer might be quicker in triaging or fix the issue.
This is the GH repo: https://github.com/AdelRedaa97/react-native-select-dropdown
Also, this library last commit is from last year. It might be unmaintained.

[MoamberRaza]

firstly i though that was only the issue with dropdown lib but currently the case of android fast synchronizations. call few apis in a row and go back and forth with app state even with cancellation token. it will not properly cancelled only with the version 0.79.1 and with android only and i have seen my different lib are not properly work with this version but lets say focus to performance. call few promises and you might get into it.

[cipolleschi]

@MoamberRaza we really need a reproducer. We can't craft reproducers ourselves for each issues we receive, or we would spend all our time just creating those reproducers.
Investing a bit of time in creating a reproducer has various pros:

1. Sometimes, just going to the process of creating the reproducer will tell you where is the problem and you can fix it yourself
2. It creates an isolated reproducer for the issue, so we can focus on solving the specific issue
3. it reduces the time between the report and the fix.

We are not going to look into this issue without a proper reproducer.

Thanks for your understanding.

[MoamberRaza]

do understand and really appreciate your and team such efforts, let me share again to get probably chance to recreate it. i am calling 2/3 recursive call and hitting api/promises as i am going to background there is one more to add here and before calling it cancelling running item from queue for performance issues and memory leaks and when come back to the foreground again i am call one api to let server now that i am now on. then again start same recursive process with few more promises initially every time you can say 2/3.
now problem is ios is handling is very efficiently but this time with 0.79.1 android is no, some times it call that pending process whenever i came back to app. although battery optimisation are well handle and i know all that processes. this was little bit better with old react 0.78.2 android.
hope it make sense this time if you still having it let me know.
even on revopush restarts app behaves differently while loading all of components some times. and all of these only with android.

[cipolleschi]

When I say that we need a reproducer, it means that you need to provide us some code that we can run.
This can happen in three ways:

1. by creating a snack:
2. by creating. a PR against react-native repository by modifying the RNTesterPlayground.js file
3. by creating a reproducer using this template

You can find more information here

A description is not something we can execute to verify the bug ourselves... 😅

[MoamberRaza]

scenario is i am running recursive functions and api in a series
IOS engine behave efficient and loaded up so quickly where as android and specially older devices almost not usable for Production people although InteractionManager is implemented and helpful tool here. and last hint is before this kotlin file release probably like 0.76.0 was a smooth experienced i have ever.

i only have a way and that is describe and request :) to understand my words with poor examples. (BTW the real effort here ). i appreciate your patience.