callkeep icon indicating copy to clipboard operation
callkeep copied to clipboard

crash ios when app is killed

Open ahmedJD opened this issue 4 years ago • 6 comments

after display incomming call the app crash when the app is killed

ahmedJD avatar Jun 11 '21 12:06 ahmedJD

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 avatar Jul 19 '21 11:07 efraespada

@efraespada

  • when i open the app the log show permissions is granted
  • i comment did dipslay incomming call and display incomming call and the app still crash
  • when the app killed i received push notification

ahmedJD avatar Jul 23 '21 09:07 ahmedJD

@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.

efraespada avatar Jul 24 '21 19:07 efraespada

@ahmedJD You can use flutter run --release|--profile, so that you can still be woken up after killing the app on iOS,

cloudwebrtc avatar Jul 25 '21 02:07 cloudwebrtc

Then you can try since the setup method. Check which method is failing.

efraespada avatar Jul 25 '21 03:07 efraespada

@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 -h') for available flutter commands and options.

ahmedJD avatar Aug 24 '21 16:08 ahmedJD