Search Issue Tracker
Fixed in 2020.2
Fixed in 2018.4, 2019.4, 2020.1
Votes
0
Found in
2017.4
2019.3.0f3
2020.1
Issue ID
1222455
Regression
No
[iOS] CoreLocation.framework is not automatically exported to build when it is included in a Plugin
How to reproduce:
1. Open the user-supplied project
2. Build for iOS and attempt to deploy the build onto a device on Xcode
3. Observe the errors
Expected result: CoreLocation.framework is included in the build and does not cause errors
Actual result: Xcode throws error "Undefined symbol: _OBJC_CLASS_$_CLLocationManager"
Reproducible with: 2017.4.37f1, 2020.1.0a25
Reproduces on:
VLNQA00160 iPhone 6s iOS 13.3.1
VLNQA00249 iPhone 6 iOS 12.4.2
Notes:
1. CoreLocation is included in the plugin by default (navigate to the Project window, Assets -> Plugins -> iOS and inspect LocationPermission.m - in its Platform Settings, CoreLocation is included by default)
2. It is possible to go about this issue by manually adding CoreLocation.framework to either Unity-iPhone target (pre 2019.3) or UnityFramework target (post 2019.3)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error in console when using the progress bar API along with Texture compression
- NullReferenceException when selecting a Dropdown Component override in the Prefab Overrides menu for the second time
- USS variables are broken on IOS
- Crash when project is reopened or upgraded
- Hub doesn't install windows 10 sdk properly
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a13