Geosearch not working in Instant Apps

1818
16
Jump to solution
02-11-2022 01:36 PM
ShannonPugh
Occasional Contributor

We have several geocoding services set up in our organizational settings. The services come from our on premises ArcGIS Server. For some reason they don't work in some instant apps and they do work in others. Also, they work fine in the web maps. I cannot determine the difference in the apps where they work and the apps where they don't. Any help would be much appreciated. It is greatly diminishing the usefulness of the apps.

0 Kudos
1 Solution

Accepted Solutions
KellyHutchins
Esri Frequent Contributor

In the meantime as a workaround if you feel comfortable editing the app data you could use AGO Assistant to remove the invalid field name. 

 

https://guide.assistant.esri-ps.com/docs/working-with-items

View solution in original post

0 Kudos
16 Replies
KellyHutchins
Esri Frequent Contributor

Which apps does it work in?  Which does it fail in?  When you say fail what exactly is happening? Is the locator showing up in the search widget or not? When searching is it not using the locator or is it failing to find locations?  Are there any errors that appear in the browser developer console?  

Also are any of the apps public? If so can you share a link and. we'll take a look? 

0 Kudos
ShannonPugh
Occasional Contributor

I haven't been able to determine specific apps that they work in and not work in. Locators are showing up in search widget, but return "There were no results found for "9204 latham st"." 

There are errors in the console, but I'm not sure if any are pertinent. I will share links of a couple of apps that do not work and one that works and then you can see the console yourself.

For simplicity, concentrate on the locator that is named "Site Address Locator for KnowYourZone" in the apps. Use "9204 Latham Street" for the search term.

Does not work:

https://escfl.maps.arcgis.com/apps/instant/minimalist/index.html?appid=3ed22391073e424b836ec873fa9d6...

https://escfl.maps.arcgis.com/apps/instant/minimalist/index.html?appid=813d866506a04266a53a94394e95f31a

Works:

https://escfl.maps.arcgis.com/apps/instant/basic/index.html?appid=3a2a2ae389bc46368e8f096ddb9c4466

If it helps, here is the url to the geocoding service:

https://gismaps.myescambia.com/arcgis/rest/services/StormSurge2018/escambiafl_surge_depth_locator_ne...

Thank you so much for your help!

 

0 Kudos
KellyHutchins
Esri Frequent Contributor
It looks like in some cases we are writing the property for the locator single line field name to “SingleLine” but in this locator that isn’t valid. We’ll look into why this is happening and get in a fix for the next release.


https://gismaps.myescambia.com/arcgis/rest/services/StormSurge2018/escambiafl_surge_depth_locator_ne...
0 Kudos
LaurieWilliams
New Contributor III

Hello,

I am currently having the same issue in Instant App. Any idea when this might be fixed?

Locators are showing up in the search widget, but return "There were no results found" for the inputted address, even though the geocoding service lists the exact address.

Thank you!

 

0 Kudos
KellyHutchins
Esri Frequent Contributor

Which app are you using? Do you have a public link to one so I can take a look and see if we can figure out what's happening?

0 Kudos
LaurieWilliams
New Contributor III

Thanks, I'm using Instant App Basic Viewer. Unfortunately, the app is not public yet. Neither the Esri nor our local geocoding service are returning values. But they work in the old basic viewer map apps.

0 Kudos
KellyHutchins
Esri Frequent Contributor

Are you using the Basic app or the Basic Viewer app? 

Basic: https://www.arcgis.com/apps/instant/basic/index.html

Basic Viewer: https://www.arcgis.com/apps/View/index.html

 

0 Kudos
LaurieWilliams
New Contributor III

Instant App, Basic template

Basic: https://www.arcgis.com/apps/instant/basic/index.html

 

Thanks!

0 Kudos
KellyHutchins
Esri Frequent Contributor

I ran a few tests with the Basic app and search locators are working for me. Any additional details you can share about your app setup (locators etc) might be helpful in allowing us to reproduce the issue.