One of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED should be specified when a receiver isn't being registered exclusively

[namp]

On android 14, I received this error. It is necessary to specify one of RECEIVER_EXPORTED or RECEIVER_NOT_EXPORTED when the receiver is not registered specifically for system broadcasts in the package at android.content.ContextWrapper.registerReceiver, but I can't fix it because of the mail3 side library, I wonder if tuya has a beta update,...update for this or not?
Bug full :
at android.os.Parcel.createExceptionOrNull(Parcel.java:3057)
at android.os.Parcel.createException(Parcel.java:3041)
at android.os.Parcel.readException(Parcel.java:3024)
at android.os.Parcel.readException(Parcel.java:2966)
at android.app.IActivityManager$Stub$Proxy.registerReceiverWithFeature(IActivityManager.java:5684)
at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1852)
at android.app.ContextImpl.registerReceiver(ContextImpl.java:1792)
at android.app.ContextImpl.registerReceiver(ContextImpl.java:1780)
at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:755)
at com.thingclips.sdk.mqtt.qqdqqpd.start(AlarmPingSender.java:4)
at com.thingclips.smart.mqttclient.mqttv3.internal.ClientState.connected(ClientState.java:4)
at com.thingclips.smart.mqttclient.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:57)
at com.thingclips.smart.mqttclient.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:38)
at java.lang.Thread.run(Thread.java:1012)
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.am.ActivityManagerService.registerReceiverWithFeature(ActivityManagerService.java:13927)
at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:2570)
at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2720)
at android.os.Binder.execTransactInternal(Binder.java:1339)
at android.os.Binder.execTransact(Binder.java:1275)

[admin]

Hello, the targetSdk version we currently support is 33, and we recommend that you continue to use targetSdk 33.
Our comprehensive internal adaptation to version 34 is already in the planning stage, please wait for our update release.
If you have a compelling reason to upgrade to 34, please reply to us.

[namp]

Thank you admin. Hopefully tuya will fix this bug as soon as possible.

[ahmedabouelkher]

The issue still exists on android 34 and it is required by the play store to compile for android 34.

https://support.google.com/googleplay/a ... 6878?hl=en

[admin]

Please use our latest version, which has fixed this issue
https://developer.tuya.com/en/docs/app- ... 9nt96cw0uj

[Glenn]

The current version of the Commercial Lock SDK (com.thingclips.smart:thingsmartlocksdk:1.4.0-lock) also still has that issue. Is there any plan to get it fixed in the near future?

[Ronbin]

Hello, I would like to recommend you to integrate this Smart Lock SDK（https://developer.tuya.com/en/docs/app- ... vl28puletn）.