-
Notifications
You must be signed in to change notification settings - Fork 113
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
Error: Fitness api can't request data for big time intervals [E/JavaBinder: !!! FAILED BINDER TRANSACTION !!!] #57
Comments
Hi, i'm facing the same issue. The api cannot handle large runs. Did you find any solutions? |
Hi, I'm also facing the same issue, My google fit app have lots of data over the last 3 months. I tried to get these all data used 'setTimeRange' in DataReadRequest, which returns nothing, I mean the data between the range is nearly 1800(approx), and there is no exception printed in logs, also any callbacks not triggered. So we struggle to get total data from GoogleFit. I think the large data responses don't parsable. I request a pagination functionality from the server and the problem may be solved. |
No worries |
same issue. I have 86400 record in 2 months. But return error when request: 5022: Cannot bucket into more than 86400 intervals. |
Hello! My google fit app doesn't work for 2 months.
I started to debug the application and I was able to find these errors from adb logcat:
Please pay attention to the line "FAILED BINDER TRANSACTION !!! (parcel size = 1330200" - google fit can't get the data from the android service because the response is too large to be returned through IPC.
Also, I'm developing an application that uses the fitness api and also I noticed that gms Task api doesn't return anything and even doesn't call "onComplete" listener in similar cases when google fit service can't deliver the result to a requester.
I think a reading task should be completed anyways if Binder fails for some reason.
The text was updated successfully, but these errors were encountered: