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

RN 0.76 버전에서 안드로이드 앱 크래시 #207

Closed
iziz9 opened this issue Nov 26, 2024 · 3 comments
Closed

RN 0.76 버전에서 안드로이드 앱 크래시 #207

iziz9 opened this issue Nov 26, 2024 · 3 comments
Labels

Comments

@iziz9
Copy link

iziz9 commented Nov 26, 2024

Description

RN 0.76.1 버전에서 react-native-naver-login 4.0.4 를 사용해 네이버 로그인을 구현하고 있습니다.
IOS에서는 정상적으로 동작하는데, 안드로이드 환경에서는 NaverLogin.login() 호출 시 아무 응답 없이 앱이 종료되고
안드로이드 스튜디오 logcat에는 아래 에러메시지가 표시됩니다.

image

java_vm_ext.cc:598] JNI DETECTED ERROR IN APPLICATION: the return type of CallVoidMethodA does not match boolean com.dooboolab.naverlogin.RNNaverLoginModule.login(com.facebook.react.bridge.Promise)
java_vm_ext.cc:598]     in call to CallVoidMethodA
java_vm_ext.cc:598]     from void com.facebook.jni.NativeRunnable.run()

다른 프로젝트에서도 시도해봤는데 RN 0.75.4에서는 정상 동작하고, RN 0.76.3에서는 같은 에러가 발생합니다.

Steps to reproduce

  1. NaverLogin.login() 호출 시 앱 크래시

Snack or a link to a repository

https://github.com/dinos-dev/dinos/tree/develop

React Native Naver Login version

^4.0.4

React Native version

0.76.1 / 0.76.3

Platforms

Android

JavaScript runtime

None

Architecture

None

Build type

None

Device

None

Device model

No response

Acknowledgements

Yes

@tree1891
Copy link

tree1891 commented Dec 4, 2024

RNNaverLoginModule.kt 에서 함수 선언 형식을 변경해서(fun [function name]() = ...fun [function name]() { ... } 로) 임시로 해결했습니다.
@react-native-seoul+naver-login+4.0.4.patch

    @ReactMethod
    fun logout(promise: Promise) {
        UiThreadUtil.runOnUiThread {
            callLogout()
            promise.safeResolve(null)
        }
    }

@iziz9
Copy link
Author

iziz9 commented Dec 4, 2024

@tree1891 알려주신대로 수정했더니 실행됐습니다!! 정말 감사합니다 ㅠㅠ👍👍

Copy link

github-actions bot commented Jan 4, 2025

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 2 days.

@github-actions github-actions bot added the Stale label Jan 4, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants