More information like this, you can visit HUAWEI Developer Forum
How Does the SDK Work
The Drive SDK is loaded into your app during app packaging. It works when the app is started. When your app calls the Drive SDK API, the Drive SDK sends a request to the Drive server. After receiving the response from the Drive server, the Drive SDK parses the response and returns the processing result to your app. The Drive SDK stops as soon as your app is closed, without performing any additional operations in the background.
What Permissions Are Required for Using the SDK
The Drive SDK requires the following permissions:
android.permission.INTERNET: network access permission, which is used to access the network and communicate with the Drive server.
android.permission.WRITE_EXTERNAL_STORAGE: read and write permissions, which are used to upload and download files.
What Data Does the SDK Collect
The Drive SDK collects the following information for app operation analysis: app ID, operation type, name of the file uploaded, size of the file uploaded or downloaded, and operation result.
The Drive SDK collects the following information for problem analysis: app name, app ID, unionId, operation type, mobile phone model, and size and name of the file uploaded or downloaded.
How the SDK Protects Data Security
The Drive SDK communicates with the Drive server through HTTPS. The app verifies the validity of the server certificate, and uploads and downloads all files using HTTPS. All files uploaded through the Drive SDK are encrypted and stored on the Drive server.
The Drive SDK does not cache sensitive data such as the access token from your app to the local storage.
For more details, you can go to:
Official website
Development Documentation page, to find the documents you need
Reddit to join our developer discussion
GitHub to download demos and sample codes
Stack Overflow to solve any integration problems
Does Huawei drive kit work in india?
What should I do if a 907135702 error occurs when I try to connect to HMS Core?
Related
Requirements:
AmazeBackup: https://forum.xda-developers.com/smartwatch/amazfit/utility-amazebackup-backup-tool-pace-t3801165
FitnessSyncer.com account;
DropBox / GoogleDrive / OneDrive account (it will be used by FitnessSyncer to automatically sync new data when it is extracted from watch);
Runalyze.com account: it will get data from FitnessSyncer and calculate VO2max (run activities only), it's optional;
Know how to read and install/configure simple software on computer.
It works with ANY watch (Pace/Stratos/Verge), ANY firmware (unlocked or not) and ANY computer (macOS/Linux/Windows).
Download and install AmazeBackup, connect watch to computer and run option #12 (export data), it should create a folder named "export" inside its main folder;
Install and login to DropBox/GDrive/OneDrive, configure it to sync data from the "export" folder above (here you have to know how to do it by yourself, it varies from software to software, computer to computer, user your brain and tutorials from help pages and the internet);
Login to FitnessSyncer, open your account page and add a new *Source* (image 03);
Add your online service (DropBox/GoogleDrive/OneDrive) as "Maps", set "File Type" as GPX, grant permission and point to the folder in your online storage service that will sync the "export/gpx" folder (image 04 - standard Advanced Options settings should work, but you may want to change them if you find any problems with multiple data sources later);
OPTIONAL: Do the same for the TCX folder if you also want to sync non-GPS data, obviously setting "File Type" as TCX and pointing to "export/tcx" in your online storage;
In order to get VO2max calculation, you must sync to Runalyze, then go to Account page and add a new *Destination*, then fill the data and grant permissions accordingly (image 05);
OPTIONAL: If you want to sync data with other services like Endomondo or whatever you use, go back to you Account page and add new Destination, then fill the required fields in "Synchronize with Service" (image 06).
Both FitnessSyncer and Runalyze have an extensive help, read them before asking questions. I like the way Runalyze shows data, but if you just want to concentrate all your activities in one place, FitnessSyncer may be enough, it even has a phone app for both Android and iOS.
That's it, every now and then, after new activities, connect the watch to computer and run AmazeBackup option #12 again, new data should be uploaded to your online service and synced automatically via FitnessSyncer and your preferred online storage service.
All services and AmazeBackup are free, please donate to keep then running and their developers happy.
https://ko-fi.com/lfomartins
Or use XDA's donate link under my username. Thanks!
A pop-up is repeatedly displayed to users when they sign in to the game, asking them to install or update to the latest version of HMS Core.
Log Analysis
Search for Failed to find HMS apk in the Logcat log file. Multiple results will be returned.
The following log indicates that HMS Core (APK) is not installed when the initialization API init is called to check for it:
XML:
Initializing JosAppsClient
I/HMSSDK_HuaweiApiManager: sendRequest
I/HMSSDK_BaseHmsClient: ====== HMSSDK version: 40000300 ======
I/HMSSDK_BaseHmsClient: Enter connect, Connection Status: 1
I/HMSSDK_BaseHmsClient: connect minVersion:30000000
E/HMSSDK_HMSPackageManager: skip package com.huawei.hwid for metadata is null
E/HMSSDK_HMSPackageManager: Failed to find HMS apk
The following log indicates that HMS Core (APK) is not installed when the sign-in API signIn is called to check for it:
I/HMSSDK_[HUAWEIIDSDK]HwIdSignInClientHub: onCreate
I/HMSSDK_HmsAPKVersionCheckUtil: ====== HMSSDK version: 40000300 ======
I/HMSSDK_HmsAPKVersionCheckUtil: check minVersion:30000000
E/HMSSDK_HMSPackageManager: skip package com.huawei.hwid for metadata is null
E/HMSSDK_HMSPackageManager: Failed to find HMS apk
I/HMSSDK_AvailableAdapter: main thread invokes resolution.
I/HMSSDK_AvailableAdapter: startResolution
According to the logs, both the init and signIn APIs find that HMS Core (APK) is not installed, and thus two pop-ups are displayed.
Solution
1. Update the integrated Game Service SDK to 5.0.1.301 or later. For more details, please refer to the official materials.
2. If you prefer not to update the SDK, you can also change the sequence for calling the sign-in and initialization APIs, so that the initialization API is called after the sign-in is successful.
This will ensure that the pop-up displays only once.
BackgroundI had recently planned on integrating the Crash SDK to my app. However, my app was developed through Eclipse and the integration process was different from that in Android Studio.
By referring to the official materials, I downloaded the tool package and used it to generate an Eclipse project package.
However, when the build.bat file in the aar2eclipse/aar directory was executed according to the procedures in the document, an error was reported in the command line. The error information was as follows:
FAILURE: Build failed with an exception.
* What went wrong:
Task ' assembleRelease ' not found in root project ' aar '.
Problem Reoccurring1. I first thought that the problem might be caused by my company's intranet. But when I connected to the Internet, the problem remained unsolved.
2. Then I guessed that it might have something to do with the Android development environment.
I borrowed a colleague's PC to execute the build.bat file, and it that did the trick. Therefore, I was able to conclude that the problem was caused by incorrect configurations in the Android development environment. I compared the configurations on the two PCs and found that the environment variables were different. ANDROID_HOME was missing from the environment variables on my PC.
CauseHuawei's Eclipse tool package is unable to run properly and reports an error without the ANDROID_HOME variable.
Solution: Right-click This PC and choose Properties from the shortcut menu. In the displayed dialog box, click the Advanced System Settings tab and then click Environment Variables. In the System Variables dialog box, create a new ANDROID_HOME parameter.
Set the value to the installation path of the local Android SDK, and the problem will be resolved, as shown below.
Reference:
https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agc-get-started#h2-1587519820720
I have been using the Crash service provided by HUAWEI AppGallery Connect recently. However, I encountered two problems when using it. One is that the native symbol file failed to be generated, and two, I failed to upload the file. In this post, I summarized my experience in the hope that it will help others who encounter the same problem.
Generating a Native Symbol FileI added the following code by referring to the official materials but couldn't find the agcp task in the Tasks directory under
Gradle.
Code:
agcp{
debug = true
appVersion = 1.0
symbolUpload = true
debugSoDirectory = "D:\\Onebox\\AndroidProject\\crashdemo\\app\\build\\intermediates\\cmake"
ndkDirectory = "D:\\AndroidSDK\\sdk\\ndk\\21.3.6528147"
}
I checked the documentation and found that I hadn't added the JSON file, so I added the JSON file to the app directory and synchronized the project. This resolved the problem.
A missing debugSoDirectory parameter will also cause the problem. So, make sure you add it as well.
Uploading a Native Symbol FileOnce the file was generated, I double-clicked processReleaseSymbolUpload. An HTTP exception was reported, as shown in the following figure.
I often connect my PC to our company's proxy. Once I disconnected from the proxy, the file was uploaded successfully.
If you cannot upload the file using a gradle plugin, you can also use a symbol table tool.
Or, you can manually upload the file in AppGallery Connect.
For more info see the official documentation
I encountered a few issues in the process of integrating the APM SDK. In this post, I will share these cases for you, so that you will have a sense of how to resolve them.
Issue 1: Error "miss client id" Is Reported After the APM SDK Is IntegratedThe detailed error message is as follows:
I/com.huawei.agc.apms: failed to fetch remote config: client token request miss client id, please check whether the 'agconnect-services.json' is configured correctly
Click to expand...
Click to collapse
TroubleshootingBy searching through the forum, I found that the issue is caused by the absence of the AppGallery Connect plugin. For details, please refer to this forum post.
To solve the problem, just add the following code to the app-level build.gradle file:
apply plugin: 'com.huawei.agconnect'
Click to expand...
Click to collapse
Issue 2: Cannot Find the Reported APM Logs on the DeviceWhen the APM SDK is integrated, there was no app performance data on the App performance management page. I wanted to locate the problem based on the Logcat logs on the device.
However, I wasn't sure how to find the APM logs.
TroubleshootingI checked the APM documentation and found out how to access the logs:
Open the AndroidManifest.xml file of the app, and add the meta-data element to application.
<application>
<meta-data
android:name="apms_debug_log_enabled"
android:value=" true" />
</application>
After the APM debug log function is enabled, you can use the Logcat log filter function com.huawei.agc.apms or apms to view the logs.
Please note that only the value of resultCode is 200 indicates that the data is reported successfully.
I/HiAnalyticsSDK: SendMission=> events PostRequest sendevent TYPE : oper, TAG : APMS, resultCode: 200 ,reqID:b639daae0490c378cf242544916a9c36
Click to expand...
Click to collapse
Issue 3: No Successfully Uploaded AMPS Logs in the Logcat.The meta-data element has been added and set to true. The contains and sending logs can be viewed in the Logcat, with the exception of the successfully uploaded AMPS logs.
TroubleshootingThe check result shows that the agconnect-services.json file was downloaded before the APM service was enabled. This indicates that it needs to be updated.
Before the service was enabled, the JSON file contained only 29 lines. After the service was enabled, more parameters were added to the file that it has contained 52 lines.
Update the JSON file, and you'll be able to view the successfully uploaded AMP logs.
Issue 4: No APM Data Displayed in AppGallery Connect While Logs Are AvailableWhen locating this problem, I found a log in which the result code is 200. However, still no APM data is available in AppGallery Connect.
The corresponding logs are as follows:
I/HiAnalyticsSDK: hmsSdk=> events PostRequest sendevent TYPE : maint, TAG : _hms_config_tag, resultCode: 200 ,reqID:842927417075465ab9ad990e2ce92646
Click to expand...
Click to collapse
TroubleshootingThe value of TAG in the preceding log is not APMS. Therefore, it cannot be the log that indicates that the APM data is successfully loaded.
I analyzed the logs and found some authentication failure logs.
E/HiAnalyticsSDK: HttpTransportCommander=> NE-004|IO Exception.timeout
D/HiAnalyticsSDK: HttpTransportCommander=> request times: 1
I/HiAnalyticsSDK: getPubKey=> result code : -102
Click to expand...
Click to collapse
After contacting Huawei technical support, I learned that the data reporting channel of the HiAnalyticsSDK used by APM has an authentication problem.
I went to My projects > HUAWEI Analytics in AppGallery Connect and enabled HUAWEI Analytics. After a while, the authentication was successful.
Issue 5: No Related Network Request Performance Data Is Displayed.All of the performance data is normal with the exception of the network request data, which is not displayed in AppGallery Connect.
TroubleshootingAccording to the official documentation, obtaining network request data depends on the APM plugin. The data can only be obtained after the APM plugin has been correctly integrated.
To integrate the plugin, do as follows:
In the project-level build.gradle file, add the following code in dependencies:
classpath 'com.huawei.agconnect:agconnect-apms-plugin:1.4.1.305'
In the app-level build.gradle file, add the following code:
apply plugin: 'com.huawei.agconnect.apms'