question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Respone of GET-Request gets too long

See original GitHub issue

So I do a standard GET-Request:

        AndroidNetworking.get(url)
                .setPriority(Priority.HIGH)
                .build()
                .getAsJSONArray(new JSONArrayRequestListener() {

                    @Override
                    public void onResponse(JSONArray response) {

                        BackendService.onTaskComplete(response.toString(), type, null);
                    }

                    @Override
                    public void onError(ANError error) {

                        BackendService.onTaskComplete(null, type, error);
                    }
                });

After restarting the app several times in development and making each time one GET-Request, the GET-Request suddenly started to get really slow. I have to wait more or less 1-2 minutes until onResponse gets called. It is not the problem of the backend, because by calling the URL in other ways I get instantly a response.

While waiting the console is slowly increasing its code cache, maybe this is a hint:

I/art: Do partial code cache collection, code=31KB, data=26KB
I/art: After code cache collection, code=29KB, data=25KB
I/art: Increasing code cache capacity to 128KB
I/art: Do partial code cache collection, code=58KB, data=56KB
I/art: After code cache collection, code=57KB, data=56KB
I/art: Increasing code cache capacity to 256KB

When I uninstall the app, the requests are fast as usual again after some while the problem repeats.

Issue Analytics

  • State:open
  • Created 6 years ago
  • Reactions:1
  • Comments:9 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
molavycommented, Jul 24, 2018

so, in this case it’s better name it slow android networking 😃

0reactions
amitshekhariitbhucommented, Jul 26, 2018

Yes, I mailed you. Please revert the url.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Size of the request headers is too long - Stack Overflow
In windows system generally this error occurs due to the default header size limits set in the http.sys service.
Read more >
431 Request Header Fields Too Large - HTTP - MDN Web Docs
The HTTP 431 Request Header Fields Too Large response status code indicates that the server refuses to process the request because the request' ......
Read more >
How To Fix HTTP Error 431 Request Header Fields Too Large
Learn how to fix the HTTP Error 431 Request Header Fields Too Large message using four simple troubleshooting tips.
Read more >
HTTP Error 431: 3 Ways to Fix Request Header Fields Too ...
Follow this tutorial to learn three methods to fix the HTTP Error 431: Request Header Fields Too Large response status code.
Read more >
What does it mean when 'HTTP Error 400. The size of ... - Quora
It means that error is due to bad programming of the client system or the Web server & server failed to understand the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found