We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
빌드 후 안드로이드 환경에서 라이브러리를 초기화 하는 과정에 아래와 같이 init을 찾을 수 없다고 합니다.
Warning: TypeError: Cannot read property 'initialize' of null
아래는 제가 작성한 init 코드입니다.
... const appName = '...'; const consumerKey = '...'; const consumerSecret = '...';
if (Platform.OS === 'ios') { NaverAuth.initialize({ appName, consumerKey, consumerSecret, serviceUrlSchemeIOS: '...', disableNaverAppAuthIOS: false, }); } else { NaverAuth.initialize({ appName, consumerKey, consumerSecret, }); } ...
iOS에서는 정상적으로 동작하는데, 안드로이드만 이러네용... ㅠ.ㅠ 비슷한 문제가 있으셨던 분이 계실까요?
None
^4.0.4
0.76.1
Android
Hermes
Paper (Old Architecture)
Debug mode
Android emulator
Android Emulator
Yes
The text was updated successfully, but these errors were encountered:
@Lucas-Baek-HYU 해결하셨나요???
Sorry, something went wrong.
No branches or pull requests
Description
빌드 후 안드로이드 환경에서 라이브러리를 초기화 하는 과정에 아래와 같이 init을 찾을 수 없다고 합니다.
Warning: TypeError: Cannot read property 'initialize' of null
Steps to reproduce
아래는 제가 작성한 init 코드입니다.
...
const appName = '...';
const consumerKey = '...';
const consumerSecret = '...';
if (Platform.OS === 'ios') {
NaverAuth.initialize({
appName,
consumerKey,
consumerSecret,
serviceUrlSchemeIOS: '...',
disableNaverAppAuthIOS: false,
});
} else {
NaverAuth.initialize({
appName,
consumerKey,
consumerSecret,
});
}
...
iOS에서는 정상적으로 동작하는데, 안드로이드만 이러네용... ㅠ.ㅠ
비슷한 문제가 있으셨던 분이 계실까요?
Snack or a link to a repository
None
React Native Naver Login version
^4.0.4
React Native version
0.76.1
Platforms
Android
JavaScript runtime
Hermes
Architecture
Paper (Old Architecture)
Build type
Debug mode
Device
Android emulator
Device model
Android Emulator
Acknowledgements
Yes
The text was updated successfully, but these errors were encountered: