Solved! Go to Solution.
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
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
I'm having the exact same issue.
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
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...
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
Awesome. Thanks for letting me know. I'll will mark it as solved.
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.
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
Thank you David!