Proguard rules fix to include everything below org.bouncycastle.jcajce.provider.asymmetric #4537
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.
Description
Update Proguard rules to fix SSH connection problems in recent release builds.
Source was from this
ClassNotFoundExceptionwhen attempting to create new connection, usinged25519SSH key in 3.11.2 release builds.Probably some changes to the BouncyCastle library we didn't notice, while we removed system's built-in
BCprovider, causing the problem.Issue tracker
Automatic tests
Manual tests
Done
Device: Fairphone 5
OS: LineageOS 23.0 (Android 16)
SftpConnectDialog should successfully save a new SSH connection, and hence be able to connect to the SSH server.
Build tasks success
Successfully running following tasks on local:
./gradlew assembledebug./gradlew spotlessCheck