DebugProbesKt.bin gets shipped in release apk
See original GitHub issueNot a big deal, but I am wondering if the Android build process should really add this to every release APK (gets placed into the root folder).
Tested with Android Studio 4.0.1 and 4.2.0 Canary 12 using the latest Kotlin and Coroutines Android plugins/libraries.
As a workaorund it should be safe to use
packagingOptions {
exclude 'DebugProbesKt.bin'
}
for release builds, right?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Android Analysis Report ZALORA_base.apk - Joe Sandbox
Installs a new wake lock (to get activate on phone screen on). Lists and deletes files in the same context. May access the...
Read more >DebugProbes - Kotlin
Debug probes is a dynamic attach mechanism which installs multiple hooks into coroutines machinery. It slows down all coroutine-related code, but in return ......
Read more >Workplace from Meta_v357.0.0.5.115 _apkpure.com.apk
Get your own cloud service or the full version to view all details. ... com.facebook.workcom.facebook.payments.shipping.form. ... DebugProbesKt.bin.
Read more >NET 7 Performance Improvements in .NET MAUI
In the case of a dotnet new maui app: kotlin directory: 386,289 bytes uncompressed, 154,519 bytes compressed; DebugProbesKt.bin : 1,719 ...
Read more >kotlinx.coroutines - android Git repositories
This is a companion version for the Kotlin 1.6.21 release. ... packagingOptions { resources.excludes += "DebugProbesKt.bin" } ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For everyone reading this issue, this was added to the README.
Fixed by providing how-to documentation in 1.4.0