You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
Restores the legacy `isNewApp -> newInstance` behavior in the migrated
`SendbirdProvider` flow.
## Why
During the `SendbirdProvider` migration, the old `useConnect` logic that
detected app changes and passed `isNewApp` into SDK initialization was
removed. The migrated path left `newInstance` commented out in
`initSDK`, which regressed the previous behavior.
## What changed
- Reintroduced legacy `appId` change tracking in
`SendbirdContextManager`
- Propagated `isNewApp` through `actions.connect()` into `initSDK()`
- Restored `newInstance: isNewApp` in `SendbirdChat.init()`
- Added regression coverage for provider behavior, connect propagation,
and SDK init params
## Validation
- `yarn test -- src/lib/Sendbird/__tests__/SendbirdProvider.spec.tsx
src/lib/Sendbird/__tests__/useSendbird.spec.tsx
src/lib/Sendbird/__tests__/utils.spec.ts --runInBand`
- `yarn eslint src/lib/Sendbird/context/SendbirdProvider.tsx
src/lib/Sendbird/context/hooks/useSendbird.tsx src/lib/Sendbird/utils.ts
src/lib/Sendbird/__tests__/SendbirdProvider.spec.tsx
src/lib/Sendbird/__tests__/useSendbird.spec.tsx
src/lib/Sendbird/__tests__/utils.spec.ts`
## Impact
This restores the pre-migration SDK initialization behavior when
switching to a different `appId`, while keeping regression tests around
the migrated provider path.
0 commit comments