Open b055man opened 4 years ago
@dariuszseweryn could it be from RxAndroidBle or is it from MBA?
Nothing in the RxAndroidBle
is directly referencing sun.misc.Unsafe
class. There are some reflection use-cases that workaround connection issues on older Android versions. They can be viewed here. There is nothing else that I know of.
I think this is exactly related to reflections. Here is a snippet from the pre-launch report from Play Console:
The pre-launch report is from a full app I'm working on, so it is possible that not all of these apply to flutter_ble, but I believe at least some of them do, as they resemble the warnings I observe in the console when there are BLE operations happening.
Any chance to have an SDK-dependant implementation of things in the future that do not use hidden APIs on modern SDKs?
[EDIT] Here's Google approach on this matter - and it looks like this behaviour might be observed on Android 9 onwards: https://developer.android.com/distribute/best-practices/develop/restrictions-non-sdk-interfaces Also, it looks like there are some further changes on the way for Android 11: https://developer.android.com/preview/non-sdk-11
When using the plugin on Android 10, there are number of warnings issued due to using non-public APIs.
Are there any plans on resolving this (Google at some point may become more restrictive..)?