I. Troubleshooting allowBackup errors after integrating Mobile Feedback
If you encounter an issue, first search for keywords on the FAQ page.
Check if allowBackup is set to false in the AndroidManifest file. For more information, see allowBackup issues during compilation.
If the prompt still appears after setting it to false, modify the file as prompted. Adding tools:replace=”android:allowBackup” usually resolves the issue.
If the steps above do not resolve the issue:
Join the DingTalk group. The group number is 35248489.
Or, submit a ticket. Select the Feedback category for the ticket.
II. Troubleshooting package conflicts after integrating Mobile Feedback
1. If you encounter an issue, first search for keywords on the FAQ page.
2. Check which software development kits (SDKs) your project contains and check for other Alibaba SDKs. If so, check if you are using the latest SDK versions. Older versions may have dependency package conflicts that cannot be resolved. For example, very old Alipay SDKs have utdid rules that differ from current ones. Newer versions are more unified and require only a single dependency on the utdid package.
3. If a utdid conflict occurs as described in step 2, follow the instructions in that step. For more information, see utdid conflicts with other service SDKs.
4. If you receive the following error during compilation: Error:Execution failed for task’:app:transformClassesWithDexForDebug’.com.android.build.api.transform.TransformException:com.android.ide.common.process.ProcessException:java.util.concurrent.ExecutionException:com.android.dex.DexException:Multiple dex files define Lcom/ut/mini/core/sign/IUTRequestAuthenication; This conflict is caused by importing both ut and app-monitor. If you find both monitor and ut-5 JAR files, delete the monitor JAR file. If you find duplicate monitor files, keep only one. For more information, see ut and app-monitor conflicts during compilation.
If the steps above do not resolve the issue:
Join the DingTalk group. The group number is 35248489.
Or, submit a ticket. Select the Feedback category for the ticket.
III. Troubleshooting issues where the Mobile Feedback page does not open or is not clickable
1. If you encounter an issue, first search for keywords on the FAQ page.
2. For these types of issues, first check if the AppKey or AppSecret is correct. To obtain the AppKey and AppSecret, go to the Mobile Feedback management console, select the App list, and click AppKey to the right of the app. The AppKey and AppSecret are displayed on the page that opens.
3. If calling openFeedbackActivity does not return a response and the feedback page does not open, the AppKey or AppSecret is usually incorrect. Check the AppKey and AppSecret as described in step 2.
4. After opening the feedback page, if clicking "I want to give feedback" or "FAQ" has no effect, it is because calling the pauseTimers method of WebView pauses the layout, parsing, and JavaScript timers for all WebViews. This affects the operation of Mobile Feedback. To resolve this, call the resumeTimers method of WebView before you call the feedback feature.
5. The feedback page Activity may open slowly because it needs to pull configurations before opening. The opening speed depends on network conditions. A slow network can cause significant delays. You can use the openFeedbackActivity(final Callable success, final Callable fail) method. This method displays a "Loading" prompt before the call and closes the prompt during the callback.
If the steps above do not resolve the issue:
Join the DingTalk group. The group number is 35248489.
Or, submit a ticket. Select the Feedback category for the ticket.
IV. Customizing the Mobile Feedback interface and features
1. If you encounter an issue, first search for keywords on the FAQ page.
2. For all custom settings related to the interface and features, refer to the following integration documents: Android SDK integration and Android SDK integration.
3. If you have suggestions for a better user experience that are not currently implemented:
Join the DingTalk group to submit your suggestions to the helpdesk. The group number is 35248489.
Or, submit a ticket. Select the Feedback category for the ticket.
V. Troubleshooting issues related to the Baichuan version of Mobile Feedback
1. We recommend using the latest version on Alibaba Cloud. The new version does not require security images, which makes integration simpler. It also has more powerful features, such as the new voice feature, and can be configured to have the same interface and features as the Baichuan version. All data from the Baichuan version will be synchronized. The Alibaba Cloud Mobile Feedback URL is: https://www.aliyun.com/product/feedback?spm=5176.131995.388261.107.0TiTwF.
2. Notes on security image issues:
1) ErrorCode=607: There is a problem with the image file. This usually occurs when the APK signature used to obtain the image file does not match the current program's APK signature. Regenerate the image using the current program's APK. When you upload the image, ensure that the AppKey of the backend application matches the AppKey used in the program.
2) ErrorCode=608: The image file was not found. Ensure the image file is in the res\drawable folder. In an Android environment, this can happen if resource optimization reduces the file size to 0. Check the image in the APK. This is often caused using shrinkResource in Gradle.
3) ErrorCode=611: The key in the parameter was not found in the image file. Confirm that the image file contains this key.
3. A blank screen appears after upgrading from the Baichuan version to the Alibaba Cloud version. This usually means the Mobile Feedback service has not been activated on Alibaba Cloud. To resolve this, click Activate Now on the home page and follow the steps to activate the service. Then, check the Management Console to confirm that the AppKey and AppSecret are correct.
4. An error occurs when upgrading from the Baichuan version and integrating the Alibaba Cloud version: Class or method not found. For example: com.manjie.comic.phone E/AndroidRuntime: FATAL EXCEPTION: mainProcess: com.manjie.comic.phone, PID: 18879java.lang.RuntimeException: Unable to instantiate receivercom.alibaba.sdk.android.feedback.impl.NetworkChangeReceiver:java.lang.ClassNotFoundException: Didn’t find class “com.alibaba.sdk.android.feedback.impl.NetworkChangeReceiver”. In this case, clean the project and recompile, or restart Android Studio or Eclipse.
If you still cannot locate the problem after performing the preceding steps, you can:
Join the DingTalk group. The group number is 35248489.
Or, submit a ticket. Select the Feedback category for the ticket.