Latest Contributions by XiaodongWang

Verified on dev 1.16, I cannot reproduce it any more, it should be fixed now. ... View more

I think the following solution can solve the problem: 1. In your custom widget, get the user session before request your own API. 2. Get the token and username from the session, and use them as parameters to request your own API. 3. After your REST server receives the request, use the token and username to access the address: https://www.arcgis.com/sharing/rest/community/users/username?f=json&token=... (www.arcgis.com or portal url) to verify the user's identity. If the user is valid, respond to the API request. import { SessionManager } from 'jimu-core' const session = SessionManager.getInstance().getMainSession() const username = session.username const token = session.token   ... View more

The app embedded in iFrame uses popup login. This is due to the security limitation of OAuth2, the app embedded in iFrame can only use popup login. The OAuth2 is used by default if the non-public resource supports OAuth2 (pop up if in the iFrame), otherwise the inside prompt login is used. However, ExB does not provide a way to change the login method (OAuth2 or inside prompt). ... View more

It should resolve the problem, but I can't guarantee it with 100% certainty. ... View more

So if I have already "1" when I extract my ZIP, what I have to do ? change it to "0" ? or "2" ?  0 and 2 are both OK, or even any number, as long as they are not 1. ... View more

Download new version, unzip, copy, paste and replace the old app in the 'folder called "App" ', then  1, Rename  cdn/0  to  cdn/1 . 2, Open  index.html  on your application's root folder. Change  <base href="./cdn/0/"/ >  to  <base href="./cdn/1/"/ >  . Change the  build Number = '0'  to  build Number = '1' . Make sure the number (CDN folder and build) is different from the previous app. what does mean "cache index.html" it's an attribute to modify ? This can be set in ‘web.config’,  it does not have to be changed, just use the default value. ... View more

This problem might be caused by Service worker cache , please try steps and see if it solves the problem. ... View more

On the other hand, not setting the clientId in the config.json can also cause this problem. Check out steps 4-6 here. ... View more

If you already have a token of portal, you can create a session and register it into ExB. Reference code: import { SessionManager } from 'jimu-core' import { UserSession } from '@esri/arcgis-rest-auth' const session = new UserSession({ portal: portalUrl, //https://www.arcgis.com/sharing/rest/ clientId: clientId, token: token, tokenExpires: new Date(tokenexpires), ssl: true, username: username }) SessionManager.getInstance().addOrReplaceSession(session)   BTW: Which version of ExB dev edition are you using? ... View more

There is no event for token expiration yet, do you think it would be ok if use the polling solution? setInterval( () => { const session = SessionManger.getInstance().getSessionByUrl(url) // check session.tokenExpires here. }, 10*1000)   ... View more

Agree with abureaux, I think this problem is caused by the lack of clientId. Please double check that the clientId has been set on the config.json. Since the app is deployed under portal, you can try clientId 'experienceBuilder'. ... View more

I think that cannot remove the layer is not caused by the LayerList widget or WAB, is there any console errors? ... View more

Set 'layerObject._wabProperties.isTemporaryLayer' property to the new layer before it's added to the map. newLayerObject._wabProperties.isTemporaryLayer = true; map.addLayer(newLayerObject); ... View more

Pascual, agree with you, hiding layers cannot resolve this problem, LayerList widget should have same behavior with Map Viewer TOC. ... View more

Karsten, Robert is right, this problem is caused by an issue: If there are too many templates in the Edit widget, an error occurs that no template shows in the widget's panel #5703 This issue has been fixed by edition Online4.2, dev 2.1 and Portal10.5. So I think, you have to upgrade to Portal10.5 to fix this problem. ... View more