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

Package manifest at '/Package.swift' cannot be accessed (/Package.swift doesn't exist in file system) #8527

Closed
andgordio opened this issue Mar 22, 2024 · 5 comments

Comments

@andgordio
Copy link

How frequently does the bug occur?

Always

Description

• Create a new project in Xcode
• Follow the documentation, SwiftPM tab: https://www.mongodb.com/docs/realm/sdk/swift/install/
• See error when attempting to add the package: Package manifest at '/Package.swift' cannot be accessed (/Package.swift doesn't exist in file system)

Can be fixed by changing Dependency rule from “Up to latest major” to “exact: 10.48.1”

Stacktrace & log output

No response

Can you reproduce the bug?

Always

Reproduction Steps

No response

Version

latest

What Atlas Services are you using?

Local Database only

Are you using encryption?

No

Platform OS and version(s)

14.2.1

Build environment

Xcode version: Version 15.1
Dependency manager and version: SPM

Copy link

sync-by-unito bot commented Mar 22, 2024

➤ PM Bot commented:

Jira ticket: RCOCOA-2320

@Jaycyn
Copy link

Jaycyn commented Mar 23, 2024

I did these exact steps and did not encounter any issues

• Create a new project in Xcode
• Follow the documentation, SwiftPM tab: https://www.mongodb.com/docs/realm/sdk/swift/install/

I tried it with both a macOS app and iOS as well.

Running macOS 14.2.1, XCode 15.3 and the current Realm release v10.49.1. Here's a screenshot of what I entered.

Package

I built a project a couple of months ago with XCode 15.1 and didnt have any issues then.

Can you try upgrading your XCode? Perhaps there's a permissions issue - try Disk First Aid or even a reboot.

@andgordio
Copy link
Author

Double-checked my settings and noticed that the version was set to 1.0.0<2.0.0. I guess I got so used to the first field being pre-filled with the latest minor version that I didn’t pay attention to the input. Apologies for the confusion.

@Jaycyn
Copy link

Jaycyn commented Mar 24, 2024

Sooooo...... does that mean it can be closed or is there still an issue we're overlooking?

@andgordio
Copy link
Author

No issue. Please close. Thanks.

@nirinchev nirinchev closed this as not planned Won't fix, can't repro, duplicate, stale Mar 25, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 24, 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

3 participants