mapbox / mapbox/mapbox-maps-ios
Fatal Exception: InvalidArgument
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 601
- Forks
- 196
- PR merge metrics
- No merged PRs in 30d
Description
## Environment
- Xcode version: 16.4
- iOS version: Multiple (iOS 18, iOS 26)
- Devices affected: Multiple (iPhones, iPads)
- Maps SDK Version: 11.10.3
## Observed behavior and steps to reproduce
We are receiving increased number of crashed reported from crashlytics:
String is not valid UTF-8: MjAyMCBDQTEwggEiMA0GCSqGSIb3DQEBAQUvc2RrLXNlc3Npb25zL3YxP2FjY2Vzc190b2tlbj1zay5leUoxSWpvaWIzSmtibUZ1WTJWemRYSjJaWGtpTENKaElqb2lhUzF6VFhKMU9DSjkuRmZydVhEVi1uWVhiQVlpMXpDcm54USZza3U9MTAweU1JZzNzV2NmNjU2OWJkZTNiZjMwYWFkYTdhMTcwYWJmNGNlYjU3Ng==
(Strings are different)
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 crash details, attached examples, and the reported Xcode, iOS, and Maps SDK versions; no source file, test, or reproduction entry point is named. A useful handoff would identify where the invalid UTF-8 argument enters the SDK and provide a reproducible check for the reported input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100