After updating the Backendless SDK to the latest version yesterday, I am having this issue. When loading the user table as related query I just get a bad access error. When I set the field as autoload in the dashboard, I get the same error.
2016-05-04 20:05:44.821 SampleProject[24979:30063497] Loaded 3 seek objects
2016-05-04 20:05:44.821 SampleProject[24979:30063497] Total seek objects in the Backendless starage - 3
2016-05-04 20:05:44.821 SampleProject[24979:30063497] Seek name = Find me a good car insurance
2016-05-04 20:05:44.822 SampleProject[24979:30063497] Seek name = Logo design for my new business
2016-05-04 20:05:44.822 SampleProject[24979:30063497] Seek name = I need someone to book me a ticket to Paris
2016-05-04 20:05:44.822 SampleProject[24979:30063497] <BackendlessCollection> -> type: Seek, offset: 0, pageSize: 100, totalObjects: 3, data: (
"<Seek: 0x7fa5e0556dc0>",
"<Seek: 0x7fa5e055b8c0>",
"<Seek: 0x7fa5e055f7f0>"
), query: <BackendlessDataQuery> -> properties: (null), whereClause: (null), queryOptions: <QueryOptions> -> {
offset = 0;
pageSize = 100;
related = (
user,
location
);
}
This confirms that the API is functioning properly. The error must be somewhere in your code.
This is strange, and Im not really sure if it is from my code, because it was working fine before the update, that’s why I’m a bit confused here.
In my Seek class I have a property for the user of Users class. Here is the Users class, please have a look at it, maybe something has changed that I am not aware of:
Hang on, Users class? That’s a very bad idea to extend BackendlessUser. You should not do this. Instead you should use BackendlessUser and then rely on the following methods to get the property values: