fix: issue 139 by bump FIT SDK version to latest#140
Merged
Conversation
raditzlawliet
approved these changes
Jan 5, 2026
Member
raditzlawliet
left a comment
raditzlawliet
left a comment
There was a problem hiding this comment.
I plan to bump to the latest SDK beforehand. Anyway, thank you for doing this.
Member
Author
|
Thanks @raditzlawliet, it's a sudden update due to the raised issue. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issue: #139 due to default behaviour on FIT SDK Encoder that removes fields with invalid values. It actually has been removed in v0.27.0 (specifically by this PR muktihari/fit#605) so bumping the version will fix the issue.