Search Issue Tracker
Fixed
Fixed in 6000.4.0b6, 6000.5.0a5
Votes
0
Found in
6000.4.0a4
6000.5.0a4
Issue ID
UUM-131209
Regression
Yes
[iOS] Pod integrated frameworks are not linked to UnityFramework
Steps to reproduce:
- Open the attached "HelloWorld" project
- Switch to the iOS Platform
- Build project
- Open .workspace file
- Build and run the app to the device
Actual results: Build fails with error: Framework 'GoogleMobileAds' not found
Expected results: Build is successful
Reproducible with versions: 6000.4.0a4, 6000.5.0a4_ca24f55d59d9_HEAD
Not reproducible with versions: 6000.4.0a3
Tested on (OS): MacBook Pro, Apple M1 Max, OS: Tahoe 26.2
Notes:
- Workaround:
** Go to the Unity-iPhone project and then select the UnityFramework target
** Go to Build Settings, search for "Framework Search Paths" and delete all values
* Go to the Pods folder and, depending on your Build Configuration, find the needed file in the Pods folder (if your Build Configuration is ReleaseForRunning, select "Pods-UnityFramework.releaseforrunning.xcconfig" file) and at the end of the "FRAMEWORK_SEARCH_PATHS = $(inherited)" add "$(PROJECT_DIR)/Frameworks"
This issue is reproducible not only with GoogleAds framework
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
- Performance Markers Search window shows an empty entry in the list
- Enabling Deep Profiling in Performance Markers Search window breaks Inspector panel buttons when navigating through the marker items
- Dragging selector from selector row background shows preview but does not apply class in UI Builder
- An "InvalidOperationException" error is thrown when TryRemoveItem is used with rebuildTree set to false
- Build fails with IL2CPP error when building on Android platform in a specific project
Resolution Note:
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.4.0b6):
Fixed in 6000.4.0b6