Invalid Token on Locator Suggest
Open
Priority - Moderate
Status - Backlog
Type - Bug
- Dominant language
- Swift
- Stars
- 19
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
When using a custom portal with a secured geocoder, calls to suggest fail with a, `Invalid token` error.
Portal URL is:
https://ragss12466.ags.esri.com/gis
Locator URL:
https://ragss12466.ags.esri.com/gis/sharing/servers/7b816fbacd6e4d9b98af54100a5bb173/rest/services/World/GeocodeServer
Geocoding works fine.
Contributor guide
Research direction
Start by reproducing suggest requests with the secured geocoder at the supplied portal and locator URLs, then compare them with the working geocoding path. Done means locator suggestions succeed without an Invalid token error while the existing geocoding behavior remains intact.
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
- 25/100