Added new API after July update and requires session token mapping

I have a number of API Express services connected to an Azure database. All of the services reference the Appery session token. Until this new API service I've never needed to map a copy of the session token to its related parameter in the "before send" mapping. Appery always mapped it before calling the API...

My existing API services continue to work fine with it unmapped -- Appery continues to assign it automatically when these APIs are invoked. But not the new service drawn into the app after the July update. (I noticed the service has a different icon in the app. the others have a gear and it has "api" in a rectangle...) The new one will not succeed unless I keep a copy of the session token and map it to the parameter in the "before send" mapping.

Thanks,

-Ron
1 person has
this problem
+1
Reply