Skip to content
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

Build fails because of missing PrivacyInfo.xcprivacy after Upgrading to 6.8.0 #2631

Closed
4 of 12 tasks
Lutzifer opened this issue Oct 10, 2024 · 5 comments
Closed
4 of 12 tasks

Comments

@Lutzifer
Copy link
Contributor

Short description of the issue:

Build fails because of missing PrivacyInfo.xcprivacy after upgrading to 6.8.0.
We use xcodegen to include the dependencies via SPM.

Expected outcome:

I can build the app with 6.8.0 the same way as before 6.8.0

What actually happens:

Screenshot 2024-10-10 at 12 55 07

We get PrivacyInfo.xcprivacy errors

Self contained code example that reproduces the issue:

As the error happens on a project level, a code example is hard to provide but can try to whip up a standalone smaller project if needed.

RxSwift/RxCocoa/RxBlocking/RxTest version/commit

6.8.0, release version

Platform/Environment

  • iOS
  • macOS
  • tvOS
  • watchOS
  • playgrounds

How easy is to reproduce? (chances of successful reproduce after running the self contained code)

  • easy, 100% repro
  • sometimes, 10%-100%
  • hard, 2% - 10%
  • extremely hard, %0 - 2%

Xcode version:

Version 16.0 (16A242d)

Installation method:

  • SPM

I have multiple versions of Xcode installed:
(so we can know if this is a potential cause of your issue)

  • yes (which ones)

15.4.0, 16.0.0

Level of RxSwift knowledge:

  • I have a significant code base
@freak4pc
Copy link
Member

I couldn't reproduce this in a fresh SPM project:
image

Also, we (monday.com) use Tuist (which works over XcodeGen) and we had no issues with upgrading/building.

Can you provide some reproduction I could debug further?

@Lutzifer
Copy link
Contributor Author

I'll see if I can extract something tomorrow, thx for having a look.

@Lutzifer
Copy link
Contributor Author

oh, and it only occurs on builds to a device, simulator runs fine.

@freak4pc
Copy link
Member

Device looks fine, too. LMK if you can reproduce something - I won't be available until next week but will take a look as soon as I can :)

image

@Lutzifer
Copy link
Contributor Author

Issue has somehow disappeared over night, seems to be some weird caching issue somewhere.

Thx for having a look again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants