Open ahmedJD opened 3 years ago
Have you done this? @ahmedJD
Ensure the required permissions are granted before start testing callkeep
Comment/remove the callkeep usage in different point to notice where the crash is happening
Try to show a notification for ensure the incoming call should appear (sometimes I didn't receive the FCM data)
@efraespada
@ahmedJD
If your iOS app is terminated while developing, you can't start again normally (as Android), you need to fire the app with the flutter
command.
It happens with any app, even if you don't use callkeep
.
It doesn't happen with release apps. You can check it by uploading your release app to TestFlight.
@ahmedJD You can use flutter run --release|--profile
, so that you can still be woken up after killing the app on iOS,
Then you can try since the setup method. Check which method is failing.
@cloudwebrtc @efraespada when i use --release i can't see logs and when i use --profile logs disappear after killing the app. i can't use them together : Only one of --debug, --profile, --jit-release, or --release can be specified.
Run 'flutter -h' (or 'flutter
after display incomming call the app crash when the app is killed