-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
warning: no rule to process file 'macos/Pods/PostHog/PostHog/Resources/PrivacyInfo.xcprivacy' of type 'text.xml' for architecture 'arm64' (in target 'PostHog' from project 'Pods') #137
warning: no rule to process file 'macos/Pods/PostHog/PostHog/Resources/PrivacyInfo.xcprivacy' of type 'text.xml' for architecture 'arm64' (in target 'PostHog' from project 'Pods') #137
Comments
Is this warning normal? How can I fix it? |
Hi @stephane-archer! This is the repo of the PostHog service, but the problems looks like a client library one. Are you perhaps using https://github.com/PostHog/posthog-flutter? |
@stephane-archer thanks for raising this issue, PostHog/posthog-flutter#105 should fix it |
@marandaneto Thank you for fixing the issue :) |
Found a few similar issues |
the problem doesn't seem to be solved |
@marandaneto please re-open this issue |
I am not entirely sure what causing this, maybe it's a macOS issue since it's not the case for iOS? ideas? everything seems to be configured correctly (based on official docs). |
@marandaneto I have no idea. Do you have access to MacOS? I'm not sure how I can help you with this. Maybe you should open an issue on Flutter Git Hub? Their testing on MacOS is not always the best, the issue might not be on your side. |
Yes, I do have a macOS and I can see the warnings on CI as well, will check if the warning appears without Flutter as well. , will give it another try later this week, as I mentioned, it is a warning and the build succeeded, so not a blocker for now I guess, thanks for testing it. |
@marandaneto I'm glad you can reproduce the issue. a warning is usually not created for no reason and makes the user wonder if they have configured Posthog correctly. It also makes the package look less professional, firebase is a joke when you compile your app and you see the number of warnings they create. You wonder if they know what they are doing. So, it is not a deal breaker but I would not consider this as useless. |
Totally agree :) I also see that on our iOS build (iOS native SDK, no flutter):
So if there's something on our end, it's not on the Flutter SDK wrapper |
I also get this warning when running https://github.com/PostHog/posthog-ios/tree/main/PostHogExampleWithPods But if I generate a privacy report: Everything is working correctly, it might be something with Pods or Xcode, but I don't see any difference between our setup and other libs. |
Hopefully https://github.com/PostHog/posthog-ios/releases/tag/3.4.0 fixes it |
@marandaneto Is it already available for users? can you tell me what version it is so I can test? |
@stephane-archer 3.4.0 as linked above, if using flutter, you just have to upgrade your pods because the flutter dep always use the latest version 3.x.x |
Pods version
|
Please test it using 3.4.0 as requested. |
if I delete |
@stephane-archer This is just pods caching, you can see here the latest version https://cocoapods.org/pods/PostHog |
@marandaneto I was able to update the pods and I don't see the warning anymore. |
@stephane-archer happy that it is fixed. |
@marandaneto can you force a pod update when someone updates their flutter package? |
Bug Description
Debug info
No response
The text was updated successfully, but these errors were encountered: