Skip to content

feat: add path property to custom event #2372

feat: add path property to custom event

feat: add path property to custom event #2372

Triggered via pull request September 29, 2024 08:27
Status Failure
Total duration 3m 17s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 11 warnings
build: GrowingAutotrackerCore/Page/GrowingPageManager.m#L59
property 'customEventWithPage' not found on object of type 'GrowingTrackConfiguration *'; did you mean 'referCustomEventWithPage'?
build
Process completed with exit code 65.
build
You are using macOS 12. We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version. It is expected behaviour that Homebrew will be buggy and slow. Do not create any issues about this on Homebrew's GitHub repositories. Do not create any issues even if you think this message is unrelated. Any opened issues will be immediately closed without response. Do not ask for help from Homebrew or its maintainers on social media. You may ask for help in Homebrew's discussions but are unlikely to receive a response. Try to figure out the problem yourself and submit a fix as a pull request. We will review it but may or may not accept it.
build: Example/Example.xcodeproj#L1
Multiple targets match implicit dependency for linker flags '-framework GrowingAPM'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ShareExtension' from project 'Example')
build: Example/Example.xcodeproj#L1
Multiple targets match implicit dependency for linker flags '-framework GrowingAnalytics'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ShareExtension' from project 'Example')
build: Example/Example.xcodeproj#L1
Multiple targets match implicit dependency for linker flags '-framework GrowingAnalytics'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'GrowingAnalyticsStartTests' from project 'Example')
build: Example/Pods/Pods.xcodeproj#L1
Multiple targets match implicit dependency for linker flags '-framework GrowingAPM'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'GrowingToolsKit-GrowingToolsKit' from project 'Pods')
build: Example/Pods/Pods.xcodeproj#L1
Multiple targets match implicit dependency for linker flags '-framework GrowingAPM'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'GrowingAnalytics-18cf2943-GrowingAnalytics' from project 'Pods')
build: Example/Example.xcodeproj#L1
Multiple targets match implicit dependency for linker flags '-framework GrowingAnalytics'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'HostApplicationTests' from project 'Example')
build: Example/Example.xcodeproj#L1
Multiple targets match implicit dependency for linker flags '-framework GrowingAnalytics'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ProtobufTests' from project 'Example')
build: Example/Example.xcodeproj#L1
Multiple targets match implicit dependency for linker flags '-framework GrowingAnalytics'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'GrowingAnalyticsTests' from project 'Example')
build: Example/Example.xcodeproj#L1
Multiple targets match implicit dependency for linker flags '-framework GrowingAPM'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ExampleiOS13' from project 'Example')
build: Example/Example.xcodeproj#L1
Multiple targets match implicit dependency for linker flags '-framework GrowingAnalytics'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'ExampleiOS13' from project 'Example')