Call UI not visible on android when answered from push notification in killed state

[voxeet]

Call UI not visible on android when answered from push notification in killed state

[codlab]

This issue is related to the react native package, can you test using the latest commit in the react-native repository
?

npm install --save git://github.com/voxeet/voxeet-uxkit-reactnative.git#5fc6ac4f0a642eaf5af7557d4b7fdb60965c43ba

[codlab]

can you provide logs from add logcat as well?

[tuneerclixlogix]

@codlab With this repo i am facing issues while initializing

[codlab]

The new commit fixes this crash when running the app npm install --save git://github.com/voxeet/voxeet-uxkit-reactnative.git#9ed0cf424ce065121dc7c304dbc1de29004235ca

[tuneerclixlogix]

@codlab With this if I am starting the conference then also the UI doesn't shows up though i receive the call at other end and when i answered i can hear the voice . Also I am not receiving push notifications with this.
I am attaching the logs while starting the conference
logs.txt

[tuneerclixlogix]

Seems like that was something wrong from my side as i sent the third parameter as true while initializing. Now, I have removed the third parameter and when i answer the call from killed state still the call UI is not shown.
Logs for that are
logs.txt

[tuneerclixlogix]

I have noticed that, if I am receiving call from other device without making the call from my side even once since the app is opened then the UI is not shown either the app was in foreground or background or killed .
If i start the conference the call UI is shown now i don't close the app and if someone else calls me and i answer then the UI is shown.

[codlab]

ok so you mean that with this version, you don't have any regression but the UI is not shown when accepting calls from killed state. I'll check this today using the latest version

In the meantime, could you forward me logs from your device since the above one was using the initialize(..., true) which was hiding the overlay completely (regardless of the type of answer)

[tuneerclixlogix]

Seems like that was something wrong from my side as i sent the third parameter as true while initializing. Now, I have removed the third parameter and when i answer the call from killed state still the call UI is not shown.
Logs for that are
logs.txt

Yes @codlab , the log file in this comment is without the 3rd parameter in initialize method.

[codlab]

the latest develop branch fixes the issue

[tuneerclixlogix]

@codlab I can see there is only one branch for this repo i.e. master

[tuneerclixlogix]

@codlab I see you are talking about the develop branch of another repository https://github.com/voxeet/voxeet-uxkit-reactnative/tree/develop . So my question is the changes that you suggested we used in AndroidManifest file with this repository for the push notifications issue , will those work with the other repository also ?

[codlab]

the @voxeet/react-native-voxeet-firebase is only here to provide Firebase support to send voxeet's push notification to the SDK. It does not manage how the push notification are displayed or handled that's why for anything related to how it reacts, it depends on the https://github.com/voxeet/voxeet-uxkit-reactnative repository 👍

The modification suggested in this repository are only here to make it possible to forward "non voxeet" push notification to other (declared) voxeet's push notification MessagingService receivers

... because Firebase teams found it ok to make only the first registered MessagingService registered to be able to handle FCM

[tuneerclixlogix]

@codlab Can you mention the steps to install from the develop branch ?
I tried with yarn add @voxeet/react-native-voxeet-conferencekit#develop but i am getting the error while building

Also i installed with version 0.2.11-beta13 but with this i am getting the same error as we got before initialize got 5 arguments, expected 4 .

[tuneerclixlogix]

@codlab Is there anything i can do to resolve this ? I have this package version installed "@voxeet/react-native-voxeet-firebase": "^2.0.0"

[codlab]

If you installed the repo using the github's develop branch, you will need to reinstall it after you installed a package the regular way (yarn and npm reset the state of git:// project)

can you test again with the npm/yarn install of the react-native-voxeet-conferencekit's repository?

Regarding the dependency issue, it's due to binary sunsetting the hosting service. We are preparing the hosting of the uxkit packages somewhere else but in the meantime, you can use the following android/build.gradle modification:

allprojects {
    repositories {
        maven { url "https://dl.bintray.com/voxeet/maven/" }
        ...
    }
}

[tuneerclixlogix]

@codlab I followed the follow commands
yarn add @voxeet/react-native-voxeet-conferencekit#develop
yarn add @voxeet/react-native-voxeet-firebase
Added maven { url "https://dl.bintray.com/voxeet/maven/" } in build.gradle
Then i got the error of multiple classes used as i was using the following meta tags in AndroidManifest.xml

<meta-data
            android:name="voxeet_incoming_class"
            android:value="com.voxeet.notification.RNIncomingCallActivity" />
 <meta-data
            android:name="voxeet_incoming_accepted_class"
            android:value="com.app.trueflutterdating.MainActivity" />

I think you guys might have included this in the package
Now i am facing this error

[codlab]

You can follow the new readme, the package has been changed
https://github.com/voxeet/voxeet-uxkit-reactnative/tree/develop#android

There's a change I need to propagate due to a typo in the package name for the deprecated ones.

Note that you should remove the meta data since they are being handled automatically in the AndroidManifest.xml (the only one interesting is the voxeet_incoming_accepted_class but in some cases, it will be handled automatically)

[codlab]

You can find the mentioned fix in the latest develop commit

[tuneerclixlogix]

@codlab Yes it worked after that but still the UI is not coming up on android with the develop branch.

[tuneerclixlogix]

Here is the log file when i receive and answer the call, I am not receiving push notifications when the app is killed
logsvoxeet.txt

[codlab]

Issue fixed which was in the react-native-voxeet-conferencekit repository, please update with the latest develop commit + make sure the MainActivity's launchMode is set to singleTask

it should be working as expected 👍

[tuneerclixlogix]

Yes @codlab the MainActivity's launchMode is set to singleTask but there is a crash while answering from killed state, i have reported this in the another thread comments here
#6 (comment)