@mark-piller Hi, I am having this issue too on Android. After debugging, it looks like that Backendless is returning a lot of nulls (which first of all shouldn’t be the case), but the Backendless Android SDK is not handling this properly.
See this. Firebase registration fails, and the SDK tries to get a intValue (I guess a token or id or something), but it is null and the app crashes:
Another issue I keep finding, after logging in the BackendlessUser is like a blank object with none of the default values that I’ve set in my user schema. This means when I try to get a value out of the user object (which should always have values because defaults were set in the data table), I get a crash as there is a NullPointerException:
In general, a lot of responses from Backendless’ SDK are now returning dirty or incorrect data, which seems the SDK itself is not prepared to accept. Whether the response is empty, or the response has incorrect data. I can go on and list more examples if you want, but all I know is everything worked fine yesterday. Today, everything is crashing.
Here’s another example, just a simple getObjectCount for a data table’s items returns null. I would hope even if they couldn’t find any matches, the count would be 0 and not null. There has been some regression for sure.
I think its working properly now. Other users still testing the application but it seems to be working properly now. Could you please mention the reason for the error? (just so that I can communicate it properly with the backendless team in future, if further such incidents happen)
@Jeffrey_Sera Is your problem still reproducing now?
@Pranav_Patel our specialists are still working to ensure that the error does not occur again. We will report on the reasons for the failure at a later date.
Please create a small app that strictly demonstrates the issue with the login API.
We’re not seeing any issues with the API as you report, however, if you provide a small app that reproduces the issue, we will be happy to look into it.
Hi @mark-piller , I seem to have a very similar issue. I had a problem end of last week when I was away and users are now reporting problems using the app from about an hour ago. When looking at the debugger I am too getting null objects when I should be getting a BackendlessUser. Hope this helps.
I just ran a test where I log in a user and am getting BackendlessUser back. We really need a sample that reproduces the issue. Can you help with a sample, please?
But, It looks like if I call this. (Android)
if (Backendless.UserService.isValidLogin()) {
I get a null pointer crash with this message
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method ‘boolean java.lang.Boolean.booleanValue()’ on a null object reference
at com.backendless.UserService.isValidLogin(UserService.java:970)
