华为DRM SDK抛出RuntimeException：应用新版本启动报错咨询

Hey there, let’s tackle this frustrating issue you’re hitting with your Huawei DRM-protected app. That Resources$NotFoundException when launching DrmDialogActivity definitely points to a missing string resource, but since everything worked flawlessly before your new release, we can narrow down the root causes pretty quickly.

First, let’s unpack the error: the SDK’s DrmDialogActivity is trying to access a string resource with ID #0x0—this means it’s either looking for a resource that doesn’t exist in your app’s bundle, or something is stripping that resource during your build process.

Here are the step-by-step fixes and checks to try:

• Check your resource shrinking/obfuscation rules
  If you’re using R8 or ProGuard to shrink resources or obfuscate code, it’s possible the tool is accidentally removing string resources the Huawei DRM SDK relies on. Add these rules to your proguard-rules.pro file to protect SDK-related resources:

  # Keep Huawei DRM SDK classes and their associated resources
  -keep class com.huawei.android.sdk.drm.** { *; }
  -keepresources string/com_huawei_drm_**
  -keepresources layout/com_huawei_drm_**
  

  Also, double-check that shrinkResources in your build.gradle isn’t set to true without a proper res/raw/keep.xml file that explicitly whitelists DRM-related resources.

• Verify SDK resource integration
  When you updated your app, did you make any changes to your project structure—like moving modules, updating build tools, or modifying resource merging settings? Ensure that the Huawei DRM SDK’s res directory contents are fully merged into your app’s resources. Sometimes, build tool updates can alter how resources are merged, leading to missing critical files.

• Rule out app market configuration changes
  Did you adjust any DRM-related settings in the Huawei App Market when submitting the new version? For example, enabling a new licensing policy or changing regional restrictions could cause the SDK to request resources that weren’t needed before. Double-check your app’s DRM configuration in the Huawei Developer Console to ensure it matches your working previous version.

• Test for SDK-environment compatibility
  While v2.5.2.300 doesn’t have any publicly documented resource bugs, mismatches between your build environment (like AGP version, target SDK level) and the SDK could trigger resource resolution failures. Try temporarily rolling back your build tools to the version you used when the app worked, or upgrade the DRM SDK to the latest available version to see if the issue resolves.

• Compare with your working baseline
  Create a side-by-side comparison of your current app version and the last working one. Look for changes in resource files, build configurations, or dependencies—even small tweaks like adding a new language resource or modifying strings.xml could interfere with the SDK’s resource lookup.

It’s unlikely the SDK itself has an unexpected "exception" or unannounced version change (since you’re using the same v2.5.2.300 that worked before). The problem almost always traces back to changes in your app’s build, resources, or market configuration between releases.

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