react-native-webrtc / react-native-webrtc/react-native-callkeep

backToForeground not working on Galaxy Z Flip and Z Fold series.

Open
#640 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.1k
Forks
511
Avg merge
9h 12m
Merged PRs (30d)
2

Description

Bug report

  • [ v ] I've checked the example to reproduce the issue.

  • Reproduced on:

  • [ v ] Android

  • iOS

Description

My app doesn't come up to foreground when I get a call with or without self-managed mode on foldable Galaxy models. In case of using self-managed mode, phone does just vibrate or ring but app is not opened in both of background state and completely closed state. Without self-managed mode, system call UI is shown, and when I answer the call, system call UI is still shown and app is not opened. These are happened only on Galaxy Z Flip and Fold series. I think backToForeground API is not working on these models.

Steps to Reproduce

Call Galaxy Z Flip or Fold user.

Versions

- Callkeep:4.3.3
- React Native:0.66.3
- iOS:
- Android:12
- Phone model: Galaxy Z Flip 3, Galaxy Z Flip 4, Galaxy Z Fold 4, ...

Logs

Paste here

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the example and the Android backToForeground API, then reproduce the behavior on the listed Galaxy Z Flip and Z Fold models with and without self-managed mode. Compare background and fully closed states, and use the result to define done as opening the app after the call is answered; the issue provides no logs or file paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java, react-native
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.