topic Re: Credential Banner popping up when opening an Experience Builder App (Started after AGOL Update on Feb 26, 2026) in ArcGIS Experience Builder Questions

Credential Banner popping up when opening an Experience Builder App (Started after AGOL Update on Feb 26, 2026)

tshafer — Fri, 27 Feb 2026 19:14:57 GMT

I created an Experience Builder app and have been testing it with a few users over the past few weeks. One of my testers tried to open the application today and was shown a Credentials banner and will not let him get into the app. This user is a Mobile Worker and has been able to get into the app up until the new AGOL update yesterday.

I changed him to a Creator with editing, and he still got the same issue. I then assigned a Mobile Worker to separate account and tried it myself and got the same results.

Is anyone having an issue with this? I would assume that a Mobile Worker should still be able to open an Experience application.

Re: Credential Banner popping up when opening an Experience Builder App (Started after AGOL Update on Feb 26, 2026)

StephanieW — Fri, 27 Feb 2026 22:32:04 GMT

Hi @tshafer this is likely related to how data used in the application is added or shared. It would be best if you are able to create a support case for us to take a closer look at the configuration, sharing settings, and potentially the web traffic to identify what specifically is triggering this. https://support.esri.com/en-us/contact

Re: Credential Banner popping up when opening an Experience Builder App (Started after AGOL Update on Feb 26, 2026)

Wei_Ying — Sat, 28 Feb 2026 02:09:06 GMT

@tshafer it looks like the user do not have access to the map data.
Would you check if the data sharing ever changed?
This banner only shows when the app contains resource requires credential.

Re: Credential Banner popping up when opening an Experience Builder App (Started after AGOL Update on Feb 26, 2026)

AndrewSpencer — Tue, 03 Mar 2026 03:17:27 GMT

I started receiving the same message a couple of weeks ago - I hadn't seen it before that. This was for a public Exp Builder app where everything was shared publicly, though the connection to a secure map service had the credentials saved in the AGOL 'item'. Oddly not all our users experienced the issue - for instance I got the prompt on my phone but not on my PC. We wondered if the issue was CORS and browser related.

After following the permissions chain, what eventually seemed to fix it was recreating the 'item' in AGOL then updating the map and checking the app which luckily were fairly simple.

Re: Credential Banner popping up when opening an Experience Builder App (Started after AGOL Update on Feb 26, 2026)

Wei_Ying — Tue, 03 Mar 2026 05:24:21 GMT

Hi @AndrewSpencer if you are still seeing this issue, could you share the public app and we will take a look.

Re: Credential Banner popping up when opening an Experience Builder App (Started after AGOL Update on Feb 26, 2026)

tshafer — Tue, 03 Mar 2026 14:41:01 GMT

@Wei_Ying There are only four files in this group. There are four members as well. I have a similar project that has the same exact sharing, and it is working.

Me, being an admin, can access the application with no banners.

Re: Credential Banner popping up when opening an Experience Builder App (Started after AGOL Update on Feb 26, 2026)

AndrewSpencer — Wed, 04 Mar 2026 00:10:21 GMT

@Wei_Ying Thanks but we're back in business as of now. The app is embedded in this page: Research Bricks. Recreating the AGOL feature layer item to proxy the map service seemed to do the trick. I recall that even when the embedded app was prompting for credentials, it actually worked fine for our users when opened in its own window/tab so I guess that doesn't help the OP much.

Re: Credential Banner popping up when opening an Experience Builder App (Started after AGOL Update on Feb 26, 2026)

tshafer — Wed, 04 Mar 2026 14:24:28 GMT

The banner is now gone. We shared the data again and removed everyone that was associated with that group. When we tried again, it worked. Not sure which task did the trick, but we are back in business.

Thanks for all the input.