One of receiver_exported or receiver_not_exported should be specified when a receiver isn't being registered exclusively for system broadcasts

Question

One of receiver_exported or receiver_not_exported should be specified when a receiver isn't being registered exclusively for system broadcasts

tuankietcoderr opened this issue 7 months ago · 9 comments

tuankietcoderr commented 7 months ago

Which package/packages do you use?

@stream-io/video-react-sdk
@stream-io/video-react-native-sdk
@stream-io/video-client

Describe the bug
I receive this bug when using Android API level 34 (Android 14)

To Reproduce
Steps to reproduce the behavior:

Go to 'Home screen'
Click on 'Create new meeting'
After video initialized, the error is displayed.

Expected behavior
Video call has to work perfectly as I use on Android API level 31

Screenshots

Version

^0.3.17

Env:

N/A

React / JS client

N/A

React Native

OS: Windows
Device: Android Pixel 4 API 34

Node JS client

v20.11.0

Additional context
N/A

Answer 1 · 2024-02-07T09:40:22.000Z

I can confirm that I experience this as well. In the meantime, I worked around this issue by targeting SDK 33.

Answer 2 · 2024-02-07T09:57:19.000Z

I can confirm that I experience this as well. In the meantime, I worked around this issue by targeting SDK 33.

Is there any alter solution for this? My target customers have to be supported from API 25 to API 34 :(

Answer 3 · 2024-02-07T10:00:22.000Z

I can confirm that I experience this as well. In the meantime, I worked around this issue by targeting SDK 33.

Is there any alter solution for this? My target customers have to be supported from API 25 to API 34 :(

Your customers running API 34 will still be able to run the app targeting API 33 without an issue. It will only start becoming a real problem somewhere in summer/autumn when Google slowly starts requiring new app updates and apps to target API 34.

Answer 4 · 2024-02-07T10:02:13.000Z

I can confirm that I experience this as well. In the meantime, I worked around this issue by targeting SDK 33.

Is there any alter solution for this? My target customers have to be supported from API 25 to API 34 :(

Your customers running API 34 will still be able to run the app targeting API 33 without an issue. It will only start becoming a real problem somewhere in summer/autumn when Google slowly starts requiring new app updates and apps to target API 34.

How about Get stream team? Are they fixing this problem?

Answer 5 · 2024-02-07T14:16:36.000Z

Hi, So to confirm do you use targetSDK 34?

This seems to happen only when targetSDK 33 is used. I believe one of the dependendant libraries we use are still using the old format.

In the meantime please stick to targetSDK 34, there will be atleast this summer that google will force the usage of targetSDK 34, but we will find and resolve this issue asap

Answer 6 · 2024-02-07T14:39:23.000Z

Hi, So to confirm do you use targetSDK 34?

This seems to happen only when targetSDK 34 is used. I belive one of the dependendant libraries we use are still using the old format.

In the meantime please stick to targetSDK 34, there will be atleast 2 years in my experience that google will force the usage of targetSDK 34, but we will find and resolve this issue asap

thank you, in the future there might be sdk 35, 36 and so on. so upgrade your packages and apis are is really essential

Answer 7 · 2024-02-07T14:48:21.000Z

I totally understand the importance. I have filed the issue accordingly.

Answer 8 · 2024-02-16T09:49:23.000Z

I have raised a PR in the react-native-incall-manager library 🤞

Answer 9 · 2024-02-19T10:55:56.000Z

Please update to react-native-incall-manager - 4.2.0

Many thanks for filing the issue!