refactor: 푸시 알림 토큰 로직 브릿지 방식으로 수정

[ff1451]

테스트를 위해 일단 머지 후 추후 재리뷰하겠습니다.

Summary by CodeRabbit

릴리스 노트

• 새로운 기능

  • 모바일(React Native) 연동 개선: 토큰 갱신, 로그인 완료, 로그아웃 시 모바일 쪽으로 상태 메시지 전송 추가

• 리팩토링

  • 모바일 환경에서의 푸시 토큰 등록 로직 제거
  • 인증 초기화 절차 단순화로 초기 로딩/인증 성능 향상

[coderabbitai]

📝 Walkthrough

Walkthrough

React Native WebView 브릿지 통합을 위해 웹 푸시 토큰 등록 로직을 제거하고, 인증 흐름에서 브리지로 메시지를 전송하도록 변경했습니다. accessToken 갱신 시, 로그인 완료 시, 로그아웃 시에 window.ReactNativeWebView.postMessage로 각각 TOKEN_REFRESH, LOGIN_COMPLETE, LOGOUT 타입 메시지를 전달합니다. notification 등록 함수는 브리지 존재 시 POST 호출을 건너뜁니다. 전역 타입 정의(global.d.ts)에 Window.ReactNativeWebView의 postMessage 시그니처를 추가했습니다.

Possibly related issues

• 관련 이슈: BCSDLab/KONECT_FRONT_END 이슈 133

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	PR 제목이 푸시 알림 토큰 로직을 브릿지 방식으로 리팩토링하는 변경사항을 명확히 요약하고 있으며, 실제 코드 변경(ReactNativeWebView 통합, 토큰 등록 흐름 제거 등)과 일치합니다.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 133-refactor-푸시-알림-토큰-로직-브릿지-형식-및-네이티브-처리로-변경

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 3

🧹 Nitpick comments (1)

src/apis/notification/index.ts (1)

5-5: 프로덕션 콘솔 로그는 제거 또는 로거로 대체를 권장합니다.

Line 5 로그는 운영 환경 노이즈를 만들 수 있어, 디버그 전용 로거/환경 분기 처리로 정리하는 편이 좋습니다.

수정 예시

-    console.log('RN WebView 환경: 웹에서 푸시 토큰 등록 생략 (네이티브가 처리)');
     return;

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/apis/notification/index.ts` at line 5, The console.log call printing "RN
WebView 환경: 웹에서 푸시 토큰 등록 생략 (네이티브가 처리)" should not remain as a plain production
log; replace it with a debug-level logger or gate it behind an environment
check. Locate the console.log in src/apis/notification/index.ts and either
remove it, change it to use the project's logger (e.g., processLogger.debug or
logger.debug) or wrap it with a NODE_ENV/__DEV__ conditional so it only runs in
non-production builds, ensuring no noisy logs in production.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/apis/client.ts`:
- Around line 166-168: The bridge postMessage call to window.ReactNativeWebView
in the token refresh path must not be allowed to throw and trigger the outer
catch that resets auth; wrap the
window.ReactNativeWebView.postMessage(JSON.stringify({ type: 'TOKEN_REFRESH',
accessToken: newAccessToken })) call in its own try/catch and swallow or
non-fatally log any error (do not rethrow), so bridge delivery failures do not
cause authentication initialization/redirect; ensure you keep the original
payload and only affect error handling around
window.ReactNativeWebView.postMessage.

In `@src/pages/User/MyPage/hooks/useLogout.ts`:
- Around line 13-15: In the useLogout hook, the bridge call
window.ReactNativeWebView.postMessage can throw and prevent the rest of the
logout sequence (clearAuth() and navigate('/')) from running; wrap the
postMessage call in a try/catch (or promise catch) so any exception is
caught/logged but does not stop execution, then always call clearAuth() and
navigate('/') after the bridge attempt; specifically update the block that
references window.ReactNativeWebView.postMessage to run inside try {
window.ReactNativeWebView.postMessage(JSON.stringify({ type: 'LOGOUT' })) }
catch (e) { /* log or ignore */ } so clearAuth() and navigate('/') run
unconditionally.

In `@src/stores/authStore.ts`:
- Around line 37-39: The postMessage call to window.ReactNativeWebView with the
LOGIN_COMPLETE payload (window.ReactNativeWebView.postMessage(JSON.stringify({
type: 'LOGIN_COMPLETE', accessToken }))) is throwing and bubbling into the
surrounding catch, which rolls back the successful auth state; wrap this bridge
call in its own try/catch (or check for existence and guard it) so any
exceptions are swallowed/logged locally and do not rethrow, ensuring the auth
success path in authStore (the surrounding login flow) is not invalidated by
bridge failures.

---

Nitpick comments:
In `@src/apis/notification/index.ts`:
- Line 5: The console.log call printing "RN WebView 환경: 웹에서 푸시 토큰 등록 생략 (네이티브가
처리)" should not remain as a plain production log; replace it with a debug-level
logger or gate it behind an environment check. Locate the console.log in
src/apis/notification/index.ts and either remove it, change it to use the
project's logger (e.g., processLogger.debug or logger.debug) or wrap it with a
NODE_ENV/__DEV__ conditional so it only runs in non-production builds, ensuring
no noisy logs in production.

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3f97cee and 32ca6a9.

📒 Files selected for processing (5)

• src/apis/client.ts
• src/apis/notification/index.ts
• src/global.d.ts
• src/pages/User/MyPage/hooks/useLogout.ts
• src/stores/authStore.ts

[coderabbitai]

♻️ Duplicate comments (1)

src/stores/authStore.ts (1)

37-43: 이전 리뷰 피드백 잘 반영됨 — LOGIN_COMPLETE 브릿지 호출이 인증 상태를 롤백하지 않습니다.

try-catch로 분리되어 Line 35의 set({ user, isAuthenticated: true, ... })이 이미 완료된 후 브릿지 호출이 실패해도 인증 상태가 유지됩니다.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/stores/authStore.ts` around lines 37 - 43, No changes required: the
try-catch around window.ReactNativeWebView.postMessage(JSON.stringify({ type:
'LOGIN_COMPLETE', accessToken })) correctly prevents bridge delivery failures
from rolling back the prior set({ user, isAuthenticated: true, ... }) call;
leave the current behavior as-is (optionally add a processLogger.error or
console.warn in the catch if you want to record the bridge failure).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@src/stores/authStore.ts`:
- Around line 37-43: No changes required: the try-catch around
window.ReactNativeWebView.postMessage(JSON.stringify({ type: 'LOGIN_COMPLETE',
accessToken })) correctly prevents bridge delivery failures from rolling back
the prior set({ user, isAuthenticated: true, ... }) call; leave the current
behavior as-is (optionally add a processLogger.error or console.warn in the
catch if you want to record the bridge failure).

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 32ca6a9 and 10d976b.

📒 Files selected for processing (4)

• src/apis/client.ts
• src/apis/notification/index.ts
• src/pages/User/MyPage/hooks/useLogout.ts
• src/stores/authStore.ts

🚧 Files skipped from review as they are similar to previous changes (1)

• src/apis/client.ts