mapbox / mapbox/mapbox-navigation-ios
func navigationViewControllerDidDismiss(_ navigationViewController: NavigationViewController, byCanceling canceled: Bool) { self.dismissNavigation() }
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.18.0
### Steps to reproduce
func navigationViewControllerDidDismiss(_ navigationViewController: NavigationViewController, byCanceling canceled: Bool) {
self.dismissNavigation()
} 导航页面都关闭了，还是后台播报导航，还有一个问题导航页面关闭后，重新发起导航提示Fatal error: MapboxNavigationProvider was instantiated twice
### Expected behavior
func navigationViewControllerDidDismiss(_ navigationViewController: NavigationViewController, byCanceling canceled: Bool) {
self.dismissNavigation()
} 导航页面都关闭了，还是后台播报导航，还有一个问题导航页面关闭后，重新发起导航提示Fatal error: MapboxNavigationProvider was instantiated twice
### Actual behavior
func navigationViewControllerDidDismiss(_ navigationViewController: NavigationViewController, byCanceling canceled: Bool) {
self.dismissNavigation()
} 导航页面都关闭了，还是后台播报导航，还有一个问题导航页面关闭后，重新发起导航提示Fatal error: MapboxNavigationProvider was instantiated twice
### Is this a one-time issue or a repeatable issue?
one-time
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 the navigationViewControllerDidDismiss(_:byCanceling:) callback and trace dismissNavigation(), then inspect how navigation audio and MapboxNavigationProvider lifecycle are handled after dismissal. Reproduce the background announcements and the subsequent “MapboxNavigationProvider was instantiated twice” fatal error; done means both repeatable behaviors have a documented or verified resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100