Closed taekeun-two closed 4 months ago
Initially I thought that it's callkeep's code, but finally I found that the error comes from react-native-incall-manager
. I'm so sorry for wrong error report.
In react-native-incall-manger
latest v4.2.0
, this problem was fixed.
https://github.com/react-native-webrtc/react-native-incall-manager/releases/tag/4.2.0
Support Android 14 receiver changes
fix(android): specify export mode on BroadcastReceivers ( Santhosh Vaiyapuri 2024-02-16 10:41:22 +0100)
Bug report
[ ] I've checked the example to reproduce the issue.
Reproduced on:
Description
After upgrading
0.72.X
and Expo49
,0.73.X
and Expo50
,the following error occurs whenever receiving call in Android 14 platform phone.
References
Registering receivers with intention using the
RECEIVER_EXPORTED
/RECEIVER_NOT_EXPORTED
flag was introduced as part of Android 13 and is now a requirement for apps running on Android 14 or higher (U+). It seems that it should be applied for callkeep's registering receivers.Steps to Reproduce
Versions
Logs