![]() ![]() For clients who still have reasons to keep using the old framework packages in the application and do not migrate to XCFramework we distribute "fat" frameworks both static and dynamic for the release 8.1.0.0. We highly recommend to migrate to XCFramework for all our clients. Please use the corresponding XCFramework while migrating from static or dynamic framework for tvOS. ![]() XCFramework allows to combine iOS and tvOS platforms in a single package. Note: Nielsen SDK builds for tvOS are no longer distributed as separated packages. ![]() The following Pod versions are now available: (For 'kids' apps, please use the NoId framework (EG: NielsenNoIdAppSDK-XC). Inside of this workspace you will see “Pods” target which will include ready to use NielsenAppApi framework. From this moment, that file should be used for using the target project instead of previous one with extension “.xcodeproj”. If using Dynamic Framework, from the command line, type the following:Ĭocoapods will automatically create a new file with extension “.xcworkspace”. Note: We highly recommend to migrate to XCFramework for all our clients. the naming for the pod NielsenTVOSAppSDK should be changed to NielsenAppSDK-XC. So in addition to appending of the -XC suffix to the pod name in the podfile please remove TVOS. If you migrate from the TVOS dynamic framework to the XCFramework, please note that TVOS slices are now part of the same XCFramework with iOS slices. real_path puts "post_install: Found # file with a value: amework" end end end end ![]() each do | config | xcconfig_path = config. xcconfig file # update Pods - NielsenVideoPlayerTVOSPodsXC. name = 'Pods-NielsenVideoPlayerTVOSPodsXC' # update Pods - NielsenVideoPlayerTVOSPodsXC. framework post_install do | installer | installer. # modify XCFramework configuration files to update NielsenAppApi. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |