e7c31f9270
fix: revert defensive null checks in signal.ts that prevented Signal session creation
...
The previous PRs (124-129) replaced non-null assertions (!) with defensive
null checks + continue statements in parseAndInjectE2ESessions and
extractDeviceJids. This caused ALL prekey bundles to be silently skipped
because the continue statements would trigger whenever any sub-field
appeared missing (even though WhatsApp always sends complete bundles).
Result: no Signal sessions were created after QR scan, causing
"SessionError: No sessions" when trying to send messages.
Reverted to the original Baileys pattern using non-null assertions,
which matches the upstream reference (infinitezap/Teste_InfiniteAPI).
https://claude.ai/code/session_01XaA7GwNaB6azTHFYQ8WEpB
2026-02-09 03:50:36 +00:00
1c9fb86cc3
fix(types): remove non-null assertions in remaining 12 files
...
Files fixed:
- messages-media.ts: stream/buffer guards, file path validation
- decode-wa-message.ts: message field guards, optional chaining
- version-cache.ts: narrowing after null checks
- jid-utils.ts: split result guards, user fallbacks
- communities.ts: attrs fallbacks with ?? operator
- sticker-pack.ts: response guards
- business.ts: attrs guards
- socket.ts: onClose guard, pairingCode guard, creds.me guard
- event-buffer.ts: null guards
- signal.ts: null guards
- encode.ts (WAM): id null check with continue
- upstream history.ts: conversations/pushnames null guards
All 26 files across the project are now corrected.
Total: ~248 non-null assertions replaced with proper null guards.
https://claude.ai/code/session_01E2cfX1N3sJgCJBTvzGazSG
2026-02-09 00:32:04 +00:00
29318cf6c2
chore: lint and re-organize
2025-10-20 00:37:37 +03:00
2e47d4b66b
messages-send, signal: improve hosted device support + patch cache
2025-10-19 23:56:05 +03:00
ca50338be1
signal: process devices sequentially
2025-10-18 20:28:03 +03:00
a3ec28e051
fix error and linting ( #1888 )
...
* fix: build
* fix: linting
* fix: cast type
2025-10-08 09:27:43 +03:00
e9198b773e
lid-mapping,signal: improvements to hosted device support in lid map
2025-10-08 02:39:02 +03:00
9e4dbb2e22
signal,messages-send,libsignal: properly parse and ignore hosted devices
2025-10-08 02:25:26 +03:00
b8f695cc82
general: linting
2025-10-02 21:41:12 +03:00
0af6c2f298
general: preliminary support for @hosted + Usync LID stuff
2025-10-02 19:38:47 +03:00
ae456cb342
fix: send message speed, lid logic, remove messages-send useless functions ( #1794 )
...
* fix: remove redundant migration
* fix: remove deduplicatelidpnjids
* fix: assertsessions complexity
* fix: assertsessions call
* fix: remove getencryptionjid
* fix: add wirejid to injecte2esession, remove libsignal lid migration
* fix: logger lid-mapping
* fix: injecte2esession decoded approach
* fix: changes made by @AstroX11
* fix: lint
* fix: lint
* fix: lint
* Revert "fix: injecte2esession decoded approach"
This reverts commit 4e368296ed084398b8a173ec117dc2478e481748.
* fix: centralize getlidforpn calls in messages-send
* fix: add resolvechunklids to signal
* fix: remove useless arrays
* fix: assertsessions logic
* fix: lint
* Revert "fix: assertsessions logic"
This reverts commit 65b0730891c91573edcab1c96af010db54382fba.
* fix: remove onwhatsapp fallback to prevent rate limit, migrate sessions when lid-map is created, new migration logic and user devices key
* fix: migrate session devices, socket creation
* fix: add back decryptionjid validation
* fix: add resolveSignalAddress to get lid
* fix: type error migration
* fix: lint
* fix: device level cache, proposed changes
2025-09-26 06:53:15 +03:00
194b557b0f
fix: optimize LID migration performance and introduce cache ( #1782 )
...
* chore: lid-map cache, bulk migration, fixes
* fix: type error
* fix: signalrepository with lid type, remove check from assertsessions, lid-mapping store level deduplication
* fix: migrations logs
* fix: remove migrationsops lenght check
* fix: skip deletesession if cached or existing migrations
* chore: remove check migrated session
* fix: remove return null loadsession
* fix: getLIDforPN call and jidsrequiringfetch
* fix: longer lid map cache TTL
* fix: lint
* fix: lid type
* fix: lid socket type
2025-09-14 21:58:59 +03:00
787aed88b8
project: Move to ESM Modules
2025-07-17 13:54:17 +03:00
fa706d0b50
chore: format everything
2025-05-06 12:10:19 -03:00
f1f49ad2c8
Usync: Barebones Usync Protocol support ( #960 )
...
* feature(feature/usync-mex): initial commit
* chore: fix merge commit
* chore:lint
2024-12-22 23:38:41 +02:00
18ac07df8e
lint: 0 warnings left
2024-10-14 05:15:10 +03:00
bd20fb631b
Run repository.injectE2ESession in chunks ( #881 )
2024-06-30 06:06:42 +03:00
fe1d0649b5
feat: add signal repository + tests
2023-03-18 12:25:47 +05:30
c5917364ba
chore: add stronger lint rules
2022-08-18 10:37:40 +05:30
2549d10be9
feat: update proto
...
The new proto extract has a bunch of breaking changes, so if you were using the raw proto in your code somewhere -- then you may have to update your code to make it work with the new proto
!BREAKING_CHANGE
2022-08-01 10:43:04 +05:30
40a1e268aa
feat: add "strictNullChecks"
2022-07-09 10:20:07 +05:30
7863c0e4c2
perf: nicer "shouldIncludeDeviceIdentity" flag computation
2022-06-17 13:16:41 +05:30
2720879545
chore: update "generateSignalPubKey" function
2022-04-18 08:23:32 +05:30
02265fd7f9
refactor: upload more pre-keys + use pure function
2022-04-13 00:02:10 +05:30
de7d1002a9
lint: stricter linting rules
2022-03-01 16:32:14 +05:30
8f11f0be76
chore: add linting
2022-01-19 15:54:02 +05:30
2b8256d56b
feat: cleaner auth state management + store SK keys
...
!BREAKING_CHANGE
2021-12-11 17:54:38 +05:30
d9cfed64ff
fix: bad request on sending messages in some cases
...
Issue source found out by @jackcokk
2021-12-03 15:20:17 +05:30
3d0704a317
feat: cleaner auth state management
...
1. removes the "auth-state.update" event since it was bloated and fairly unnecessary
2. adds "creds.update" event that only sends the updated properties of the auth credentials
3. ensure the auth creds are not mutated anywhere, but only with the "creds.update" event
4. Separates the signal credentials from the auth credentials (kinda in progress)
5. in memory key store requires a save function to let one know when to save the keys
!BREAKING_CHANGE
2021-11-20 16:21:56 +05:30
dee815448b
feat: cache user devices
2021-11-07 19:51:14 +05:30
cacbaa37f2
exclude my device from message send
2021-10-09 19:29:10 +05:30
f1527a9f6b
separate out crypto utils
2021-09-23 22:37:33 +05:30
f267f27ada
finalize multi-device
2021-09-22 22:19:53 +05:30
Claude