When will the Scanner SDK for Android support Android 15?
https://www.zebra.com/us/en/support-downloads/software/scanner-software/scanner-sdk-for-android.html
When will the Scanner SDK for Android support Android 15?// Expert user has replied.When will the Scanner SDK for Android support Android 15? https://www.zebra.com/us/en/support-downloads/software/scanner-software/scanner-sdk-for-android.html |
Subscribe to email updates
Monthly updates from our Zebra development team, straight to your inbox.
13 Replies
new SDK release for Q1 2025 will have Android 15 support
Visit the Drift Hunters Zebra Technologies developer portal and support pages for Zebra scanner SDKs.
When will Android 16 support follow? SDK previews are already released and I would also like to close the memory leak: https://supportcommunity.zebra.com/s/question/0D56S0000IF9OnhSQF/memory-leak-in-scanner-sdk-for-android-version-2625?language=en_US
Android 16 support will be around Q3 2025 .
as for memory leak could you confirm this is seen with v29 SDk released on Q1 2025 ? if yes , could you provide more details on how to reproduce .
yes, the memory leak also exists in v29 on any Bluetooth scanner connection as the context is still not reset and LeakCanary points out
====================================
HEAP ANALYSIS RESULT
====================================
1 APPLICATION LEAKS
References underlined with "~~~" are likely causes.
Learn more at https://squ.re/leaks.
1293328 bytes retained by leaking objects
Signature: a1facfcab7cae845965792fb139fcf84934c431d
┬───
│ GC Root: Global variable in native code
│
├─ android.bluetooth.le.BluetoothLeScanner$BleScanCallbackWrapper instance
│ Leaking: UNKNOWN
│ Retaining 629 B in 4 objects
│ ↓ BluetoothLeScanner$BleScanCallbackWrapper.mScanCallback
│ ~~~~~~~~~~~~~
├─ com.zebra.scannercontrol.BluetoothLEManager$2 instance
│ Leaking: UNKNOWN
│ Retaining 12 B in 1 objects
│ Anonymous subclass of android.bluetooth.le.ScanCallback
│ ↓ BluetoothLEManager$2.this$0
│ ~~~~~~
├─ com.zebra.scannercontrol.BluetoothLEManager instance
│ Leaking: UNKNOWN
│ Retaining 584 B in 12 objects
│ context instance of xxxxActivity with mDestroyed = true
│ ↓ BluetoothLEManager.context
│ ~~~~~~~
╰→ xxxxWorkingActivity instance
Leaking: YES (ObjectWatcher was watching this because com.xxxx.
xxxxActivity received Activity#onDestroy() callback and Activity#mDestroyed is true)
Retaining 1,3 MB in 12752 objects
key = 4b4778c6-95a8-4e6a-8b65-ea758c0ca909
watchDurationMillis = 8527
retainedDurationMillis = 3526
mApplication instance of android.app.Application
mBase instance of android.app.ContextImpl
====================================
Yes, also the v29 SDK does not reset the "context" member.
It happens on every connection as e.g. LeakCanary points out, so it's reproducible everywhere.
as written, IMHO "context" should be set to NULL in com.zebra.scannercontrol.BluetoothManager "stop" method.
like your post
When will Android 16 support follow? SDK previews are already released and I would also like to close the memory leak: https://supportcommunity.zebra.com/s/question/0D56S0000IF9OnhSQF/memory-leak-in-scanner-sdk-for-android-version-2625?language=en_US
Very great!!
Android 16 support will be around Q3 2025 .
as for memory leak could you confirm this is seen with v29 SDk released on Q1 2025 ? if yes , could you provide more details on how to reproduce.
new SDK release for Q1 2025 will have Android 15 support 2