-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App not Launching or going to Foreground from Background when click on accept action button ( ONLY ANDROID ) #113
Comments
flutter doctor -v
|
your case looks very similar to this #111, have you tried this solution #111 (comment) |
I added the SYSTEM_ALERT_WINDOW permission and added a popup for the user to accept the app overlay permission and this works Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An issue I've encountered with the package. For a clearer understanding, I have attached the relevant code example.
After testing on multiple Android devices, I've observed that when our application is running in the background and a call notification is received, there's a glitch in its behavior. Upon clicking the "accept" button on the call notification, the code responsible for navigating to the call screen is executed. However, this does not bring the application to the foreground. Instead, the application remains in the background.
To ensure that the issue isn't with the callback function, I verified the 'onAcceptCallback'. It appears to be functioning correctly because when I manually bring the application to the foreground after clicking "accept", I can see that it has already navigated to the call screen.
*NOTE: This issue only on android side on ios it works fine
The text was updated successfully, but these errors were encountered: