mapbox / mapbox/mapbox-navigation-ios
[Bug]: Invalid Package.swift manifest of mapbox-navigation-native-ios in latest release
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 918
- Forks
- 326
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
### Mapbox Navigation SDK version
3.12.1
### Steps to reproduce
1. Clone `git clone https://github.com/mapbox/mapbox-navigation-native-ios`
2. Fetch git tags
3. Checkout `git checkout v324.15.2`
4. Execute `swift package describe`
**NOTE:** This is fixed on main branch but requires a new release of both navigation-ios and navigation-native-ios packages.
## Background
We are using [bazel](https://bazel.build) as our build system and [rules_swift_package_manager](https://github.com/cgrindel/rules_swift_package_manager) to pull in Swift packages. Problem is that [rules_swift_package_manager](https://github.com/cgrindel/rules_swift_package_manager) relies on `swift package describe` command to construct the BUILD files for bazel which in this case does not work.
### Expected behavior
The Swift Package Manager should have printed out the JSON description of the package.
### Actual behavior
```
error: Source files for target MapboxNavigationNativeTests should be located under 'Tests/MapboxNavigationNativeTests', or a custom sources path can be set with the 'path' property in Package.swift
```
### Is this a one-time issue or a repeatable issue?
repeatable
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Package.swift and reproduce the failure using `swift package describe` at tag v324.15.2, then compare the tagged package with the fix already present on main. Done means releasing updated navigation-ios and navigation-native-ios packages so the Swift Package Manager can emit the package description.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100