Repository navigation
fix(api): drop zero session deadline handling from Session - #1175
Conversation
The backend now gives indefinite native sessions the same far-future deadline as the web 'maximum lifetime off' setting, so expire_at is never 0. Restore Session.expireAt to its required form and remove the zero-deadline docs and tests.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
What & why
The backend now gives indefinite native sessions the same far-future deadline as the web "maximum lifetime off" setting (
ExpiryTimeMax), soexpire_atis never0. This restoresSession.expireAtto its form before #960: required, with no default and no epoch-zero docs. It also removesSessionLifetimeTest, which only covered zero deadlines.hasMaximumLifetimewas already removed in #1165. Part of MOBILE-517.Checks
spotlessCheck, apiCheck (no API dump change), api unit tests, ui unit-test and e2e compile.
Screenshots / video
No UI or runtime change for responses the backend sends, so there is nothing to show on a device.
Summary by CodeRabbit