Add privacy manifest to the xcframework bundle #37
Annotations
7 errors and 12 warnings
|
Test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
|
Test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
|
Test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
|
Test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
|
Test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
|
Test:
CriteoPublisherSdk/Tests/IntegrationTests/CR_DfpNativeFunctionalTests.m#L103
test_givenValidNative_whenLoadingNative_thenDfpViewContainsNativeCreative, ((renderedProperly) is true) failed
|
|
Test
Process completed with exit code 1.
|
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3, actions/setup-java@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Test
Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'CriteoPublisherSdk' from project 'CriteoPublisherSdk')
|
|
Test:
Pods/Pods.xcodeproj#L1
The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 9.0, but the range of supported deployment target versions is 11.0 to 16.2.99. (in target 'CriteoMRAID-CriteoMRAIDResource' from project 'Pods')
|
|
Test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L458
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
|
Test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L507
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "tests-reports".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
|
Test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L589
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
|
Test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L629
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
|
Test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L710
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
|
Test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L750
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
|
Test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L832
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
|
Test:
CriteoPublisherSdk/Tests/UnitTests/CR_BidManagerTests.swift#L872
Closure Parameter Position Violation: Closure parameters should be on the same line as opening brace (closure_parameter_position)
|
Loading