Android：多包名应用代码同步与跨模块启动Activity问题求助

Hey there, let’s break down your problems step by step—this is a super common scenario when managing parallel Android apps, so I’ve got some actionable solutions for you:

The root issue here is duplicate code with differing package names. The cleanest long-term fix is to extract shared logic into a library module:

• Move all core functionality (business logic, custom views, utility classes) out of X’s app module into a new Android Library module.
• Keep only package-specific code in X and Y’s app modules: things like the Application class, Manifest files, entry Activities, and any UI that’s unique to each app.
• Now, both X and Y depend on this shared library. When you make improvements to X, you can commit those changes directly to the library module—Y will pick them up automatically without any import conflicts.

If you can’t refactor into a library right now, use Git tools to automate package name replacement when syncing changes:

• Use git cherry-pick to apply specific commits from X to Y.
• After cherry-picking, run a batch replace command to swap X’s package name with Y’s. For example, in Linux/macOS:

  sed -i '' 's/com.original.x.package/com.new.y.package/g' app/src/main/java/**/*.java
  

• On Windows, you can use PowerShell’s Get-ChildItem + Replace or Android Studio’s "Find in Path" with regex to bulk-update imports.

Cross-app Activity launch requires explicit intent setup and proper manifest configuration:

Step 1: Configure X’s XActivity #

Make sure XActivity is exported and has a clear component name in X’s Manifest:

<activity
    android:name=".XActivity"
    android:exported="true"> <!-- Required for Android 12+ -->
    <!-- Add intent filters if you want implicit launch, but explicit is safer here -->
</activity>

Step 2: Launch from Y’s YActivity #

Use an explicit Intent with ComponentName to target X’s Activity directly:

// In YActivity.java
Intent launchXIntent = new Intent();
// Replace with X's actual package name and XActivity's full class name
ComponentName xComponent = new ComponentName("com.x.package", "com.x.package.XActivity");
launchXIntent.setComponent(xComponent);

// Optional: Pass data to XActivity
launchXIntent.putExtra("KEY_DATA", "Hello from Y!");

// Check if the intent is resolvable to avoid crashes
if (getPackageManager().resolveActivity(launchXIntent, 0) != null) {
    startActivity(launchXIntent);
} else {
    // Handle case where X isn't installed
    Toast.makeText(this, "App X not found", Toast.LENGTH_SHORT).show();
}

Step 3: Add Queries for Android 11+ #

On Android 11 and above, Y needs to declare that it interacts with X in its Manifest:

<queries>
    <package android:name="com.x.package" />
</queries>

Pro Tip: Avoid Hardcoding Package Names #

If both modules are in the same project, define X’s package name as a build config field in Y’s build.gradle:

// In Y's app/build.gradle
android {
    defaultConfig {
        buildConfigField "String", "X_APP_PACKAGE", "\"com.x.package\""
        buildConfigField "String", "X_ACTIVITY_CLASS", "\"com.x.package.XActivity\""
    }
}

Then use it in code:

ComponentName xComponent = new ComponentName(BuildConfig.X_APP_PACKAGE, BuildConfig.X_ACTIVITY_CLASS);

If you don’t strictly need two separate app modules, use Android’s product flavors to create X and Y as variants of a single module:

// In your app/build.gradle
android {
    productFlavors {
        appX {
            applicationId "com.x.package"
            // Add flavor-specific resources/manifest tweaks if needed
        }
        appY {
            applicationId "com.y.package"
        }
    }
}

This way, you maintain one codebase, generate two apps with different package names, and sync changes automatically without any import headaches.

内容的提问来源于stack exchange，提问作者enjektor0