Efra Espada

I just realized this exception only happens when I try to do login when I've previously made a login in another device in the same app/project with the same Google...

@cloudwebrtc I'm working in a [PR](https://github.com/flutter-webrtc/callkeep/pull/86) for providing some documentation to the community. If you agree of course. #86 I've integrated Callkeep in my application and I think I have...

@ahmedJD you could be trying to use some methods (related with the permissions) that could need an activity which is not ready yet. What I do in those cases is...

@ahmedJD I supposed it was happened in Android because I deal with this problem. Have you any trace of the iOS error?

@ahmedJD I'll do this: - 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...

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

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

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

No, you must control it by yourself. I start calls with FCM data push messages (the app can be closed) and end them with Firestore Database (app is open and...

No, when the app is terminated or backgrounded (even iOS) your listeners will stop receiving changes. Use push data messages to do that.