react-native-callkeep icon indicating copy to clipboard operation
react-native-callkeep copied to clipboard

Package androidx.localbroadcastmanager.content does not exist

Open alexanderoskin opened this issue 2 years ago • 5 comments

Bug report

  • [ ] I've checked the example to reproduce the issue.

  • Reproduced on:

  • [x] Android

  • [ ] iOS

Description

Package androidx.localbroadcastmanager.content does not exist error in VoiceConnection.java:27.

Steps to Reproduce

Install latest Callkeep and try to build project for Android with the latest React Native.

Versions

- Callkeep: 4.3.3
- React Native: 0.69.1

Logs

/node_modules/react-native-callkeep/android/src/main/java/io/wazo/callkeep/VoiceConnection.java:27: error: package androidx.localbroadcastmanager.content does not exist
import androidx.localbroadcastmanager.content.LocalBroadcastManager;
                                             ^

alexanderoskin avatar Jul 07 '22 08:07 alexanderoskin

Hey, i have been facing a similar issue and i found out that google has split the v4 library into multiple packages :

Note: Prior to Support Library revision 24.2.0, there was a single v4 support library. That library was divided into multiple modules to improve efficiency. For backwards compatibility, if you list support-v4 in your Gradle script, your app will include all of the v4 modules. However, to reduce app size, we recommend that you just list the specific modules your app needs.

hence we need to add explicitly mention androidx.localbroadcastmanager:localbroadcastmanager:1.1.0 dependency.

i wanted to create PR for the same but dont have push rights, if someone can help me with that, it will be great.

Till then i have created a fork with fix here - https://github.com/ohheyitskartik/react-native-callkeep-with-broadcast-manager

ohheyitskartik avatar Jul 09 '22 10:07 ohheyitskartik

Hello @ohheyitskartik, everyone have the right to open a PR. I don't understand why you said that. Do you have a message for this issue? Sylvain

sboily avatar Jul 09 '22 12:07 sboily

@sboily, my bad i just cloned the repo & didn't fork it hence i was not able to select my branch for a PR, i have just raised one #596

ohheyitskartik avatar Jul 09 '22 13:07 ohheyitskartik

@alexanderoskin that work, open node_modules/react-native-callkeep/android/build.graldew add :
implementation "androidx.localbroadcastmanager:localbroadcastmanager:1.1.0" run npx patch-package react-native-callkeep

NguyenVanVietPoLy avatar Jul 27 '22 08:07 NguyenVanVietPoLy

how can I fix this error so that I don't have to modify the plugin files every time?

w4ugit avatar Sep 09 '22 11:09 w4ugit

When this bug will be fixed?

whoiswentz avatar Sep 27 '22 22:09 whoiswentz

Facing the same issue

I have to update build.gradle at following path.

/node_modules/react-native-callkeep/android/build.gradle

I have attached gradle file as build.txt due to github security.

image build.txt

chiragpurohit71085 avatar Sep 28 '22 14:09 chiragpurohit71085

"react-native": "0.70.0", "react-native-callkeep": "^4.3.3",

same issue

*Update

Fix merged to master but not released yet

SoftermiiMK avatar Oct 17 '22 11:10 SoftermiiMK

waiting for the fix to be released

Sheharyar566 avatar Oct 31 '22 12:10 Sheharyar566

@manuquentin, can you update the package on https://www.npmjs.com/package/react-native-callkeep??

pierguinzani avatar Nov 04 '22 12:11 pierguinzani

package need to be released new version, although it should be automated

pantomath91 avatar Nov 07 '22 18:11 pantomath91

Same issue for me

ashirkhan94 avatar Nov 08 '22 07:11 ashirkhan94

any update on this issue ?

GittyAjay avatar Nov 16 '22 05:11 GittyAjay

Until a new version is released you can change in your package.json file

"react-native-callkeep": "4.3.3",

to

"react-native-callkeep": "git+https://github.com/react-native-webrtc/react-native-callkeep#4b1fa98a685f6502d151875138b7c81baf1ec680",

to get the fix right away.

mstadius avatar Nov 17 '22 10:11 mstadius

Any update

ashirkhan94 avatar Nov 21 '22 09:11 ashirkhan94

is this released yet? and if it's not is there any workarounds to use this fix?

alaaamady avatar Jan 16 '23 15:01 alaaamady

I think this is fixed with 4.3.4 released in commit 054ece7

Baloo1 avatar Feb 22 '23 13:02 Baloo1