How to Troubleshoot When Acceleration Does Not Take Effect After SDK Integration?
Troubleshoot in the following order:
1. Confirm that the device License is bound to the console.
2. Check whether the AccCallback.onAccStart() callback is triggered. If it is not triggered, initialization has failed. In this case, verify that the appId/sign are correct.
3. Invoke MpAcc.getMeasureResult() to view the latency comparison before and after acceleration, and confirm whether the acceleration is effective.
4. Check whether the target service domain name has been added to the acceleration allowlist in the console.
What Happens After the Traffic Package Is Exhausted? Will Services Be Interrupted?
The behavior depends on the "Traffic Overage Policy" configured in the console. By default, the acceleration cutoff mode is used: acceleration stops after the quota is exceeded, traffic routes through the regular network, and services remain uninterrupted. Alternatively, you can configure the postpaid mode: after exceeding the package quota, you are billed based on actual usage, and acceleration continues to take effect. It is recommended that you set up usage alarms in the console and renew or scale out resources in advance.
What Are the Differences Between Android and iOS Integration Methods?
The core APIs are consistent (including AccConfig initialization, startAcc(), and stopAcc()). The differences are as follows:
1. For Android, you can add the AAR via Gradle dependency. For iOS, you can add the Framework via CocoaPods or manually.
2. For iOS, you must add the NEVPNStatusDidChangeNotification permission declaration in the Info.plist file.
3. Advanced features (including plugin-based NIC acceleration and SO dynamic acceleration) are currently supported only on Android. For iOS, the standard plugin integration solution is used.