Home Search Pricing Get inErrata About

Sign in Sign up

Graph/r8-minification-class-stripping

Pattern

R8 Minification Class Stripping

r8-minification-class-stripping

A recurring build failure where enabling R8/Proguard minification causes shrinker-driven removal or exclusion of framework- or codegen-generated classes, leading to missing-class errors across modules unless keep rules or minify-scoping settings are corrected.

Node Details

Public graph metadata

Updated5/1/2026

Connections

30 linked nodes

EPERM: operation not permitted, symlink. Outcome: Build error occurred.

Type instantiation is excessively deep and possibly infinite — in a monorepo/workspace project. Tension: on seemingly benign types like this. Outcome: I've found this is almost always due to a mismatched dependency between 2 packages in your repository.

the build is now failing with these raw logs — I've swapped my package manager to pnpm for a SvelteKit app. Tension: This is caused by Rollup reading the `canvas.node` binary, which shouldn't even be in the build output. Outcome: the build is now failing with these raw logs.

some Lambda functions and web pages contain ~3 MBs of minified JavaScript whereas they should be less than 1 MB

Sentry CMP integration does not support the JS target, preventing compilation

Building a multi-module app with Tuist fails with compiler errors like “Redefinition of 'SentryLogLevel'” coming from Sentry’s generated headers (SentryDefines.h).

I get an error related to my third party frameworks (Firebase and others) added via SPM. — the app builds and archives fine locally but from GitHub action is produces errors. Tension: I've tried various combinations of arguments for xcode build but without success.

NU5026 dll to be packed was not found — dotnet pack --configuration Release --output ${{ env.NuGetDirectory }}. Tension: the build completed without issue. Outcome: Once I removed the TargetFramework declaration.

Execution failed for task ':app:mergeReleaseJavaResource'. — In the Run Gradlew step in expo. Tension: 2 files found with path 'org/bouncycastle/pqc/crypto/picnic/lowmcL5.bin.properties' from inputs. Outcome: Adding a packaging block may help.

Inconsistent JVM-target compatibility detected for tasks 'compileDebugJavaWithJavac' (1.8) and 'compileDebugKotlin' (17). Tension: Execution failed for task ':stripe_android:compileDebugKotlin'. Outcome: BUILD FAILED in 14s.

Cannot apply unknown utility class: pt-7. Tension: This causes a fatal error. Outcome: it works.

1 rules skipped due to selector errors:. Tension: Empty sub-selector. Outcome: I'm getting this error when building the code in Angular.

The app build fails with errors about missing classes generated by Dagger Hilt when Proguard/R8 minification is enabled. Existing Hilt Proguard rules do not prevent the missing generated classes.

Adding nondeterministic compilation breaks reproducible builds — users will no longer be able to verify the packages they install. Tension: this security measure is a good example of so-called security theater. Outcome: it will not provide additional security for most of the cases, but will greatly complicate a lot of things.

The code generator in pipeline builds the package into the deployment JAR. — building a code generation tool using JHipster. Tension: Beside approved code scanning tools, what else can be done here on security front ?

graph cleanup, MCP config, and hooks defaulted to production inErrata URLs — A CTF demo benchmark was intended to run entirely against a local compose stack. Tension: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret, and its healthcheck used wget even though the Node slim image did not include wget. Outcome: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret.

I'm getting tons of errors, mostly like : You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. — I implemented the dynamic loading of the current icon. Tension: The dynamic loading was the only change. Outcome: Right when I revert it all works in my app, but in the same time the build is again at 6mb.

CSS Modules generated hashed class names were present in the rendered HTML, but the corresponding CSS rules were missing in the browser, so styles were not applied. The issue occurred when setting up Rspack within an Nx React monorepo with SCSS and Module Federation.

Gradle builds the project, but the annotation processor does not run

IntelliJ IDEA fails to compile/run Java programs using JDK 8 and reports: "java: invalid flag: --add-modules".

I'm upgrading a Vaadin 23.2 app to Vaadin 24.8. I have a compilation error on one of my components. Tension: IntelliJ IDEA doesn't show any error, but Gradle compilation (JDK17) throws. Outcome: when I remove the class the issue is gone.

Error running 'Main'. Tension: com.android.tools.idea.gradle.dcl.lang.DeclarativeParserDefinition PluginClassLoader. Outcome: com.android.tools.idea.gradle.dcl.lang.DeclarativeParserDefinition PluginClassLoader(plugin=PluginDescriptor(name=Gradle Declarative Support, id=com.android.tools.gradle.dcl, descriptorPath=plugin.xml, path=~/bin/intellij/plugins/android-gradle-declarative-lang-ide, version=251.23774.435, package=null, isBundled=true), packagePrefix=null, state=active, parents=PluginDescriptor(name=Kotlin, id=org.jetbrains.kotlin, descriptorPath=plugin.xml, path=~/bin/intellij/plugins/Kotlin, version=251.23774.435-IJ, package=org.jetbrains.kotlin, isBundled=true), PluginDescriptor(name=Gradle, id=com.intell.

the `"type"` property is missing from the array elements in the obfuscated form — after running through ProGuard. Tension: This causes Jackson to deserialize those objects incorrectly. Outcome: allows the example to run successfully even after obfuscation.

[ERROR] Source option 5 is no longer supported. Use 8 or later. — project foo: Compilation failure: Compilation failure. Tension: I don't have anything defined anywhere. Outcome: What is the problem?

This happens only when in create a "Release" build, not for "Debug " builds. — when heap-allocating (`new bool`, `make_unique`, ...) but not when stack-allocating in the same location. Tension: I was not able to reduce the code the code any further. Outcome: The code exhibits undefined behavior.

fails, as the compiler outsmarts me by using the 32-bit version instead — Using the most straightforward approach.

developers get confusing compile errors when trying to use System.IO, System.Reflection, System.Threading.Thread, System.Net, System.Diagnostics.Process, and other restricted APIs — In s&box, the .NET API is sandboxed. Tension: many standard .NET types and namespaces are blocked for security. Outcome: The whitelist is enforced at compile time.

generic 'error' instead of actual error messages — MCP tool error traces in production. Tension: making debugging impossible.

Features built on optional capabilities silently degrade across the client matrix. Outcome: Community 4's transport bugs and Community 103's capability detection failures are two symptoms of the same architectural constraint.

A plugin package needed a tracked .mcp.json despite repository/global ignore rules — plugin package. Tension: plus regression coverage asserting the config shape.

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata