-
Android Native SDK API Call Auto-Logging
Native SDK for Android currently supports manual instrumentation for logging each connection (see URL). The desired feature is automated logging of common connection types. Sample Code - Android Manual Logging Connections: https://github.com/acous...1
-
iOS Native SDK API Call Request Body Capture
Native SDK for iOS captures responsebody but not requestbody. Requestbody is needed as well to be able to determine what's passed during a request. -
Crash Symbolication - Human Readable Crash Reports
Enable Tealeaf to support the upload of ProGuard files, LLVM debug symbol maps (dSYMs), and source maps to show human readable stack traces with methods, file paths, and line numbers for JavaScript and native errors.0
-
Full Support for SwiftUI for native iOS
Native Tealeaf SDK for iOS doesn't support SwiftUI. SwiftUI was released on September, 2019. There is no reason to not have support yet. Most taps are not recorded using the current SDK. Capture is pretty much useless. -
android.widget.Gallery is not supported by Tealeaf Server
android.widget.Gallery is not supported by Tealeaf Server, as we using that widget in our application to show the list in the Gallery format1 Will not implement
-
Support iPadOS
Since June of 2019, responsible iOS developers have been updating their code to work on iPadOS. If IBM isn't staying current with announced changes to the Apple and Android ecosystems, clients using their products are at risk of crashing or reject...0 Under consideration
-
Capture the icons/images from the Custom Font File
Capture the icons/images from the Custom Font File with unicodes in the Replay Server. Instead of images, we can use font files to display the icons in the device and that should be reflecedin the replay server