Open dhunink opened 9 years ago
Suggested irl by @mvhulzen: could be the regular design of the API. A insecure request is made while the desired action requires authentication, so a error is thrown. In response a second call is made, this time secured with a token. If the above is true, a fix is not needed but could be accomplished by adding a secure token on the first request and force the API call to include that token.
The following function returns Error: token required Why sin't the EsriRequest sending a token when queuing the featureserivce?