Skip to content
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

no notification for swapped out app #219

Closed
fangzhzh opened this issue Nov 6, 2018 · 7 comments
Closed

no notification for swapped out app #219

fangzhzh opened this issue Nov 6, 2018 · 7 comments
Assignees

Comments

@fangzhzh
Copy link

fangzhzh commented Nov 6, 2018

Description

Hey Twilio!

Mobile devices not receiving incoming call notifications has definitely been an issue for us at Cradle.

We’ve found a specific case that reliably causes an issue on some phones, Specifically Samsung Galaxy phones and also all the Huawei phones we’ve got. The Google Pixel and any simulator phones don’t experience the issue

When we open the the recent apps list then swipe to kill our app, we will not receive notifications at all.

In the logcat, when the app was killed, we get:

I/ActivityManager: Killing 16379:cradle.android.io.cradle.debug/u0a374 (adj 900): stop cradle.android.io.cradle.debug,from pid 3649
W/BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_RESTARTED dat=package:cradle.android.io.cradle.debug flg=0x10 (has extras) } to android/com.kddi.android.CpaNotiReceiver

From now on, if this user is called, it will show

GCM: broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE flg=0x10000000

This is all using Twilio Voice 2.0.7 (we look forward to the v3 of the SDK to be production ready!!), we also setup the test using the voice-quickstart-android project and had the exact same experience. Kill the app then you stop getting call notifications.

Is this something you’ve experienced or noticed before? Is it something you’ve tested for? Do you have any suggestions or best practice guidelines as to how best use the SDK and reliably receive incoming call notifications?

I searched the error message and got the issues at firebase-quick-android project, but they didn’t help much.

firebase/quickstart-android#89
firebase/quickstart-android#378

Steps to Reproduce

  1. set up this sample project
  2. open recent list, swap the app out
  3. call the device, no FCM notification

Expected Behavior

VoiceActivity should be raised

Actual Behavior

no

Reproduces How Often

100% on some phones

Versions

Android 5, 7, 8

Voice Android SDK

2.0.7

OS Version

Android 5, 7, 8

Device Model

Samsung galaxy s7, Huawei LYO-L02

@kbagchiGWC kbagchiGWC self-assigned this Nov 7, 2018
@kbagchiGWC
Copy link
Contributor

@fangzhzh
I have not faced this issue in our testing. We will test this on our side and get back to you.

@AakashBabu
Copy link

Twilio Android Bug. (We are using GCM)
While making a Call to User, Sometimes On Receiving End, On the below function, Flow is not moving Forward. But the receiver gets the Notification but Not getting Callback on both methodes(onCallInvite & onError).
Voice.handleMessage(context, remoteMessage, new MessageListener() {
@OverRide
public void onCallInvite(CallInvite callInvite) {
Log.v("responce_voice","CallInvite");

}

@Override
public void onError(MessageException messageException) {
    Log.v("responce_voice","CallInvite err");
}

});

@kbagchiGWC
Copy link
Contributor

@AakashBabu What version of the SDK are you using? Can you please share logs?

@kbagchiGWC
Copy link
Contributor

@AakashBabu Can you file a separate issue for this? This seems like a different than the issue this was opened for.

@AakashBabu
Copy link

Twilio SDK : 2.1.0
Android version tested: Lolipop and marshmellow

@gwicks56
Copy link

Did you ever find a solution to this issue? Having the exact same problems with Samsungs for my app.

@kbagchiGWC
Copy link
Contributor

We have updated our quictstart application. Please refer to the latest and let me know if you have additional question.

For now, I am closing this ticket due to inactivity.

Thank you,

-Kumkum

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants