Failure to generate keystore

[Ben-ADFA]

Ref. 2564

On Telegram, Anil Rauniyar has provided logs linked to failed keystore generation:
https://t.me/CodeOnTheGoDiscussions/1132
https://t.me/CodeOnTheGoDiscussions/1136

I've pasted the logs into the .txt file attached here.
The user is running version 26.03 with a custom Kotlin project on an OPPO smartphone with Android 11.

failedkeystore.txt

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

⚠️ Possible Duplicate Issue

• project could not be initialized #564

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[hal-eisen-adfa]

According to Gemini:

It looks like you're encountering a classic compatibility issue related to how modern Android versions (specifically Android 9.0/API 28 and above) handle cryptography.

What’s happening?

The error java.security.NoSuchAlgorithmException: The BC provider no longer provides an implementation for KeyPairGenerator.RSA occurs because Google deprecated and eventually removed the ability to explicitly request the Bouncy Castle (BC) provider for certain cryptographic algorithms.

In the past, developers often did this:
KeyPairGenerator.getInstance("RSA", "BC");

On newer Android versions, this call fails because the system wants you to use the default Android OpenSSL (Conscrypt) provider instead of forcing the Bouncy Castle implementation.

---

How to Fix It

If you are the developer of the Code On The Go project or have access to the source code, you need to change how the KeyPairGenerator is initialized in your ToolsManager class.

1. Remove the Provider String (Recommended)

The most robust fix is to let the system decide which provider to use. Most modern environments will default to the most secure/performant one.

Change this:

// This likely causes the crash
KeyPairGenerator keyPairGenerator = KeyPairGenerator.getInstance("RSA", "BC");

To this:

// This allows the system to use the default provider (AndroidOpenSSL)
KeyPairGenerator keyPairGenerator = KeyPairGenerator.getInstance("RSA");

2. Update the Algorithm Name

If you are generating keys for the Android KeyStore specifically, ensure you aren't manually injecting the BC provider into your logic. If the code is trying to find a specific implementation that was removed, the "providerless" call above is the official Google recommendation.

---

Why did this change?

Google made this change to improve security and performance. The version of Bouncy Castle bundled with Android was often outdated or less optimized than the specialized Conscrypt (OpenSSL-based) provider that Android uses now. By forcing developers away from the "BC" string, they ensure apps use the hardware-accelerated, up-to-date system defaults.

If you are just a user of Code On The Go:

Since the stack trace points to com.itsaky.androidide, this is an internal issue within the app's code.

• Check for Updates: See if there is a newer version of Code On The Go available, as the developers may have already patched this for Android 9+.
• Report the Bug: If you're on the latest version, you might want to share this stack trace with the developer on their GitHub repository.

[hal-eisen-adfa]

We need to change our code