The link to AMapPathManager is no longer available. Maybe after importing it with cocoapods, AMapPathManager is used elsewhere, but it is not set up and the third-party header file cannot be used. Please refer to the link below;
About the solution to the problem that third-party library header files do not prompt when importing when using cocoaPods
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
The link to AMapPathManager is no longer available. Maybe after importing it with cocoapods, AMapPathManager is used elsewhere, but it is not set up and the third-party header file cannot be used. Please refer to the link below;
About the solution to the problem that third-party library header files do not prompt when importing when using cocoaPods
http://blog.csdn.net/arthursh...