Closed mrcse closed 10 months ago
flutter doctor -v
[✓] Flutter (Channel stable, 3.13.6, on macOS 14.0 23A344 darwin-x64, locale en-PK)
• Flutter version 3.13.6 on channel stable at /usr/local/Caskroom/flutter/3.7.0/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision ead455963c (9 days ago), 2023-09-26 18:28:17 -0700
• Engine revision a794cf2681
• Dart version 3.1.3
• DevTools version 2.25.0
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
• Android SDK at /Users/mrcse/Library/Android/sdk
• Platform android-33, build-tools 33.0.1
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 15A240d
• CocoaPods version 1.12.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2022.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
[✓] VS Code (version 1.82.3)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.74.0
[✓] Connected device (3 available)
• Jamshid’s iPhone (mobile) • 00008120-001170143AC0C01E • ios • iOS 17.0.2 21A351
• macOS (desktop) • macos • darwin-x64 • macOS 14.0 23A344 darwin-x64
• Chrome (web) • chrome • web-javascript • Google Chrome 113.0.5672.126
[✓] Network resources
• All expected network resources are available.
• No issues found!
your case looks very similar to this https://github.com/ConnectyCube/connectycube-flutter-call-kit/issues/111, have you tried this solution https://github.com/ConnectyCube/connectycube-flutter-call-kit/issues/111#issuecomment-1727946091
I added the SYSTEM_ALERT_WINDOW permission and added a popup for the user to accept the app overlay permission and this works Thanks
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