Search Issue Tracker
By Design
Votes
0
Found in [Package]
preview.5 - 1.0.0
Issue ID
1184558
Regression
No
[iOS] Mobile Notifications cross-build produces an Xcode project that fails during the Deployment process
The Mobile Notification package executes a post-build Editor script that changes the Project file (iOSNotificationPostProcess). This post-process script only executes when PLATFORM_IOS is defined. When using the BuildPipeline.BuildPlayer from another Platform, this is not executed and leaves the Project unable to build. When building with Xcode, Customer gets "Undefined symbols" Error because the Notification Framework was not added to the Project
To reproduce:
1. Download attached "NotificationsCrossBuild.zip" project and open in Unity
2. Open Build Settings and change Target Platform to Mac OS X
3. Press Tests > Build
4. When Xcode project is built deploy it to the iOS device
Expected results: Xcode successfully deploys Project to the Device
Actual results: Project deployment fails and Xcode throws 8 Errors about Undefined symbols
Notes:
- This issue seems to be related only with iOS
- Cannot check on other Players because this Project is built specifically for iOS
- If Target Platform is set to iOS, then everything works as Expected
- Cannot check on preview.4 - 1.0.0 and lower Package version, because Project becomes corrupted
Reproduced on Package preview.5 - 1.0.0 and preview.2 - 1.0.4
Reproduced on Unity 2019.2.7f2, 2019.3.0b5 and 2020.1.0a5
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Resolution Note:
Per buildpipeline team, it's a known issue when the build target is iOS. The workaround is to switch, wait for domain reload, then build.