Google Play安装Beta版应用时触发错误代码-505的问题求助
Hey there, let’s figure out why you can’t install both your Production (com.domain.standard) and Development (com.domain.evv) Beta builds side-by-side on the same device—this -505 error is super common in this exact scenario, and I’ve fixed it a few times before. Here’s what’s going on and how to resolve it:
Common Root Causes & Solutions
1. Duplicate sharedUserId in Manifest
Android uses the android:sharedUserId attribute to group apps that need to share data or system permissions. If both your Production and Development builds declare the same sharedUserId in their AndroidManifest.xml, the system treats them as part of the same "app group" and won’t let you install both.
- Check: Open both manifests and look for a line like:
android:sharedUserId="com.yourdomain.app" - Fix: Give your Development build a unique sharedUserId (e.g.,
com.yourdomain.app.dev) or remove the attribute entirely if you don’t need cross-app data sharing between the two versions.
2. Conflicting Component Identifiers
Even with different package names, if certain components (like content providers, broadcast receivers, or services) have identical unique identifiers across both builds, Android will throw the -505 error. The most frequent culprit is duplicate content provider authorities.
- Check: Look for content provider declarations in your manifests. For example, if both have:
android:authorities="com.yourdomain.app.provider" - Fix: Update the authority for your Development build to something unique, like
com.yourdomain.evv.provider. Do the same for any other components that use hardcoded unique IDs (like intent filters with specific actions).
3. Google Play Console Misconfiguration
If you set up both builds as flavors of the same app in the Google Play Console instead of separate app entries, Google Play will treat them as different versions of the same app—so users can only install one at a time.
- Check: Log into the Play Console and verify that
com.domain.standardandcom.domain.evvare listed as two distinct applications, not under the same app’s "Artifact Library" or "Beta" tab. - Fix: If they’re grouped together, create a new separate app entry for the Development build in the Play Console and upload its Beta version there.
Quick Local Test to Narrow Down the Issue
Before troubleshooting Play Console settings, test locally first:
- Build both APKs (or App Bundles) from your project.
- Manually install both on a test device using ADB or Android Studio’s "Run" button.
- If you still get the -505 error, the problem is in your app code/manifest. If local installation works, the issue is in your Google Play Console configuration.
内容的提问来源于stack exchange,提问作者Bryant Makes Programs

