Skip to content

Loading query failed: 500 Internal server error #669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sksaibabavali opened this issue Feb 28, 2019 · 6 comments
Closed

Loading query failed: 500 Internal server error #669

sksaibabavali opened this issue Feb 28, 2019 · 6 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@sksaibabavali
Copy link

sksaibabavali commented Feb 28, 2019

When I debug I am getting data But for the same data I am trying to see in Browser it is telling
Loading query failed: 500 Internal server error.
This is my entity

@Entity
public class Certify {

    public int Driver_Id;
    public int Server_Id;
    @io.objectbox.annotation.Id
    public long id;
    public String updatedAt;
    public String createdAt;
    public String ELogDate;
    public int SyncRequired;
}
@greenrobot
Copy link
Member

You are referring to Object Browser I assume; could you please check the logs (logcat) for error info?
Also, which version are you using?
Thanks.

@Joeywp
Copy link

Joeywp commented Mar 1, 2019

I'm having the same problem with the browser (v2.3.3), happens only on the emulator though, works fine on my real Pixel 2 XL. It basically gives this warning:
W/Box: Exception thrown: Do not use vector-based find on 32 bit systems with big objects

Sometimes I also get this warning, though it might not be from objectbox:
Unexpected CPU variant for X86 using defaults: x86

I'm running the emulator as: Pixel 2 API 28 with the Android 9.0 (Google Play) image on CPU/ABI x86

@greenrobot
Copy link
Member

As indicated by the log message; this should be limited to 32 bit systems. So as a workaround, you could use a 64 bit emulator. We'll likely provide a fix with the next version.

@greenrobot-team greenrobot-team self-assigned this Mar 4, 2019
@greenrobot-team greenrobot-team added the bug Something isn't working label Mar 11, 2019
@greenrobot-team greenrobot-team added this to the 2.4.0 milestone Mar 11, 2019
@greenrobot-team
Copy link
Member

greenrobot-team commented Mar 11, 2019

We could verify this issue and have developed a fix. It will be available with the next update. Thanks for reporting!

The issue occurs if one of the properties of an entity, e.g. a String property, has a value bigger than 4000 bytes (e.g. a very long text). The data browser then fails to query your entities when running on a 32-bit system, like the x86 Android emulators.

-ut

@greenrobot-team greenrobot-team modified the milestones: 2.4.0, 2.3.4 Mar 19, 2019
@greenrobot
Copy link
Member

2.3.4 has been released; please let us know if that fixed it for you, thanks!

@sksaibabavali
Copy link
Author

Super it is working now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants