VSTS生成签名APK安装后仅显示白屏，Xamarin.Android应用运行异常

I'm developing an Android app using Xamarin.Android. When deploying directly to my device via Visual Studio, the app runs perfectly. I can also generate a signed archive locally through Visual Studio and install/run it without issues. However, after configuring a build in VSTS (Azure DevOps) that successfully signs the APK, installing and launching the app only shows a white screen—no error messages are displayed anywhere.

Let’s break down the most likely reasons for this frustrating issue and walk through actionable steps to troubleshoot and fix it:

Possible Causes & Troubleshooting Steps #

1. Validate Build Configuration Parity #

First, make sure your VSTS build uses the exact same build configuration as your working local builds. It’s surprisingly easy to accidentally set VSTS to use a Debug config (which might have missing optimized assets) or a mismatched platform target:

• In your VSTS build definition, double-check the Build Configuration parameter in the Xamarin Android build task—confirm it matches the config you use locally when generating your signed archive (usually Release).

2. Check Resource & Asset Packaging #

VSTS builds sometimes handle resource/asset packaging differently than local Visual Studio builds, leading to missing critical files:

• Verify all your app’s assets (images, fonts, JSON configs, etc.) have the correct Build Action set in your .csproj file (e.g., AndroidResource for drawables, EmbeddedResource for internal files) and that these settings are checked into source control.
• Enable verbose logging in your VSTS build task (look for logging options in the task settings) to scan for warnings about missing resources or merge conflicts—these often fly under the radar but can break your app’s UI loading.

3. ProGuard/R8 Shrinking Misconfiguration #

If you’re using code shrinking (ProGuard or R8) for Release builds, VSTS might apply overly aggressive rules that strip critical app components:

• Ensure your proguard.cfg or r8.cfg file is fully committed to source control and picked up by the VSTS build. Unpushed local changes to these files are a common culprit.
• Add explicit rules to keep core components from being stripped. For example:

  -keep public class com.yournamespace.MainActivity { *; }
  -keep public class com.yournamespace.SplashActivity { *; }
  

• Test temporarily disabling ProGuard/R8 in your VSTS build—if the white screen goes away, you know shrinking is the issue, and you can refine your rules accordingly.

4. Verify Signing Configuration Consistency #

Even if the APK shows as signed successfully, subtle differences in signing setup between local and VSTS can cause issues:

• Confirm the keystore used in VSTS is identical to your local one (same keystore file, alias, keystore password, and key password). A mismatched keystore can interfere with resource access or app identity checks.
• Try switching from APK Signature Scheme v2 to v1 only temporarily in your VSTS signing task—some older devices have compatibility issues with v2 signatures that lead to silent failures.

5. Capture Device Logs with Logcat #

Since there’s no visible error, dig into the device’s logs to find the root cause:

• Connect your device to your computer, open a command line, and run adb logcat *:E to filter for error-level logs.
• Look for exceptions like ClassNotFoundException, ResourceNotFoundException, or initialization failures—these are almost always the reason behind a silent white screen.

6. Check APK Integrity #

Sometimes the APK generated by VSTS gets corrupted during build or publishing:

• Download the APK directly from VSTS and compare its file size to your local signed APK—if there’s a big discrepancy, the build process might be missing files.
• Use the apksigner verify command to confirm the signature is valid, and try installing the APK manually via adb install to see if you get any installation errors that don’t show up in the device’s UI.

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