Select to view content in your preferred language

Search/Query widgets triggering generatetoken after upgrade to 11.4

225
5
a month ago
Trevor_Hart
Frequent Contributor

We have recently upgraded from 11.1 to 11.4.

The search & query widgets for experience builder stopped working correctly and I noticed its trying to generate a token based on a token. This creates a 400 error.

Sometimes I'll see a result after a while but mostly it just sits there spinning.

Anybody seen this before?

Trevor_Hart_1-1743019185958.png

Trevor_Hart_2-1743019558795.png

 

 

 

0 Kudos
5 Replies
JeffreyThompson2
MVP Frequent Contributor

I have not seen this one. But I suspect it may be related to a known issue. Please answer the following questions:

  1. Are you using the version installed in Enterprise or connecting on Developer Edition?
  2. Does your organization use SSO?
  3. Do you have an Add Data Widget in your project? If so, check if it is connecting to Enterprise data?
GIS Developer
City of Arlington, Texas
0 Kudos
Trevor_Hart
Frequent Contributor

Thanks for the reply. Its an interesting issue.

It is the version included with Enterprise 11.4, no it doesnt include the add data widget.

A new EXB app with a new Web Map has the same behaviour.

The site uses SAML but it happens with built in users too.

0 Kudos
Trevor_Hart
Frequent Contributor

Actually its not specific to the widgets, even just opening the app results in the same behaviour.

We've logged a ticket with Esri.

0 Kudos
AndreLoerch
Occasional Contributor

I'm encountering this same issue using Experience Builder Developer version 1.16, with Enterprise data (map services) and access via SAML (SSO with Okta) in Portal. This issue so far seems to only impact me (the developer of the app) and not the other users of the app. We've deployed it in IIS.

I'm seeing hundreds/thousands of generateToken messages with the same response shared by the OP. 

If this is or may be a known issue, I'd be grateful for more details on it. Thanks! 

0 Kudos
Trevor_Hart
Frequent Contributor
We’ve logged a ticket with Esri. So far no resolution.