Crazy result from Backend Services

[Erick]

We're using Javascript SDK to retrieve data from our Backend Services database. But it's returning crazy results when authenticate an user or not. The Files is public for everyone (will be changed to shared soon). I will descibe the issue below.

At first, initialize the everlive object:
var everlive = new Everlive({ apiKey: 'KEY' });

At second, authenticate user:
everlive.Users.login('USER', 'PASSWORD', function (data) {

        everlive.Files.get()
            .then(function (data) {
                alert(data.result.length) // RETURNS 0 RECORDS
            },
            function (error) {
                alert(JSON.stringify(error));
            });

    }, function (error) {
        location.href = "login.aspx"
    }); 


If i remove the authentication, then the everlive will return 69 records from Files.
everlive.Files.get()
            .then(function (data) {
                alert(data.result.length) // RETURNS 69 RECORDS
            },
            function (error) {
                alert(JSON.stringify(error));
            });



After authenticate the user, the code below will return Item not found with code 801 but the file exists...
Works fine when not authenticate the user.

everlive.Files.getById("FILE").then(function (data) {
                       alert(JSON.stringify(error))
                    }, function (error) { alert(JSON.stringify(error)) })

[Erick]

Same story with deleting or updating one file

[Anton Dobrev]

Hello,

Unfortunately, we were unable to reproduce the issue on our side - the code is executing as expected. In order to proceed further with the resolution of the problem - could you please elaborate a little bit on the issue you are experiencing? We'll appreciate a runnable demo that illustrates the problem and any other information that will be helpful to get a fix on the issue.

I look forward to your reply.

Regards,
Anton Dobrev
Telerik

 

 

[Erick]

It seems be a same bug as described here:
http://www.telerik.com/forums/permissions-not-accessible

It's fixed by now.