Commit cbb01af
fix(iv): wake queue on login(sameId, freshJwt) refresh path
Same-user-id login with a fresh JWT (the documented post-401 refresh
path) was storing the new token but never calling forceExecuteOperations,
so ops parked by hasValidJwtIfRequired stayed deferred until something
else woke the queue. updateUserJwt already does this correctly; reference
#2599 LoginHelper does too. Match that design — drop redundant
if (jwtBearerToken != null) guards (putJwt no-ops on null) and call
forceExecuteOperations unconditionally on the same-id branch so the
queue drains as soon as the developer supplies a fresh token.
Extend the existing same-id+JWT test to verify forceExecuteOperations
fires.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent 1e8d3f2 commit cbb01af
2 files changed
Lines changed: 10 additions & 9 deletions
File tree
- OneSignalSDK/onesignal/core/src
- main/java/com/onesignal/user/internal
- test/java/com/onesignal/user/internal
Lines changed: 7 additions & 8 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
37 | 37 | | |
38 | 38 | | |
39 | 39 | | |
40 | | - | |
41 | | - | |
42 | | - | |
43 | | - | |
44 | | - | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
45 | 45 | | |
46 | 46 | | |
47 | 47 | | |
48 | 48 | | |
49 | 49 | | |
50 | | - | |
51 | | - | |
52 | | - | |
| 50 | + | |
| 51 | + | |
53 | 52 | | |
54 | 53 | | |
55 | 54 | | |
| |||
Lines changed: 3 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
331 | 331 | | |
332 | 332 | | |
333 | 333 | | |
334 | | - | |
| 334 | + | |
| 335 | + | |
335 | 336 | | |
336 | 337 | | |
| 338 | + | |
337 | 339 | | |
338 | 340 | | |
0 commit comments