Custom locator published on Portal, shared publicly, and added as a locator to AGOL org not available in AGOL apps when not signed in

[IngridMans]

I have a custom locator that I published on our Portal and set sharing to 'Everyone.' It also has been added under out AGOL org's Geocoders (under org settings->Utilities). I notice how in the documentation, it is phrased that here is where you can add locators for which 'members of your organization will have access to...', so I'm not sure if actually possible, but I'd really like any public facing apps hosted on our AGOL org to default to using our custom locator that lives on our Portal ArcGIS Server. This includes the maps within Survey123 Surveys, maps in ArcGIS Field Apps, and anything built with Experience Builder or Instant apps. Currently apps trying to use that custom locator still prompt the user to sign in to our Portal, even though it is a publicly shared locator. 

Any advice or clarification? 

[Ann-SophieSølund]

Hi IngridMans,
I am not sadly not able to provide you an answer to your question but I do have a similar problem that I would like to ask about. It seems from your description that you are able to have custom geocode locators in for instance ArcGIS Field Maps app. Is that correctly understood? And If so, do you have any advice or documentation on how to change the geocode locator in Field Maps / Apps in general.
Any advice is greatly appreciated. Thank you

[IngridMans]

Hi Ann, 

I had added our (publicly accessible) Portal-published custom locator as one of the locators to make available to all users in our AGOL org (as an admin under Organization->Settings->Utility Services) and added that rest url under the Geocoding section. That seemed to be what made the locator available in field maps; however I don't know much more about changing which locators to use in Field Maps other than how you set up the web map itself in the web map settings. My issue is that Field Maps still wants users to sign in to the Portal account to use that custom geocoder, even though that service is publicly shared from our Portal. 

Does this answer your question?