DocsICP FilingConsole
官方文档
首页

Troubleshooting steps for iOS SDK integration errors

更新时间：
复制 MD 格式
产品详情
我的收藏

Troubleshooting steps

  • If your project already includes other Alibaba SDKs, such as the Alipay SDK, integrating the Mobile Push SDK may cause a UTDID conflict error.

    • If you integrate the Push SDK using Pods, manually integrate the version of the Alipay SDK that excludes the UTDID component. For more information, see UTDID conflict issues when using Alibaba Cloud product SDKs.

    • If a UTDID conflict occurs when you integrate both the Push SDK and other Alibaba SDKs using Pods, manually integrate one of the SDKs. Remove the UTDID dependency for the manually integrated SDK, and retain the UTDID dependency from the Pods integration.

  • If you encounter issues when integrating the SDK using Pods, see FAQ and solutions for iOS SDK integration using Pods.

  • If the console prints the following log after you integrate the SDK:

    1. [NSConcreteMutableData gzipDeflate]: unrecognized selector sent to instance

    • To resolve this, open your project configuration, go to Build Settings > Other Linker Flags, and add -ObjC, as shown in the following figure:

  • If a compile error occurs after you add -ObjC, see Errors when configuring -ObjC.

  • If initialization returns a route not found error after you switch the appKey, see Resolving the "route not found" error after switching the appKey on iOS.

If the preceding steps do not resolve the issue:

  1. When you report an issue, include the following information in the specified format to help us quickly identify the problem. Fields marked with an asterisk (*) are required.

  2. Operation:

  3. Unexpected behavior:

  4. Device platform (Android or iOS):

  5. Push method (all, account, device, tag, or alias):

  6. * AppKey:

  7. * Message ID (available in the console):

  8. * Device ID (available in the terminal log):