Repository navigation
Document async bridge Job rule in existing ProGuard guidance - #26
Open
piercifani wants to merge 1 commit into
Open
piercifani wants to merge 1 commit into
piercifani wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
piercifani
force-pushed
the
codex/document-async-bridge-job
branch
from
October 8, 2026 14:02
b8b6e3f to
99ca559
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the async-bridge
kotlinx.coroutines.Jobkeep rule directly to the existingAndroid/app/proguard-rules.proguidance in Project Structure.Explain why R8 renaming can break native JNI method lookups after upgrading to Skip 1.9.13, why non-minified debug builds miss the issue, and where existing or separately maintained Android apps should add the rule.
Companion generator fix: skiptools/skipstone#294. The upgrade note belongs here alongside the existing R8 guidance; the generator PR no longer adds a separate README section.
Validation: production site build and internal link checks passed;
git diff --checkpassed.