Skip to content

Clean up push registration retry logic#1826

Merged
SessionHero01 merged 8 commits intofeature/onion-request-refactorfrom
push-retry
Jan 14, 2026
Merged

Clean up push registration retry logic#1826
SessionHero01 merged 8 commits intofeature/onion-request-refactorfrom
push-retry

Conversation

@SessionHero01
Copy link
Collaborator

No description provided.

…into feature/onion-request-refactor

# Conflicts:
#	app/src/main/java/org/session/libsession/messaging/sending_receiving/notifications/PushRegistryV1.kt
#	app/src/main/java/org/thoughtcrime/securesms/configs/ConfigToDatabaseSync.kt

val apiResponseIterator = apiResponses.iterator()

intermediateResults.forEachIndexed { idx, result ->
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we get fewer results than expected from the server, isn't it possible to misalign the results?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the server MUST give us exactly the same number of result back, otherwise we have no way to know if a request is success or not. Think of it this way: we send an array of request to the server, you'd expect to get the same sized array back, it is an assumption that we have made prior to the network refactoring.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will add an explicit check for this server behavior and we will reject the whole call if the server is naughty

@SessionHero01 SessionHero01 merged commit f394159 into feature/onion-request-refactor Jan 14, 2026
4 checks passed
@SessionHero01 SessionHero01 deleted the push-retry branch January 14, 2026 03:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants