question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

backToForeground doesn't work on Android 9.

See original GitHub issue

Bug report

  • I’ve checked the example to reproduce the issue.

  • Reproduced on:

  • Android

  • iOS

Description

Hello, I’m having a problem. Right know I’m testing the new method called backToForeground, it works perfectly on Android 7 and 8, but now Im testing on Android 9 (Emulated on Android Student) and the app is not waking up. There is any way to fix this?

Steps to Reproduce

Versions

- Callkeep: 3.0.15
- React Native: 0.61.5
- iOS: 
- Android: API 29 (Android 9)
- Phone model: Pixel Pixel 2 (Emulated)

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:8
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

9reactions
maitzethcommented, Jun 30, 2020

@manuquentin I managed to work adding this permission on the Manifest.

<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>

Before that I was not able to make it work in Android 9 and 10

2reactions
manuquentincommented, Aug 12, 2020

We’ve experienced the same issue on a Samsung Galaxy A5 (2016). It appears that backToForeground works as expected (when calling it in a AppState.addEventListener('change', ...) the app comes on foreground).

But Samsung have a fork of ConnectionService that prevents a lot of things… we’ve recently noticed that we can’t trigger clicks in the Samsung ConnectionService UI with calls to adb shell input keyevent ... in our functional tests (calls that works on Pixel devices). I think Samsung has forbidden applications to be reordered above ConnectionService UI …

We’ve try to display a local notification, so the user will click on it and display the app, but Android displays it as a small icon…

We’ll continue our work on #251 to work around this issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Bring app back to foreground from code doesn't work on ...
The thing is, my code works on Android 11 and before, but on Android 12 & 13 the notification click is received by...
Read more >
Restrictions on starting activities from the background
From this screen, the user can control their notification preferences. Exceptions to the restriction. Apps running on Android 10 or higher can start...
Read more >
react-native-incoming-call - NPM Package Overview - Socket
Only for Android since iOS we have VoIP. ... which contains some bugs that I don't have much time to fix. ... Incoming...
Read more >
Galaxy watch 4 bringing application back to foreground ...
After porting Android application that previously ran on Wear OS to Galaxy ... In Galaxy watch 4 it doesn't work (probably due to...
Read more >
3CX App for Android Build History
Fixed incoming calls not dropped correctly: partial fix applied – full fix requires v16 Update 3 PBX. Fixed stuck call when app drops...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found