만약 배달앱을 만든다고하면,앱을 켤 때, foreground, background 모두 권한을 받아두는 식으로 개발하나요 ?

저는 npm run android 하면 빌드앱이 우선으로 실행되고, expo go 로 계속 switch 해야하는데요 혹시 expo go 로 디폴트로 시작하게는 못하나요 ?

✘ chaejinjeong😝  ~/Desktop/lukas/Study/reactnative/zerocho/threads  ↱ main ±  eas update --channel development --message "fix: apiUrl"[expo-cli] env: load .env[expo-cli] env: export KAKAO_NATIVE_KEY[expo-cli] Starting Metro Bundler[expo-cli] iOS ./index.ts ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░ 99.9% (1879/1883)[expo-cli] Android ./index.ts ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░ 99.9% (1886/1886)[expo-cli] iOS ./index.ts ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░ 99.9% (1884/1884)[expo-cli] Android ./index.ts ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░ 99.9% (1886/1886)[expo-cli] Android Bundled 8190ms index.ts (1886 modules)[expo-cli] iOS ./index.ts ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░ 99.9% (1884/1884)[expo-cli] Android ./index.ts ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░ 99.9% (1886/1886)[expo-cli] iOS ./index.ts ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░ 99.9% (1884/1884)[expo-cli] iOS Bundled 12572ms index.ts (1884 modules)[expo-cli] iOS ./index.ts ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░ 99.9% (1884/1884)[expo-cli] Creating asset map[expo-cli] [expo-cli] › Assets (54):[expo-cli] assets/images/avatar.png (17.5 kB)[expo-cli] assets/images/react-logo.png (3 variations | 13.9 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/AntDesign.ttf (70.3 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/Entypo.ttf (66.2 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/EvilIcons.ttf (13.5 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/Feather.ttf (56.2 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/FontAwesome.ttf (166 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/FontAwesome5_Brands.ttf (134 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/FontAwesome5_Regular.ttf (33.7 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/FontAwesome5_Solid.ttf (203 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/FontAwesome6_Brands.ttf (209 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/FontAwesome6_Regular.ttf (68 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/FontAwesome6_Solid.ttf (424 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/Fontisto.ttf (314 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/Foundation.ttf (57 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/Ionicons.ttf (443 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/MaterialCommunityIcons.ttf (1.15 MB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/MaterialIcons.ttf (357 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/Octicons.ttf (49.4 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/SimpleLineIcons.ttf (54.1 kB)[expo-cli] node_modules/@expo/vector-icons/build/vendor/react-native-vector-icons/Fonts/Zocial.ttf (25.8 kB)[expo-cli] node_modules/@react-navigation/elements/lib/module/assets/back-icon-mask.png (653 B)[expo-cli] node_modules/@react-navigation/elements/lib/module/assets/back-icon.png (8 variations | 359 B)[expo-cli] node_modules/@react-navigation/elements/lib/module/assets/clear-icon.png (4 variations | 425 B)[expo-cli] node_modules/@react-navigation/elements/lib/module/assets/close-icon.png (4 variations | 235 B)[expo-cli] node_modules/@react-navigation/elements/lib/module/assets/search-icon.png (7 variations | 592 B)[expo-cli] node_modules/expo-router/assets/arrow_down.png (9.46 kB)[expo-cli] node_modules/expo-router/assets/error.png (469 B)[expo-cli] node_modules/expo-router/assets/file.png (138 B)[expo-cli] node_modules/expo-router/assets/forward.png (188 B)[expo-cli] node_modules/expo-router/assets/pkg.png (364 B)[expo-cli] node_modules/expo-router/assets/sitemap.png (465 B)[expo-cli] node_modules/expo-router/assets/unmatched.png (4.75 kB)[expo-cli] [expo-cli] › android bundles (2):[expo-cli] _expo/static/js/android/index-76e11ae11c34c3503a6dbd90ed0b7a03.hbc (5.82 MB)[expo-cli] _expo/static/js/android/index-76e11ae11c34c3503a6dbd90ed0b7a03.hbc.map (14.5 MB)[expo-cli] [expo-cli] › ios bundles (2):[expo-cli] _expo/static/js/ios/index-4cdfeb96d45c0edbe3d45931022e8005.hbc (5.82 MB)[expo-cli] _expo/static/js/ios/index-4cdfeb96d45c0edbe3d45931022e8005.hbc.map (14.5 MB)[expo-cli] [expo-cli] › Files (2):[expo-cli] assetmap.json (25.4 kB)[expo-cli] metadata.json (6.42 kB)[expo-cli] [expo-cli] Exported: dist✔ Exported bundle(s)✔ Uploaded assetmap.json ⠇ Uploading (0/56)(node:12056) [DEP0044] DeprecationWarning: The util.isArray API is deprecated. Please use Array.isArray() instead.(Use node --trace-deprecation ... to show where the warning was created)✔ Uploaded 2 app bundles✔ Uploading assets skipped - no new assets foundℹ 50 iOS assets, 50 Android assets (maximum: 2000 total per update). Learn more about asset limits✔ Computed project fingerprints✔ Published!Branch developmentRuntime version 1.0.0Platform android, iosUpdate group ID 36193c9d-e3cb-43b3-abb0-1b0a945b68afAndroid update ID 4c505558-7e8e-4837-89eb-67c40f4d84ceiOS update ID d1473ce0-3b64-4d6a-a907-c14cb46ac87bMessage fix: apiUrlCommit 53e7e483149d3a1c11158dc6d82e1d275d1817dd*EAS Dashboard https://expo.dev/accounts/lukasdiego/projects/threads/updates/36193c9d-e3cb-43b3-abb0-1b0a945b68afNo compatible builds found for the following fingerprints: iOS fingerprint: 0ccba201890a2a4b134bfc3a01a91979c8c32e83 URL : https://expo.dev/accounts/lukasdiego/projects/threads/fingerprints/0ccba201890a2a4b134bfc3a01a91979c8c32e83 Android fingerprint: 676271bcdf365731eeac1b2652140fffb81ea64f URL : https://expo.dev/accounts/lukasdiego/projects/threads/fingerprints/676271bcdf365731eeac1b2652140fffb81ea64f chaejinjeong😝  ~/Desktop/lukas/Study/reactnative/zerocho/threads  ↱ main ±   eas update 는 된 것 같은데  Builds에서는 안보이네요 업데이트가 잘 못 된걸까요 ?우선 commit들은 확인이 됩니다.

Error: adb: failed to install /Users/chaejinjeong/Desktop/lukas/Study/reactnative/zerocho/threads/android/app/build/outputs/apk/debug/app-debug.apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Existing package com.lotto.threads signatures do not match newer version; ignoring!]현재 npm run android 시 이런 에러를 겪고 있습니다.. 혹시 어떤게 잘 못 된걸까요 ?앱을 삭제했습니다orbit으로 다시 instsall 했습니다

eas configure 성공하려면app.config.js 가 아니라 app.json으로 있어야하나요 ?

윈도우에서 react expo로 앱을 만든 후 애뮬에 배포하는거말고 윈도우 하드디스크에 apk를 받고싶어서 npx eas build -p android --profile preview --local 이라고 명령어 실행하면 Unsupported platform, macOS or Linux is required to build apps for Android Error: build command failed. 이렇게 뜨는데 제가 잘못한게 있을까요? 아니면 맥북에서만 로컬 빌드가 가능한건가요?? eas 온라인 빌드는 한달 30회 제한도 있고 큐에 쌓이고 기다리는 시간이 너무 길어서 apk 추출해서 실기기에 넣고싶은데 윈도우에서는 방법이 없을까요?    

✘ chaejinjeong😝  ~/Desktop/lukas/Study/reactnative/zerocho/threads  ↱ main ±  eas build --profile development --platform android ★ eas-cli@16.17.0 is now available. To upgrade, run: npm install -g eas-cli Proceeding with outdated version. Failed to read the app config from the project using "npx expo config" command: npx expo config --json exited with non-zero code: 1. Falling back to the version of "@expo/config" shipped with the EAS CLI. [@react-native-kakao/core] 'nativeAppKey' missing in expo config plugin value Error: build command failed.현재 강의 따라하다가 app.config.js 로 app.json이 바뀌어있는 상태인데 config.js 에서는 환경변수로 값이 인식이 안되나요 ? Expo 프로젝트에 환경변수는 등록이 되어있는 상태입니다.

https://github.com/ZeroCho/threads-clone/tree/9313da137d2520c8a336e9add8ec61a776bca4e4/app위 링크에서 modal.tsx 만 다음 코드로 바꾼 후 실습 진행하시면 됩니다.이렇게 되어 있을 때, 해당 링크에 있는 파일을 다운로드 할 수 있나요?아니면 해당 링크에 들어가서, 파일 하나하나 접근해서 파일 하나씩 다운로드를 하는건가요?죄송합니다. 무슨 말인지 모르겠어요.

'c:/Users/swu/threads-clone/node_modules/@faker-js/faker/tsconfig.json' 구성 파일에서 입력을 찾을 수 없습니다. 지정된 '포함' 경로는 '["src/**/*"]'이고 '제외' 경로는 '["node_modules"]'이었습니다. 처음에 오류가 발생해서 npm uninstall @faker-js/faker 로 한 번 지웠다가 다시 npm i @faker-js/faker 로 설치했는데 이런 오류가 발생합니다 ㅜㅜ 지웠다가 설치해서 이런 오류가 발생하는 걸까요? 

LOG key: Xo8WBi6jzSxKDVR4drqm84yr9iU= ERROR [Error: invalid android_key_hash or ios_bundle_id or web_site_url]key는 잘 받아오는데 로그인이 안됩니다.. const onKakaoLogin = async () => { try { console.log("key: ", await getKeyHashAndroid()); const result = await kakaoLogin(); console.log(result); const user = await me(); console.log(user); // TODO: save the token to server } catch (error) { console.error(error); } };현재 사용 중인 코드입니다.

reactive kakao login docs를 보고 설치하고 강의따라 kakako core,user 설치했는데, 아래와같은 에러가 계속 발생합니다> Configure project :react-native-reanimated Android gradle plugin: 8.8.2 Gradle: 8.13 [Incubating] Problems report is available at: file:///Users/chaejinjeong/Desktop/lukas/Study/reactnative/zerocho/threads/android/build/reports/problems/problems-report.html FAILURE: Build failed with an exception. * What went wrong: Could not determine the dependencies of task ':app:processDebugResources'. > Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'. > Could not find com.kakao.sdk:v2-common:2.20.1. Searched in the following locations: - file:/Users/chaejinjeong/Desktop/lukas/Study/reactnative/zerocho/threads/node_modules/react-native/android/com/kakao/sdk/v2-common/2.20.1/v2-common-2.20.1.pom - https://dl.google.com/dl/android/maven2/com/kakao/sdk/v2-common/2.20.1/v2-common-2.20.1.pom - https://repo.maven.apache.org/maven2/com/kakao/sdk/v2-common/2.20.1/v2-common-2.20.1.pom - https://www.jitpack.io/com/kakao/sdk/v2-common/2.20.1/v2-common-2.20.1.pom - https://central.sonatype.com/repository/maven-snapshots/com/kakao/sdk/v2-common/2.20.1/v2-common-2.20.1.pom Required by: project :app > project :react-native-kakao_core > Could not find com.kakao.sdk:v2-user:2.20.1. Searched in the following locations: - file:/Users/chaejinjeong/Desktop/lukas/Study/reactnative/zerocho/threads/node_modules/react-native/android/com/kakao/sdk/v2-user/2.20.1/v2-user-2.20.1.pom - https://dl.google.com/dl/android/maven2/com/kakao/sdk/v2-user/2.20.1/v2-user-2.20.1.pom - https://repo.maven.apache.org/maven2/com/kakao/sdk/v2-user/2.20.1/v2-user-2.20.1.pom - https://www.jitpack.io/com/kakao/sdk/v2-user/2.20.1/v2-user-2.20.1.pom - https://central.sonatype.com/repository/maven-snapshots/com/kakao/sdk/v2-user/2.20.1/v2-user-2.20.1.pom Required by: project :app > project :react-native-kakao_user * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. > Get more help at https://help.gradle.org. Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. For more on this, please refer to https://docs.gradle.org/8.13/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. BUILD FAILED in 6s 33 actionable tasks: 5 executed, 28 up-to-date Error: /Users/chaejinjeong/Desktop/lukas/Study/reactnative/zerocho/threads/android/gradlew app:assembleDebug -x lint -x test --configure-on-demand --build-cache -PreactNativeDevServerPort=8081 -PreactNativeArchitectures=arm64-v8a exited with non-zero code: 1 Error: /Users/chaejinjeong/Desktop/lukas/Study/reactnative/zerocho/threads/android/gradlew app:assembleDebug -x lint -x test --configure-on-demand --build-cache -PreactNativeDevServerPort=8081 -PreactNativeArchitectures=arm64-v8a exited with non-zero code: 1 at ChildProcess.completionListener (/Users/chaejinjeong/Desktop/lukas/Study/reactnative/zerocho/threads/node_modules/@expo/spawn-async/src/spawnAsync.ts:67:13) at Object.onceWrapper (node:events:622:26) at ChildProcess.emit (node:events:507:28) at maybeClose (node:internal/child_process:1101:16) at Process.ChildProcess._handle.onexit (node:internal/child_process:305:5) ... at spawnAsync (/Users/chaejinjeong/Desktop/lukas/Study/reactnative/zerocho/threads/node_modules/@expo/spawn-async/src/spawnAsync.ts:28:21) at spawnGradleAsync (/Users/chaejinjeong/Desktop/lukas/Study/reactnative/zerocho/threads/node_modules/@expo/cli/src/start/platforms/android/gradle.ts:134:28) at assembleAsync (/Users/chaejinjeong/Desktop/lukas/Study/reactnative/zerocho/threads/node_modules/@expo/cli/src/start/platforms/android/gradle.ts:83:16) at runAndroidAsync (/Users/chaejinjeong/Desktop/lukas/Study/reactnative/zerocho/threads/node_modules/@expo/cli/src/run/android/runAndroidAsync.ts:62:24)node_modules 모두 삭제하고 설치해도 똑같습니다npx expo install --fix 로도 호환이 안맞춰지는 것 같습니다.패키지는 설치되어있는 것 확인했습니다.제 진행중인 코드입니다.

강의 17 부터는 서버와 데이터베이스가 따로 필요한걸까요?서버를 따로 구축해야 되는지, 데이터베이스를 추가로 설치해야 되는건지 궁금합니다

궁금한 점 : @apply 핑크로 변하지 않아도 실행은 됩니다! 상관 없는걸까요??styles.module.csstailwind.config

yarn info react version19.1.0yarn info react-native version0.80.1yarn info expo version53.0.20제로초님 안녕하세요! 강의 내용과 똑같이 환경변수를 설정하고 ios eas build를 하는 과정에서 nativeAppKey 환경변수를 읽어오지 못하는 상황이 계속 발생합니다. expo 대시보드의 프로젝트 환경변수에도사진과 같이 등록해놓은 상태이고, eas build --profile development --platform ios 커맨드를 실행했을때 아래와 같이 에러나 나는 상황입니다. .env를 .gitIgnore에서 잠깐 제거하고 빌드해도 동일하게 에러가 납니다..!!Failed to read the app config from the project using "npx expo config" command: npx expo config --json exited with non-zero code: 1.Falling back to the version of "@expo/config" shipped with the EAS CLI.// app.config.js[ '@react-native-kakao/core', { nativeAppKey: process.env.KAKAO_APP_KEY, android: { authCodeHandlerActivity: true, }, ios: { handleKakaoOpenUrl: true, }, }, ], ... 생략 extra: { kakaoAppKey: process.env.KAKAO_APP_KEY, router: {}, eas: { projectId: '...생략', }, },// eas.json{ "cli": { "version": ">= 16.10.0", "appVersionSource": "remote" }, "build": { "development": { "developmentClient": true, "distribution": "internal", "ios": { "simulator": true } }, "preview": { "distribution": "internal" }, "production": { "autoIncrement": true } }, "submit": { "production": {} } } // src/app/_layout.tsxuseEffect(() => { initializeKakaoSDK(Constants.expoConfig?.extra?.kakaoAppKey as string); }, []); 도움 주시면 감사하겠습니다 🙏🏻

안녕하세요 강사님  accessToken 만료시 refreshToken 으로 다시 발급받는과정에서 질문이 있습니다. dio.dart 소스에 onError 에서 print 로 로그를 호출하고 있는데요 @override void onError(DioException err, ErrorInterceptorHandler handler) async { print("[ERR] [${err.requestOptions.method}] ${err.requestOptions.uri}"); final refreshToken = await storage.read(key: REFRESH_TOKEN_KEY); if (refreshToken == null) { return handler.reject(err); } final isStatus401 = err.response?.statusCode == 401; final isPathRefresh = err.requestOptions.path == "/auth/token"; if (isStatus401 && !isPathRefresh) { final dio = Dio(); try { final resp = await dio.post( "http://$ip/auth/token", options: Options(headers: {"authorization": "Bearer $refreshToken"}), ); final accessToken = resp.data["accessToken"]; final options = err.requestOptions; options.headers.addAll({ "authorization": "Bearer $accessToken", }); await storage.write(key: ACCESS_TOKEN_KEY, value: accessToken); final response = await dio.fetch(options); return handler.resolve(response); } on DioException catch (e) { return handler.reject(e); } } // return handler.reject(err); super.onError(err, handler); } 호출하는 restaurant_detail_screen.dart 를 보면 Future<RestaurantDetailModel> getRestaurantDetail() async { final dio = Dio(); dio.interceptors.add( CustomInterceptor(storage: storage) ); final repository = RestaurantRepository(dio, baseUrl: "http://$ip/restaurant"); return repository.getRestaurantDetail(id: id); } 이런식으로 되어있거든요? 그래서 refreshToken 으로 토큰을 재발급 받고 storage에도 새로 저장하였으나 dio 가 매번 호출되는 방식입니다. 그러다 보니 매번 onError 가 호출이되고 에러 로그가 찍힐수 밖에 없는 구조입니다. 싱글톤 방식으로 수정이 되지 않으면 해당 에러는 계속 날것 같은데 혹시 이후에 해당부분이 수정이 되는 강의 부분이 있을까요?

안녕하세요 제가 지금 토이프로젝트로 8월 말까지 앱의 mvp 기능을 만들고 싶어서 expo 강좌를 수강 신청 및 수강하게 되었습니다제가 웹, 앱에 대한 지식이 전혀 없어서 gpt한테 물어보면서 진행을 해도 잘 이해하면서 하고 있지는 않은 것 같습니다 핵심개념들이 없는 것 같습니다react, ts를 공부해야 이해가 될까요 ..?

안녕하세요 제로초님! 모르는 부분 강의 참고하며 회사 서비스를 expo로 구현중입니다. TextInput를 터치하면 키보드에 인풋이 가려지는 현상이 있어서 해결중인 상황입니다. expo 공식문서에 나와있는 react-native-keyboard-controller 라이브러리를 사용하려고 했지만 사용하려면 pod install을 다시 해줘야돼서 prebuild가 필수적인데, ios 폴더가 생기면 네이티브 코드 관리를 잘 할 자신이 없어서.. development builds App 만으로 해결할 수 있는 방법이 있을까요?

재설치, eas build 를 다시해도 아래와 같은 에러 문구가 계속 나오네요.. 

useState(0) 부분에서 오류가 나 실행이 안됩니다. 오류를 못찾겠어요ㅠㅠ 알려주세요

제로초님 안녕하세요!const result = await kakaoLogin();로그인 했을때 받아오는 result 내부의 accessToken이 백엔드에 전달해야될 인가 코드라고 생각하면 될까요?? 백엔드 개발자분에게 인가 코드를 전해드려야하는데 저게 인가 코드인건지 궁금합니다..!!