tencent cloud

All product documents
Tencent Cloud Super App as a Service
DocumentationTencent Cloud Super App as a ServiceGuidelines for Code IntegrationAndroidAndroid SDK DescriptionSDK Integration FAQs
SDK Integration FAQs
Download PDF
Last updated: 2025-02-28 19:47:40
SDK Integration FAQs
Last updated: 2025-02-28 19:47:40
Download PDF

When integrating the mini program SDK and compiling the project, you might encounter the following AAPT error:

  AAPT: error: attribute android:requestLegacyExternalStorage not found.
Solution:
Add the following configuration under the <application> tag in AndroidManifest.xml :
&lt;application
    android:theme="@style/AppTheme"
    tools:replace="android:icon"
      tools:remove="android:requestLegacyExternalStorage">
 /application>

When integrating the mini program SDK and compiling the project, you might see a "Duplicate class android.support.v4" error:

Duplicate class android.support.v4.app.INotificationSideChannel found in modules core-1.3.1-runtime (androidx.core:core:1.3.1) and support-v4-21.0.3-runtime (com.android.support:support-v4:21.0.3)
Solution:
Add the following code ingradle.properties:
android.useAndroidX=true
android.enableJetifier=true

When integrating the mini program SDK and compiling the project, You might face a "compileDebugJavaWithJavac" version mismatch error:

Execution failed for task ':app:kaptGenerateStubsDebugKotlin'.
> 'compileDebugJavaWithJavac' task (current target is 1.8) and 'kaptGenerateStubsDebugKotlin' task (current target is 17) jvm target compatibility should be set to the same Java version.
  Consider using JVM toolchain: https://kotl.in/gradle/jvm/toolchain
Solution:
Update the JDK version in build.gradle under compileOptions.
android { compileOptions { sourceCompatibility JavaVersion.VERSION_17 // Needs to match the kapt version targetCompatibility JavaVersion.VERSION_17 // Needs to match the kapt version } }

If you encounter a "java.lang.NoClassDefFound, ProxyService" error:


Solution:
Check and remove the following configuration if it exists.
kapt.include.compile.classpath=false

Minimum Android version supported

minSdkVersion: 21 (Android 5.0)

SDK initialization check

From version 1.5.1.1 of the mini_core, you can check if the SDK initialized successfully by filtering logs with MINI_SHARK. A successful initialization will log: 'shark init ok!'

If the initialization fails, an exception log will be displayed.


Supported devices for debugging

Supported: ARM architecture emulators and real devices. Not supported: x86 emulators.

Taro framework support

Uncaught DOMException: Failed to read the 'sessionStorage' property from 'Window': Access is denied for this document.
    at <anonymous>:1207:96250
    at Array.forEach (<anonymous>)
    at Module.<anonymous> (<anonymous>:1207:96164)
    at Module.9 (<anonymous>:1207:113782)
    at l (<anonymous>:1203:566)
    at Module.204 (<anonymous>:1215:87806)
    at l (<anonymous>:1203:566)
    at t (<anonymous>:1203:435)
    at Array.r [as push] (<anonymous>:1203:298)
    at <anonymous>:1215:125
Add the following dependency if using the Taro framework:
implementation 'com.tencent.tcmpp.android:mini_extra_v8:${version}'

Troubleshooting mini program request errors

Errors during mini program operations like scanning, launching, or searching will be shown via Toast messages, including error codes and TraceId. These details are also logged for further investigation.
For 5-digit error codes, these are general client-side errors. Refer to theAndroid error codes for specific details. Common error codes include:
-11001: Shark network error. Check the network link and gateway between the client and server.
-11002 Server-side business logic error. Investigate the service based on the accessed API, and search the specific business error codes in the logs.
-11006 The mini program does not exist in the current configuration environment. Check if the mini program is released and the environment matches the app's configuration.
-12001 Shark network instance creation failed, usually due to missing, incorrect, or mismatched configuration files.
-12012 Mini program download failed. Ensure the download service is operational.
-12013 Mini program package parsing error. The package may be corrupted. Check for non-ASCII characters in resource file paths if using an older backend version.
For errors with different digit counts, they indicate specific business errors similar to -11002.
Use the TraceId to correlate and find the request details in backend logs for troubleshooting.




Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback

Contact Us

Contact our sales team or business advisors to help your business.

Contact Us
Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 available.

Submit a Ticket
7x24 Phone Support
Hong Kong, China
+852 800 906 020 (Toll Free)
United States
+1 844 606 0804 (Toll Free)
United Kingdom
+44 808 196 4551 (Toll Free)
Canada
+1 888 605 7930 (Toll Free)
Australia
+61 1300 986 386 (Toll Free)
EdgeOne hotline
+852 300 80699
More local hotlines coming soon