[MAJOR BUG] Infinite requests after closing popup

559
8
Jump to solution
01-11-2021 08:16 AM
Labels (2)
BrunoSousa1
New Contributor III
Hi,

I believe I've found a major bug in ArcGIS Experience Builder Developer Edition.
When you have a text or embed widget linked to data and try to interact with the data (selecting it and closing the popup) it starts sending infinite requests until your browser loses the connection with the layers due to Insufficient resources.

Requests URL: query?f=json&objectIds=0&outFields=*&spatialRel=esriSpatialRelIntersects&token=

How to replicate the issue:
  1. Start an existing or new Experience Builder Developer project;
  2. Add a map widget. Select a map with layers.
  3. Add a text widget (or Embed widget). 
  4. Connect the widget to data.
  5. Edit the text/embed widget by adding Dynamic Content.
  6. Save it and run it on Preview mode.
  7. Select a feature and close the popup.
What I've tried:
  1. Reinstalling ArcGIS Experience Builder;
  2. Installing on an Ubuntu computer;
  3. Tested with both ArcGIS Online and Enterprise Portal maps and layers;
  4. Replacing the ExperienceBuilder Application (used to authenticate) within ArcGIS Online and ArcGIS Enterprise;
  5. Two other coworkers could replicate the same issue in different machines.
2 Solutions

Accepted Solutions
DavidMartinez
Esri Regular Contributor

Hi Bruno,

I was able to reproduce this issue in 1.2 as well. This has been fixed in our 1.3 release. It will be available at the end of this month. Again, thanks for letting us know about this bug.  

 

Cheers,

 

David

View solution in original post

DavidMartinez
Esri Regular Contributor

Hi Ualas,

As a workaround, you can change the URL of the JS API  to use 4.18 instead of 4.17. To change it search for 'arcgisJSApiURL' in these files and replace the URL:

  • client/dist/experience/index.html

  • client/dist/template/index.html

  • client/dist/site/index.html

  • client/dist/builder/index.html

 

Cheers,

 

David

 

View solution in original post

8 Replies
UalasRohrer
New Contributor III

I'm having the exact same issue.

0 Kudos
DavidMartinez
Esri Regular Contributor

Thanks, Bruno we appreciate you finding this and bringing it to our attention. Will take a look and reply back to this post.

 

Cheers,

 

David

BrunoSousa1
New Contributor III

Thanks, David. Sorry about the alarmism. My team and I had this presentation of an App today, so this bug was making it hard for us to show the App we built.

We could not solve this at all and we tested multiple machines, multiple data types, and multiple data sources... 

0 Kudos
DavidMartinez
Esri Regular Contributor

Hi Bruno,

I was able to reproduce this issue in 1.2 as well. This has been fixed in our 1.3 release. It will be available at the end of this month. Again, thanks for letting us know about this bug.  

 

Cheers,

 

David

View solution in original post

BrunoSousa1
New Contributor III

Awesome. Thanks for letting me know. I'll will mark it as solved.

0 Kudos
UalasRohrer
New Contributor III

Hello @DavidMartinez , I'm wondering if it would be possible for you to share the fix. I have to present the app and I'm afraid the stakeholders can't wait until the end of the month for the new version.

Thank you,

Ualas B.

0 Kudos
DavidMartinez
Esri Regular Contributor

Hi Ualas,

As a workaround, you can change the URL of the JS API  to use 4.18 instead of 4.17. To change it search for 'arcgisJSApiURL' in these files and replace the URL:

  • client/dist/experience/index.html

  • client/dist/template/index.html

  • client/dist/site/index.html

  • client/dist/builder/index.html

 

Cheers,

 

David

 

View solution in original post

UalasRohrer
New Contributor III

Thank you David!