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.
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
chore: apply API v8 changes - WPB-15840 #2570
base: develop
Are you sure you want to change the base?
chore: apply API v8 changes - WPB-15840 #2570
Changes from 9 commits
58a86c3
6b784ce
fd1d8ee
370520b
ab99673
693bf86
5b853a4
3060699
e02a9e6
a256f89
24aec65
51eca5b
0c92bd2
2936cd7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check failure on line 42 in wire-ios-request-strategy/Sources/Request Strategies/MLS/Actions/CountSelfMLSKeyPackagesActionHandler.swift
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am I correct? https://wearezeta.atlassian.net/wiki/spaces/ENGINEERIN/pages/1593671681/API+changes+v7+v8
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it looks like it. The optional query parameter was added from v5 but we never used it. I think it's fine to start using if from v8. The question is... which cipher suite should we pass?
Check failure on line 100 in wire-ios-sync-engine/Source/Data Model/Conversation+MessageDestructionTimeout.swift
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest to fallback to the local domain, which there should be (even though it's optional 🙃).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't crash the app if there was no domain
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion: also here it'd be good to fallback on the local domain.
Check failure on line 55 in wire-ios-sync-engine/Source/Data Model/Conversation+ReadReceiptMode.swift
Check failure on line 63 in wire-ios-sync-engine/Source/Synchronization/Strategies/RegistrationStrategy.swift
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we don't specifically handle these new errors, does the registration status still consider it an error? The login and registration flows are being re-written so probably doesn't make much sense to handle these errors if not absolutely necessary.
Check failure on line 80 in wire-ios-sync-engine/Source/Synchronization/Strategies/TeamInvitationRequestStrategy.swift
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there something to handle or would it end up as an error log?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, I don't think we have tickets or design changes to handle this error