Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore: 🐛 Revising the Refresh Event Handler #220

Merged
merged 1 commit into from
Jan 14, 2025

Conversation

psychology50
Copy link
Member

작업 이유

  • The client can refresh and should be able to receive messages from the socket server to process pending chat messages, but the receipt handler wasn’t working.

작업 사항

export const refresh = async () => {
    try {
        const response = await fetch(`${CONFIG.API_URL}/v1/auth/refresh`, {
            method: 'GET',
            credentials: 'include'
        });

        if (response.ok) {
            console.log('🟢 [Token refresh] API 서버 갱신 성공: ', response);

            TokenManager.setAccessToken(response.headers.get('Authorization'));

            const receiptId = 'receipt-' + Date.now();

            return new Promise((resolve, reject) => {
                stompClient.watchForReceipt(receiptId, (frame) => { // publish 하기 전에 watchForReceipt로 응답을 기다려야 함
                    console.log('🔄 [Token refresh confirmed] frame:', frame);
                    console.log('🟢 [Token refresh confirmed] headers:', frame.headers);
                    console.log('🟢 [Token refresh confirmed] raw body:', frame.body);

                    try {
                        const jsonMatch = frame.body.match(/\{.*\}/);
                        if (jsonMatch) {
                            const jsonStr = jsonMatch[0];
                            console.log('🟢 [Token refresh confirmed] Extracted JSON:', jsonStr);
                            const serverMessage = JSON.parse(jsonStr);
                            console.log('🟢 [Token refresh confirmed] Parsed message:', serverMessage);

                            ...
                        } else {
                            ...
                        }
                    } catch (error) {
                        ...
                    }
                });

                stompClient.publish({
                    destination: "/pub/auth.refresh",
                    headers: {'Authorization': TokenManager.getAccessToken(), 'receipt': receiptId},
                    body: JSON.stringify({accessToken: TokenManager.getAccessToken()})
                });
            });
        }
        return true;
    } catch (error) {
        ...
    }
}

image

  • Now, they can successfully receive messages.

리뷰어가 중점적으로 확인해야 하는 부분

  • None.

발견한 이슈

  • None.

@psychology50 psychology50 added bug 긴급하고, 중요도가 높은 이슈 fix 기능 수정 labels Jan 14, 2025
@psychology50 psychology50 self-assigned this Jan 14, 2025
@psychology50 psychology50 merged commit dd54569 into dev Jan 14, 2025
1 check passed
@psychology50 psychology50 deleted the fix/socket-server-refresh-receipt branch January 14, 2025 11:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 긴급하고, 중요도가 높은 이슈 fix 기능 수정
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant