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

error: Swift package target 'Realm' is linked as a static library by 'AppName' and 'Realm', but cannot be built dynamically because there is a package product with the same name. #8694

Closed
bekzodrakhmatof opened this issue Oct 1, 2024 · 3 comments

Comments

@bekzodrakhmatof
Copy link

How frequently does the bug occur?

Always

Description

error: Swift package target 'Realm' is linked as a static library by 'AppName' and 'Realm', but cannot be built dynamically because there is a package product with the same name.

Stacktrace & log output

error: Swift package target 'Realm' is linked as a static library by 'AppName' and 'Realm', but cannot be built dynamically because there is a package product with the same name.

Can you reproduce the bug?

Always

Reproduction Steps

error: Swift package target 'Realm' is linked as a static library by 'AppName' and 'Realm', but cannot be built dynamically because there is a package product with the same name.

Version

all

What Atlas Services are you using?

Local Database only

Are you using encryption?

No

Platform OS and version(s)

iOS 18

Build environment

[Xcode version: ...
Dependency manager and version: ...
](error: Swift package target 'Realm' is linked as a static library by 'AppName' and 'Realm', but cannot be built dynamically because there is a package product with the same name.)

Copy link

sync-by-unito bot commented Oct 1, 2024

➤ PM Bot commented:

Jira ticket: RCOCOA-2440

@isabsent
Copy link

Which version of Realm is affected by this bug? Only the latest or all previous ones too?

@bekzodrakhmatof
Copy link
Author

It was on the all versions as well. But it looks like it worked after some workaround. It could be something conflicting with other packeges.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants