There appears to be a difference in behavior between Backendless Java cloud code that is deployed and cloud code that is being debugged through the “CodeRunner” construct.
When making the following two function calls within our Java cloud code within an endpoint requested by our mobile application with a valid logged-in-user token, if the cloud code is “deployed” and running solely in Backendless, neither is returning the expected result. The value returned by “loggedInUser()” is “null” and the value returned by “isValidLogin()” is “false”.
If, however, the cloud code handling the request from the mobile application is currently running through the “CodeRunner” debugging structure, both calls properly return their expected values - the valid logged in user ID and “true”, respectively.
String userId = Backendless.UserService.loggedInUser();
boolean isValidLogin = Backendless.UserService.isValidLogin();
Everything was working as expected with the deployed cloud code prior to some time on 05/22/2023, but now no deployed cloud code is properly processing the requesting user context. Redeployment of the cloud code has not alleviated the issue.
In both the “CodeRunner” context cloud code and the deployed cloud code, the following functions are returning the same - and seemingly accurate - values, including the same user token header.
InvocationContext.getHttpHeaders();
InvocationContext.getUserId();
InvocationContext.getAppId();