We know that proguard provides retrace function to deobfuscate strack trace. But does Proguard supports the functionality through which logs could be deobfuscated ?
Make sure you are generating mapping.txt file and then you can use retrace as explained at https://www.guardsquare.com/en/products/proguard/manual/retrace
however I don't think proguard offers anything for complete log file
Related
I have a vue 2 application. I setup sentry with official #sentry/vue package.
In some issues I can't get full detailed stack trace.
This issue has a good stack trace. I can click and see the exact line in my code.
But in this issue I can't do it.
I don't understand why In the first case sentry saved a few lines of code from chunk-app-vendors.xxx.js, but it didn't save code in the second issue.
I don't have access to this file, because my application has already been updated.
How can I solve this problem to see more data about errors?
Is it because your project lacks sourcemap, and cannot locate the specific error location? You need to upload the sourcemap.
Sentry doesn't generate and doesn't upload sourcemaps by default.
In particular, the whole process consists of:
generating the sourcemaps
uploading them to Sentry
validating them (on sentry)
I suggest you to read the related section of their documentation.
I am getting following exception when trying to call feature file of another module from different module with logs as,
org.graalvm.polyglot.PolyglotException: TypeError: Access to host class utils.Utils is not allowed or does not exist.
Following is the file which I am trying to run as,
https://github.com/bipin-k/karate-automation/blob/master/sample-automation/src/main/java/sample.feature
https://github.com/bipin-k/karate-automation
karate error description
Please read this answer for hints on how to handle re-use across Java modules: https://stackoverflow.com/a/58339662/143475
Recommendation is to avoid it as far as possible. And things like call read('../../../../core-utilities/src/main/java/java-functions-calls.feature') lead to un-maintainable tests: https://stackoverflow.com/a/54126724/143475
Most likely the problem is because in the project where you make the call - the utils.Utils class is simply not on the Java "classpath". You should probably take the help of someone who knows Java well, or stick to a simpler "single module" Java project.
I am using Jetpack Compose 1.0.0-alpha09 with Kotlin 1.4.21. I use vectorResource to load an ImageVector from resources.
All works fine in the design previews and for debug builds. However, when I build a release build with ProGuard, I get the following exception at runtime:
org.xmlpull.v1.XmlPullParserException: Binary XML file line #1<VectorGraphic> tag requires viewportWidth > 0
at androidx.compose.ui.autofill.AndroidAutofillDebugUtilsKt.vectorResource(AndroidAutofillDebugUtils.kt:142)
at ...
After a long tedious process trying to identify differences between release and debug which may cause this, I have discovered that disabling optimization in ProGuard using -dontoptimize 'solves' this issue.
What exactly causes this discrepancy in behavior? Is this a bug in, Jetpack Compose, ProGuard, or in my configuration of ProGuard?
I'm trying to build my project but I can't.
I get this error:
Error:Cannot run program "C:\tools\jdk8.0.191\bin\java.exe" (in directory "C:\Users\"my user"\AppData\Local\JetBrains\IntelliJIdea2020.1\compile-server"): Malformed argument has embedded quote: -Djava.endorsed.dirs=\"\"
Do anyone know what to do about this? Iøm trying to build in IntelliJ 2020.1
Best Regards
It might be related to more strict command-line processing in JDK on Windows after JDK-8221858 (private) security patch see this comment for details.
Try following workaround: Help -> Edit Custom VM Options action and add the following line at the bottom of the file: -Djdk.lang.Process.allowAmbiguousCommands=true and restart IDE.
Today I cloned the Dojo Boilerplate and I'm running build.sh for the first time.
Messages like "warn(216) dojo/has plugin resource could not be resolved during build-time" are showing up in the console, and I wonder how much these warnings matter. Should I try to resolve them?
There always will be a lot of this kinds of warnings in build report. I seldom find that this will cause issues in your final building.
Don't worry about warning, just go head. Unless you see some errors in the report, you need to fix the errors.
Here is standard response from dojo https://bugs.dojotoolkit.org/ticket/15903
You can use grep to filer out messages starting for ex. from warn or info
src/util/buildscripts/build.sh --profile devel.profile.js | grep -vE "^warn|^info"