removing legacy field#216
Closed
reklis wants to merge 1 commit into
Closed
Conversation
Member
|
I can't seem to reproduce this issue when using a free account ( |
Member
|
update: I was able to reproduce this when using a paid account. Going to check whether the field is still required on free accounts. |
Member
|
okay as I suspected, if we remove the
so we'll need to conditionally include the field instead. |
Member
|
Created #220 to fix this. Closing this PR in favor of that one. Thanks for spotting the issue. |
kabiroberai
added a commit
that referenced
this pull request
May 17, 2026
Ref #216: the public API seems to now complain when passing in `capabilities`, but the field is still required when using the private API. Co-authored-by: sfusco <slf@stevenfusco.com>
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.
Tested on ios26