In Xcode 16 beta 3, adding a framework to a target doesn't work?

Question

drewolbrich OP

Created Aug ’24

Replies 7

Boosts 3

Participants 4

In Xcode 16.0 beta 3 (16A5202i) I'm trying to add a framework to a target.

I'm clicking the '+' button under Target > General > Frameworks, Libraries, and Embedded Content:

When I do this, the dialog that appears doesn't list any frameworks:

I feel like I'm doing something wrong or missing something obvious. This issue is easy to reproduce by creating a new project in Xcode.

I tried reverting using Xcode 15 to add the framework that way, but Xcode 15 is unable to load the project file that Xcode 16 wrote.

Incidentally, Add Other > Add Package Dependency has no effect when selected:

Assuming this is a bug I should submit feedback about, is there another method I can use in the meantime to add a framework to my target so I can continue working?

This is blocking development.

Thank you for any help you provide.

Answered by DTS Engineer in 798302022

It seems like the functionality was working in Xcode 16 beta 2 and has regressed in betas 3 and 4. This issue can be quite disruptive, and I'd greatly appreciate it if you could file a bug report.

Please be specific when filing; it would also be helpful if the report included information about the project type, frameworks used, etc.

Once you open the bug report, please post the FB number here for my reference.

If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why?

Boost

Answer 1

drewolbrich OP

Aug ’24

I updated to Xcode 16.0 beta 4 (16A5211f) and I am experiencing the same issue.

1

Answer 2

drewolbrich OP

Aug ’24

This issue does not occur in Xcode 16.0 beta 2 (16A5171r).

0

Answer 3

DTS Engineer OP

Apple

Aug ’24

Recommended

It seems like the functionality was working in Xcode 16 beta 2 and has regressed in betas 3 and 4. This issue can be quite disruptive, and I'd greatly appreciate it if you could file a bug report.

Please be specific when filing; it would also be helpful if the report included information about the project type, frameworks used, etc.

Once you open the bug report, please post the FB number here for my reference.

If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why?

0

Answer 4

fianamiky OP

Aug ’24

I upgraded to Xcode 16.0 beta 4 (16A5211f) and I'm encountering the same problem.

1

Answer 5

lukdor OP

Aug ’24

same problem in beta 4

1

Answer 6

drewolbrich OP

Aug ’24

Accepted Answer

I've discovered that one workaround is to temporarily load your project in Xcode 16.0 beta 2 and use that to add the frame to the target, and then switch back to Xcode 16.0 beta 4.

In the case of a local Swift package, another workaround, using Xcode 16.0 beta 4, is to add the package at the project level using the UI normally intended for adding remote packages, but selecting the local package option, and also selecting the option to add the package to a specific target. Once this is complete, remove the package from the project. The local package will remain associated with the target.

0

Answer 7

fianamiky OP

Aug ’24

I've found two workarounds for Xcode 16.0 beta issues. You can temporarily load your project in Xcode 16.0 beta 2 to add the frame to the target, then switch back to Xcode 16.0 beta 4. For local Swift packages in Xcode 16.0 beta 4, add the package at the project level using the UI for remote packages, select the local package option, add it to a specific target, then remove the package from the project. The local package will remain associated with the target. For more details, refer to this guide on managing packages in Xcode. [quote='798302022, DTS Engineer, /thread/761068?answerId=798302022#798302022']

It seems like the functionality was working in Xcode 16 beta 2 and has regressed in betas 3 and 4. This issue can be quite disruptive, and I'd greatly appreciate it if you could file a bug report.

Please be specific when filing; it would also be helpful if the report included information about the project type, frameworks used, etc.

Once you open the bug report, please post the FB number here for my reference.

If you have any questions about filing a bug report, take a look at [Bug Reporting: How and https://sellhamstercoin.com/)

[/quote]

0