묻고 답해요
158만명의 커뮤니티!! 함께 토론해봐요.
인프런 TOP Writers
-
해결됨스프링 MVC 1편 - 백엔드 웹 개발 핵심 기술
서블릿으로 구현한 회원관리에 대한 질문입니다.
[질문 템플릿]1. 강의 내용과 관련된 질문인가요? (예/아니오)2. 인프런의 질문 게시판과 자주 하는 질문에 없는 내용인가요? (예/아니오)3. 질문 잘하기 메뉴얼을 읽어보셨나요? (예/아니오)[질문 내용]JSP에 java 코드를 추가해서 회원관리 웹 애플리케이션을 구현한 것이 mvc model1 이고 servlet과 jsp를 이용해서 회원관리 웹 애플리케이션을 구현한 것이 mvc model2 라고 알고있습니다.그럼 처음에 서블릿에서 PrintWriter 클래스를 이용해서 구현한 회원관리 웹 애플리케이션은 mvc model1 인가요? 아니면 순수 java를 이용한 회원관리 웹 애플리케이션인가요??
-
해결됨[코드캠프] 부트캠프에서 만든 고농축 백엔드 코스
이미지 업로드 API - graphql postman uploadFile 시 headers 문제
안녕하세요.'이미지 업로드 API' 수업 따라가다 Postman으로 'uploadFile' 호출시 'Cross-Site Request Forgery(CSRF)' 오류 발생에 대해서 확인 후 원인에 대해서 시원한 답변 부탁 드릴께요.위와 같이 CSRF 오류가 발생 합니다. 구글후 headers에 하기 값을 추가하니 문제 없네요. 원인에 대해서 쉽게 설명좀 부탁 드립니다. :)
-
미해결비트코인 암호화폐 자동매매 코인봇 만들기 Part 1 - 무위험 전략 학습하기
ImportError: pycurl: 에러
- 학습 관련 질문을 남겨주세요. 상세히 작성하면 더 좋아요! - 먼저 유사한 질문이 있었는지 검색해보세요. - 서로 예의를 지키며 존중하는 문화를 만들어가요. - 잠깐! 인프런 서비스 운영 관련 문의는 1:1 문의하기를 이용해주세요.안녕하세요.실행하면 아래와 같이 오류가 납니다.❯ python api_test.pyImportError: pycurl: libcurl link-time ssl backends (secure-transport, openssl) do not include compile-time ssl backend (none/other) mac 이고python 3.8.9pip 23.0.1환경입니다. api_test.py 실행하면 아래와 같은 오류가 나서 openssl 까지 설치를 해도 마찮가지입니다. T Tpip install pycurl 을 실행하면 아래와 같이 만족한다고 나옵니다.❯ pip install pycurlRequirement already satisfied: pycurl in /Users/hyungsoolim/dev/coin/myenv/lib/python3.8/site-packages (7.45.2) 다시한번더 폴더를 coinbot/bithumb 을 만들고coinbot/bithumb 디렉토리에서 가상환경 생성하고coinbot/bithumb 아래에 pycurl-7.43.0.tar.gz 복사하고설치를 진행하니 아래와 같이 오류가 발생합니다. 파이썬 3.8버전이랑 pycurl 버전이 잘 안맞아서 그런가요?역시 환경설정이 어렵네요 T T 확인 부탁드립니다.
-
해결됨10주완성 C++ 코딩테스트 | 알고리즘 코딩테스트
4-h성곽 문제 dfs 언더플로 오버플로 체크
안녕하세요, 큰돌님. 강의를 듣다 궁금한 점이 생겨서 질문 드립니다. 평소대로라면 dfs에서 최대 최소 범위 오버 플로나 언더 플로를 체크하셨을 텐데, 이번 코드는 그게 없네요.혹시 그 이유가 지도가 무조건 성벽에 둘러싸여져 있어서 그런 것일까요?
-
미해결자바 코딩테스트 - it 대기업 유제
실전 문제 질문 하나만 드립니다 ㅠ
강사님 안녕하세요, 제가 이번에 모 유니콘 기업에 코딩테스트를 보게 되었는데요.1반과 2반을 키순대로 나열하는데, 키순이 안맞는 곳만 상대방 반의 같은 index 위치의 학생과 교환이 가능합니다. 최소한 몇번 교환을 해야 만족하는지 구하는게 전부입니다. 너무 간단해 보여서 저는키순이 안맞는 위치를 체크한 후,같은 index 위치의 다른 반 애를 데려왔을때, 키순이 앞뒤로 안맞는지 체크, 안맞으면 안바꿈이런식으로만 했는데, 테스트 케이스 다 틀리네요 ㅠ얘는 그냥 구현일가요? 아니면 어떤 알고리즘이 있는걸가요?예제1)int[] height1 = {150, 170, 180, 180}; int[] height2 = {150, 160, 170, 190};답 : 횟수 1 (3번 인덱스 끼리만 교환) 예제2)int[] height1 = {130, 140}; int[] height2 = {130, 140};답 : 횟수 0
-
해결됨데이터 분석 SQL Fundamentals
스칼라 서브쿼리 실습 - 01 : 질문 있습니다!
안녕하세요 선생님, 강의 너무 재밌게 복습하고 있는 수강생입니다.질문이 있어서 글을 씁니다. " 스칼라 서브쿼리 실습 - 01 " 강의 07:10 에서 아래 쿼리에 문제가 있다고 알려주십니다.select a.*,(select avg(sal) from hr.emp x where x.deptno = a.deptno) dept_avg_salfrom hr.emp a;그리고 그 과정에서 M:N join 결과물을 예로 들어서 왜 그런 지를 알려주시는데요, 여기서 의문이 생겼습니다."스칼라 서브쿼리 실습 - 01 " 바로 이전 강의에서 스칼라 서브 쿼리는 메인 쿼리의 각 레코드 별로 연산이 수행된다는 걸로 기억합니다. 그 말은...(select avg(sal) from hr.emp x where x.deptno = a.deptno)위 스칼라 서브쿼리가 hr.emp 테이블의 각 레코드 별로 연산이 수행된다는 걸로 전 이해합니다.그런데 07:10 때는 이걸 조인의 결과물로 설명하시면서 좋지 않은 쿼리라고 알려주십니다.각 레코드 별로 연산을 수행한다고 생각하면 사실 저 서브쿼리가 잘못된 쿼리 같지가 않다고 저는 생각하는데, 그게 아닌가요? 조인을 통해서 스칼라 서브쿼리를 좋은지 아닌지를 판단해야 되는 건가요??
-
미해결[초급편] 안드로이드 커뮤니티 앱 만들기(Android Kotlin)
파이어베이스
로그인 회원가입 파이어베이스 하는데gradle 에 버전이 호환되지 않는다구 떠요 버전 설정은 어떻게 해야할까요
-
미해결[리뉴얼] React로 NodeBird SNS 만들기
useMemo 질문이요
const TextAreaStyle = { resize: 'none', height: 120, marginBotton: 5, }; function EditPostCard() { return ( <> <TextArea rows={4} style={TextAreaStyle} /> <Space wrap> <Button type="primary">수정</Button> <Button type="primary" danger>취소</Button> </Space> </> ); } export default EditPostCard; 컴포넌트 밖에서 스타일객체를 선언한 경우 function EditPostCard() { const TextAreaStyle = useMemo(() => ({ resize: 'none', height: 120, marginBotton: 5, })); return ( <> <TextArea rows={4} style={TextAreaStyle} /> <Space wrap> <Button type="primary">수정</Button> <Button type="primary" danger>취소</Button> </Space> </> ); } 컴포넌트 안에서 useMemo를 사용한 경우리렌더링때문에 스타일을 따로 선언해주었는데요.두 가지 경우가 큰 차이가 있나요? useMemo안 쓰고컴포넌트 밖에다 선언해줘도 상관없나요?
-
미해결스프링 입문 - 코드로 배우는 스프링 부트, 웹 MVC, DB 접근 기술
회원 가입> 등록 후 회원목록 조회가 되지 않습니다.
[질문 템플릿]1. 강의 내용과 관련된 질문인가요? (예/아니오)2. 인프런의 질문 게시판과 자주 하는 질문에 없는 내용인가요? (예/아니오)3. 질문 잘하기 메뉴얼을 읽어보셨나요? (예/아니오)[질문 내용]회원가입 > 등록 후 회원목록 조회가 되지 않습니다. https://drive.google.com/file/d/1mo2EohoMsgKRpeusyQ-AXlygE1CSSJIV/view?usp=sharing코드 링크입니다. WhiteLabel Error Page 오류가 납니다.
-
해결됨[개정3판] Node.js 교과서 - 기본부터 프로젝트 실습까지
분리한 라우터를 한번 더 분리하고 싶으면 어떻게 해야 하나요?
예를들어 api 들은/api로 요청을 받아서 api들만 따로 빼주었는데여기서 한번더 /api/user/api/board이런식으로 분리하고싶다면 어떤 방법이 가장 좋을까요..?
-
미해결풀스택을 위한 도커와 최신 서버 기술(리눅스, nginx, AWS, HTTPS, 배포까지) [풀스택 Part3]
실행 오류 [답변 부탁드리겠습니다.]
안녕하세요.본 강의에서 해주신 코드 double check, 인바운드 규칙 확인 및 모든 방법을 다 써봤는데도 마지막 public ip접속시 'succes'라는 문구가 뜨지 않는데요.컨테이너를 전부 삭제해보고 인스턴스도 재부팅해봤는데도 원하는 결과가 출력되지 않습니다.어떤점에서 error가 났다는 log기록도 없는데 혹시 제가 놓친 부분이 무엇인지 알 수 있을지 조언해주시면 감사드리겠습니다.혹시 몰라서 전체 log 화면 첨부드립니다.감사합니다.
-
미해결스프링 MVC 2편 - 백엔드 웹 개발 활용 기술
th:field와 th:erroclass
안녕하세요th:errorclass : th:field 에서 지정한 필드에 오류가 있으면 class 정보를 추가한다pdf내용 중 한 문장인데요 . 이 의미가 th:field는 오류가 있다면 그 오류난 것을 알고 있어서 th:errorclass를통해 class정보를 추가한다는 의미 맞죠??그리고th:errors="*{itemName}"은errors중에 해당 필드 에러가 있을때 즉 itemName필드에 에러가 발생했을때 수행된다 이느낌 맞나요?/
-
해결됨Slack 클론 코딩[실시간 채팅 with React]
tsconfig-for-webpack-config 초기설정 파일 질문있습니다
영상을 보면서 진행하다보니 packge.json 스크립트에 TS_NODE_PROJECT가 추가되어있어 깃허브 setting으로 가서 확인을 해보니 tsconfig-for-webpack-config 파일이 추가되어있더라구요 근데 깃허브 package.json에는 "dev": "webpack serve --env development", "build": "cross-env NODE_ENV=production webpack"이렇게 되어있는데 TS_NODE_PROJECT 스크립트와 tsconfig-for-webpack-config.json 파일에 대해서 설명을 추가로 부탁드릴 수 있을까요?또한 영상과 달리 npm run dev에서는 cross-env가 빠져있는데 그부분도 빠져도 상관없는지 궁금합니다
-
미해결홍정모의 따라하며 배우는 C언어
포인터 연산에 관한 질문.
#define CRT_SECURED_NO_WARNINGS#include <stdio.h>#include <string.h>void fit_str(char*, unsigned int);int main(){ char msg[] = "just,""do it!"; puts(msg); printf("lenght %d\n", strlen(msg)); fit_str(msg, 4); puts(msg); printf("length %d\n", strlen(msg)); return 0; }void fit_str(char*a, unsigned int b){ a[b] = '\0';} 마지막 줄의 a[b]는 되는데 a+b는 왜 안될까요...? a는 포인터 배열이기 때문에 a+b 연산이 a[b]와 같지 않나요?
-
해결됨처음 배우는 리액트 네이티브
배포중 에러 해결이 안되네요.. ㅜㅜ
안녕하세요 선생님,선생님 강의를 기본으로 넣고 싶은 기능들을 넣어가며 만들고 싶던 앱을 제작 중인 웹퍼블리셔입니다.지금도 공식문서를 뒤저가며 열심히 구르고 있지만 선생님 강의가 없었으면 훨씬 더 많이 구르고 있을 것 같아요 ㅜㅜㅜ 늘 감사합니당.. 어찌어찌 생각한 기능 구현도 성공하고 안드로이드와 ios 모두에서 expo로 테스트해보고 이제 처음으로 빌드를 해보려고 시도하고 있는데 문제가 생겼어요..다른 것들은 구글링해서 스스로 해결하려고 노력했지만 이 부분은 구글링도 gpt로도 잘 해결이 안되어서 올려봅니당 ㅜㅜ 강의처럼 expo build 를 이용하려했지만 현재 지원이 종료되었다고하며 진행이 안되길래 로그에서 하라는대로 eas build를 이용했습니다.firebase 9버전으로 제작했습니다.mac에서 진행중입니다.ios 진행전에 안드로이드 개발자 계정 비용내고 안드로이드 빌드중입니다. eas build --platform android 명령어를 입력했을때🤖 Android build failed: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.라는 로그가 나옵니다.Run gradlew를 클릭하면 해당 로그가 보이는데Running 'gradlew :app:bundleRelease' in /home/expo/workingdir/build/android Downloading https://services.gradle.org/distributions/gradle-7.5.1-all.zip 10 %. 20%. 30%. 40%. 50%. 60%. 70%. 80%. 90%. 100% Welcome to Gradle 7.5.1! Here are the highlights of this release: - Support for Java 18 - Support for building with Groovy 4 - Much more responsive continuous builds - Improved diagnostics for dependency resolution For more details see https://docs.gradle.org/7.5.1/release-notes.html To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.5.1/userguide/gradle_daemon.html#sec:disabling_the_daemon. Daemon will be stopped at the end of the build > Task :react-native-gradle-plugin:pluginDescriptors > Task :react-native-gradle-plugin:processResources > Task :react-native-gradle-plugin:compileKotlin > Task :react-native-gradle-plugin:compileJava NO-SOURCE > Task :react-native-gradle-plugin:classes > Task :react-native-gradle-plugin:inspectClassesForKotlinIC > Task :react-native-gradle-plugin:jar > Configure project :expo-application WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL. > Configure project :expo-constants WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL. > Configure project :expo-file-system WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL. > Configure project :expo-font WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL. > Configure project :expo-keep-awake WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL. > Configure project :expo-mail-composer WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL. > Configure project :expo-modules-core WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL. Checking the license for package NDK (Side by side) 23.1.7779620 in /home/expo/Android/Sdk/licenses License for package NDK (Side by side) 23.1.7779620 accepted. Preparing "Install NDK (Side by side) 23.1.7779620 (revision: 23.1.7779620)". "Install NDK (Side by side) 23.1.7779620 (revision: 23.1.7779620)" ready. Installing NDK (Side by side) 23.1.7779620 in /home/expo/Android/Sdk/ndk/23.1.7779620 "Install NDK (Side by side) 23.1.7779620 (revision: 23.1.7779620)" complete. "Install NDK (Side by side) 23.1.7779620 (revision: 23.1.7779620)" finished. Checking the license for package CMake 3.22.1 in /home/expo/Android/Sdk/licenses License for package CMake 3.22.1 accepted. Preparing "Install CMake 3.22.1 (revision: 3.22.1)". "Install CMake 3.22.1 (revision: 3.22.1)" ready. Installing CMake 3.22.1 in /home/expo/Android/Sdk/cmake/3.22.1 "Install CMake 3.22.1 (revision: 3.22.1)" complete. "Install CMake 3.22.1 (revision: 3.22.1)" finished. > Configure project :expo-notifications WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL. > Configure project :expo-permissions WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL. > Configure project :expo-splash-screen WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL. > Configure project :expo Using expo modules - expo-application (5.1.1) - expo-constants (14.2.1) - expo-file-system (15.2.2) - expo-font (11.1.1) - expo-keep-awake (12.0.1) - expo-mail-composer (12.1.1) - expo-modules-core (1.2.6) - expo-notifications (0.18.1) - expo-permissions (14.1.1) - expo-splash-screen (0.18.1) WARNING:Software Components will not be created automatically for Maven publishing from Android Gradle Plugin 8.0. To opt-in to the future behavior, set the Gradle property android.disableAutomaticComponentCreation=true in the `gradle.properties` file or use the new publishing DSL. Checking the license for package Android SDK Build-Tools 30.0.3 in /home/expo/Android/Sdk/licenses License for package Android SDK Build-Tools 30.0.3 accepted. Preparing "Install Android SDK Build-Tools 30.0.3 (revision: 30.0.3)". "Install Android SDK Build-Tools 30.0.3 (revision: 30.0.3)" ready. Installing Android SDK Build-Tools 30.0.3 in /home/expo/Android/Sdk/build-tools/30.0.3 "Install Android SDK Build-Tools 30.0.3 (revision: 30.0.3)" complete. "Install Android SDK Build-Tools 30.0.3 (revision: 30.0.3)" finished. Checking the license for package Android SDK Platform 33 in /home/expo/Android/Sdk/licenses License for package Android SDK Platform 33 accepted. Preparing "Install Android SDK Platform 33 (revision: 2)". "Install Android SDK Platform 33 (revision: 2)" ready. Installing Android SDK Platform 33 in /home/expo/Android/Sdk/platforms/android-33 "Install Android SDK Platform 33 (revision: 2)" complete. "Install Android SDK Platform 33 (revision: 2)" finished. The Kotlin Gradle plugin was loaded multiple times in different subprojects, which is not supported and may break the build. This might happen in subprojects that apply the Kotlin plugins with the Gradle 'plugins { ... }' DSL if they specify explicit versions, even if the versions are equal. Please add the Kotlin plugin to the common parent project or the root project, then remove the versions in the subprojects. If the parent project does not need the plugin, add 'apply false' to the plugin line. See: https://docs.gradle.org/current/userguide/plugins.html#sec:subprojects_plugins_dsl The Kotlin plugin was loaded in the following projects: ':expo', ':expo-modules-core' > Task :expo-constants:preBuild UP-TO-DATE > Task :expo-application:preBuild UP-TO-DATE > Task :expo-application:preReleaseBuild UP-TO-DATE > Task :expo-constants:preReleaseBuild UP-TO-DATE > Task :expo-application:packageReleaseRenderscript NO-SOURCE > Task :expo-file-system:preBuild UP-TO-DATE > Task :expo-file-system:preReleaseBuild UP-TO-DATE > Task :expo-constants:packageReleaseRenderscript NO-SOURCE > Task :expo-font:preBuild UP-TO-DATE > Task :expo-font:preReleaseBuild UP-TO-DATE > Task :expo-file-system:packageReleaseRenderscript NO-SOURCE > Task :expo-keep-awake:preBuild UP-TO-DATE > Task :expo-keep-awake:preReleaseBuild UP-TO-DATE > Task :expo-keep-awake:packageReleaseRenderscript NO-SOURCE > Task :expo-mail-composer:preBuild UP-TO-DATE > Task :expo-mail-composer:preReleaseBuild UP-TO-DATE > Task :expo-font:packageReleaseRenderscript NO-SOURCE > Task :expo-modules-core:preBuild UP-TO-DATE > Task :expo-modules-core:preReleaseBuild UP-TO-DATE > Task :expo-modules-core:packageReleaseRenderscript NO-SOURCE > Task :expo-notifications:preBuild UP-TO-DATE > Task :expo-notifications:preReleaseBuild UP-TO-DATE > Task :expo-notifications:packageReleaseRenderscript NO-SOURCE > Task :expo-permissions:preBuild UP-TO-DATE > Task :expo-permissions:preReleaseBuild UP-TO-DATE > Task :expo-permissions:packageReleaseRenderscript NO-SOURCE > Task :expo-splash-screen:preBuild UP-TO-DATE > Task :expo-splash-screen:preReleaseBuild UP-TO-DATE > Task :expo-splash-screen:packageReleaseRenderscript NO-SOURCE > Task :expo-mail-composer:packageReleaseRenderscript NO-SOURCE > Task :react-native-community_datetimepicker:preBuild UP-TO-DATE > Task :react-native-community_datetimepicker:preReleaseBuild UP-TO-DATE > Task :react-native-async-storage_async-storage:preBuild UP-TO-DATE > Task :react-native-async-storage_async-storage:preReleaseBuild UP-TO-DATE > Task :react-native-async-storage_async-storage:packageReleaseRenderscript NO-SOURCE > Task :react-native-svg:preBuild UP-TO-DATE > Task :react-native-community_datetimepicker:packageReleaseRenderscript NO-SOURCE > Task :react-native-svg:preReleaseBuild UP-TO-DATE > Task :react-native-svg:packageReleaseRenderscript NO-SOURCE > Task :expo-application:compileReleaseRenderscript NO-SOURCE > Task :expo-constants:compileReleaseRenderscript NO-SOURCE > Task :expo-constants:generateReleaseResValues > Task :expo-application:generateReleaseResValues > Task :expo-constants:generateReleaseResources > Task :expo-application:generateReleaseResources > Task :expo-constants:packageReleaseResources > Task :expo-file-system:compileReleaseRenderscript NO-SOURCE > Task :expo-file-system:generateReleaseResValues > Task :expo-application:packageReleaseResources > Task :expo-file-system:generateReleaseResources > Task :expo-font:compileReleaseRenderscript NO-SOURCE > Task :expo-font:generateReleaseResValues > Task :expo-font:generateReleaseResources > Task :expo-font:packageReleaseResources > Task :expo-keep-awake:compileReleaseRenderscript NO-SOURCE > Task :expo-keep-awake:generateReleaseResValues > Task :expo-keep-awake:generateReleaseResources > Task :expo:generateExpoModulesPackageList > Task :expo:preBuild > Task :expo:preReleaseBuild > Task :expo:packageReleaseRenderscript NO-SOURCE > Task :expo:compileReleaseRenderscript NO-SOURCE > Task :expo:generateReleaseResValues > Task :expo:generateReleaseResources > Task :expo-keep-awake:packageReleaseResources > Task :expo-mail-composer:compileReleaseRenderscript NO-SOURCE > Task :expo-mail-composer:generateReleaseResValues > Task :expo-mail-composer:generateReleaseResources > Task :expo:packageReleaseResources > Task :expo-modules-core:compileReleaseRenderscript NO-SOURCE > Task :expo-modules-core:generateReleaseResValues > Task :expo-modules-core:generateReleaseResources > Task :expo-mail-composer:packageReleaseResources > Task :expo-file-system:packageReleaseResources > Task :expo-notifications:compileReleaseRenderscript NO-SOURCE > Task :expo-notifications:generateReleaseResValues > Task :expo-permissions:compileReleaseRenderscript NO-SOURCE > Task :expo-notifications:generateReleaseResources > Task :expo-permissions:generateReleaseResValues > Task :expo-permissions:generateReleaseResources > Task :expo-modules-core:packageReleaseResources > Task :expo-splash-screen:compileReleaseRenderscript NO-SOURCE > Task :expo-splash-screen:generateReleaseResValues > Task :expo-splash-screen:generateReleaseResources > Task :expo-permissions:packageReleaseResources > Task :react-native-async-storage_async-storage:compileReleaseRenderscript NO-SOURCE > Task :react-native-async-storage_async-storage:generateReleaseResValues > Task :react-native-async-storage_async-storage:generateReleaseResources > Task :expo-notifications:packageReleaseResources > Task :expo-splash-screen:packageReleaseResources > Task :react-native-async-storage_async-storage:packageReleaseResources > Task :react-native-community_datetimepicker:compileReleaseRenderscript NO-SOURCE > Task :react-native-community_datetimepicker:generateReleaseResValues > Task :react-native-community_datetimepicker:generateReleaseResources > Task :react-native-svg:compileReleaseRenderscript NO-SOURCE > Task :expo:extractDeepLinksRelease > Task :react-native-svg:generateReleaseResValues > Task :react-native-svg:generateReleaseResources > Task :react-native-svg:packageReleaseResources > Task :expo-application:extractDeepLinksRelease > Task :react-native-community_datetimepicker:packageReleaseResources > Task :expo-constants:extractDeepLinksRelease > Task :expo:processReleaseManifest package="expo.core" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/expo/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :expo-application:processReleaseManifest package="expo.modules.application" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/expo-application/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :expo-constants:processReleaseManifest package="expo.modules.constants" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/expo-constants/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :expo-file-system:extractDeepLinksRelease > Task :expo-file-system:processReleaseManifest package="expo.modules.filesystem" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/expo-file-system/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. /home/expo/workingdir/build/node_modules/expo-file-system/android/src/main/AndroidManifest.xml:8:9-10:20 Warning: provider#expo.modules.filesystem.FileSystemFileProvider@android:authorities was tagged at AndroidManifest.xml:8 to replace other declarations but no other declaration present > Task :expo-font:extractDeepLinksRelease > Task :expo-font:processReleaseManifest package="expo.modules.font" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/expo-font/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :expo-keep-awake:extractDeepLinksRelease > Task :expo-mail-composer:extractDeepLinksRelease > Task :expo-mail-composer:processReleaseManifest package="expo.modules.mailcomposer" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/expo-mail-composer/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :expo-modules-core:extractDeepLinksRelease > Task :expo-modules-core:processReleaseManifest package="expo.modules" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :expo-keep-awake:processReleaseManifest package="expo.modules.keepawake" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/expo-keep-awake/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :expo-notifications:extractDeepLinksRelease > Task :app:buildCodegenCLI SKIPPED > Task :app:generateCodegenSchemaFromJavaScript SKIPPED > Task :app:generateCodegenArtifactsFromSchema SKIPPED > Task :expo-notifications:processReleaseManifest package="expo.modules.notifications" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/expo-notifications/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :expo-permissions:extractDeepLinksRelease > Task :expo-splash-screen:extractDeepLinksRelease > Task :app:generatePackageList > Task :app:preBuild > Task :app:preReleaseBuild > Task :app:compileReleaseRenderscript NO-SOURCE > Task :expo-splash-screen:processReleaseManifest package="expo.modules.splashscreen" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/expo-splash-screen/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :expo-permissions:processReleaseManifest package="expo.modules.permissions" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/expo-permissions/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :react-native-community_datetimepicker:extractDeepLinksRelease > Task :react-native-async-storage_async-storage:extractDeepLinksRelease > Task :react-native-svg:extractDeepLinksRelease > Task :app:generateReleaseResValues > Task :react-native-async-storage_async-storage:processReleaseManifest package="com.reactnativecommunity.asyncstorage" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/@react-native-async-storage/async-storage/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :react-native-community_datetimepicker:processReleaseManifest package="com.reactcommunity.rndatetimepicker" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/@react-native-community/datetimepicker/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :react-native-svg:processReleaseManifest package="com.horcrux.svg" found in source AndroidManifest.xml: /home/expo/workingdir/build/node_modules/react-native-svg/android/src/main/AndroidManifest.xml. Setting the namespace via a source AndroidManifest.xml's package attribute is deprecated. Please instead set the namespace (or testNamespace) in the module's build.gradle file, as described here: https://developer.android.com/studio/build/configure-app-module#set-namespace This migration can be done automatically using the AGP Upgrade Assistant, please refer to https://developer.android.com/studio/build/agp-upgrade-assistant for more information. > Task :expo-application:compileReleaseLibraryResources > Task :expo-constants:compileReleaseLibraryResources > Task :expo-font:compileReleaseLibraryResources > Task :expo-keep-awake:compileReleaseLibraryResources > Task :expo-mail-composer:compileReleaseLibraryResources > Task :expo-file-system:compileReleaseLibraryResources > Task :expo-modules-core:compileReleaseLibraryResources > Task :expo-notifications:compileReleaseLibraryResources > Task :expo-permissions:compileReleaseLibraryResources > Task :react-native-async-storage_async-storage:compileReleaseLibraryResources > Task :react-native-community_datetimepicker:compileReleaseLibraryResources > Task :expo:compileReleaseLibraryResources > Task :react-native-async-storage_async-storage:compileReleaseAidl NO-SOURCE > Task :react-native-async-storage_async-storage:generateReleaseBuildConfig > Task :react-native-svg:compileReleaseLibraryResources > Task :react-native-community_datetimepicker:compileReleaseAidl NO-SOURCE > Task :react-native-community_datetimepicker:generateReleaseBuildConfig > Task :expo-splash-screen:compileReleaseLibraryResources > Task :react-native-community_datetimepicker:parseReleaseLocalResources > Task :react-native-async-storage_async-storage:javaPreCompileRelease > Task :react-native-community_datetimepicker:javaPreCompileRelease > Task :expo-modules-core:compileReleaseAidl NO-SOURCE > Task :expo-application:compileReleaseAidl NO-SOURCE > Task :expo-constants:compileReleaseAidl NO-SOURCE > Task :expo-file-system:compileReleaseAidl NO-SOURCE > Task :expo-font:compileReleaseAidl NO-SOURCE > Task :expo-keep-awake:compileReleaseAidl NO-SOURCE > Task :expo-mail-composer:compileReleaseAidl NO-SOURCE > Task :expo-notifications:compileReleaseAidl NO-SOURCE > Task :expo-permissions:compileReleaseAidl NO-SOURCE > Task :expo-splash-screen:compileReleaseAidl NO-SOURCE > Task :expo:compileReleaseAidl NO-SOURCE > Task :expo:generateReleaseBuildConfig > Task :react-native-async-storage_async-storage:parseReleaseLocalResources > Task :app:mapReleaseSourceSetPaths > Task :expo:parseReleaseLocalResources > Task :expo-application:parseReleaseLocalResources > Task :expo-modules-core:parseReleaseLocalResources > Task :react-native-async-storage_async-storage:generateReleaseRFile > Task :expo-modules-core:generateReleaseRFile > Task :react-native-community_datetimepicker:generateReleaseRFile > Task :expo-application:generateReleaseRFile > Task :expo-constants:parseReleaseLocalResources > Task :expo-constants:generateReleaseRFile > Task :expo-file-system:parseReleaseLocalResources > Task :expo-file-system:generateReleaseRFile > Task :expo-font:parseReleaseLocalResources > Task :expo-font:generateReleaseRFile > Task :expo-keep-awake:parseReleaseLocalResources > Task :expo-keep-awake:generateReleaseRFile > Task :expo-mail-composer:parseReleaseLocalResources > Task :expo-mail-composer:generateReleaseRFile > Task :expo-notifications:parseReleaseLocalResources > Task :expo-notifications:generateReleaseRFile > Task :expo-permissions:parseReleaseLocalResources > Task :app:createBundleReleaseJsAndAssets warning: the transform cache was reset. Welcome to Metro v0.73.9 Fast - Scalable - Integrated > Task :expo-permissions:generateReleaseRFile > Task :expo-splash-screen:parseReleaseLocalResources > Task :expo-splash-screen:generateReleaseRFile > Task :expo:generateReleaseRFile > Task :expo-application:generateReleaseBuildConfig > Task :expo-modules-core:generateReleaseBuildConfig > Task :react-native-async-storage_async-storage:compileReleaseJavaWithJavac [stderr] Note: /home/expo/workingdir/build/node_modules/@react-native-async-storage/async-storage/android/src/main/java/com/reactnativecommunity/asyncstorage/AsyncStorageModule.java uses or overrides a deprecated API. [stderr] Note: Recompile with -Xlint:deprecation for details. [stderr] Note: /home/expo/workingdir/build/node_modules/@react-native-async-storage/async-storage/android/src/main/java/com/reactnativecommunity/asyncstorage/AsyncStoragePackage.java uses unchecked or unsafe operations. [stderr] Note: Recompile with -Xlint:unchecked for details. > Task :react-native-community_datetimepicker:compileReleaseJavaWithJavac [stderr] Note: Some input files use or override a deprecated API. [stderr] Note: Recompile with -Xlint:deprecation for details. > Task :react-native-async-storage_async-storage:bundleLibRuntimeToJarRelease > Task :react-native-community_datetimepicker:bundleLibRuntimeToJarRelease > Task :expo-modules-core:javaPreCompileRelease > Task :expo-application:javaPreCompileRelease > Task :expo-constants:generateReleaseBuildConfig > Task :expo-file-system:generateReleaseBuildConfig > Task :expo-constants:javaPreCompileRelease > Task :expo-font:generateReleaseBuildConfig > Task :expo-font:javaPreCompileRelease > Task :expo-file-system:javaPreCompileRelease > Task :expo-keep-awake:generateReleaseBuildConfig > Task :expo-keep-awake:javaPreCompileRelease > Task :expo-mail-composer:generateReleaseBuildConfig > Task :expo-notifications:generateReleaseBuildConfig > Task :expo-notifications:javaPreCompileRelease > Task :expo-mail-composer:javaPreCompileRelease > Task :expo-permissions:generateReleaseBuildConfig > Task :expo-splash-screen:generateReleaseBuildConfig > Task :expo-permissions:javaPreCompileRelease > Task :expo-splash-screen:javaPreCompileRelease > Task :react-native-svg:compileReleaseAidl NO-SOURCE > Task :expo:javaPreCompileRelease > Task :react-native-svg:generateReleaseBuildConfig > Task :react-native-svg:parseReleaseLocalResources > Task :expo:writeReleaseAarMetadata > Task :expo-application:writeReleaseAarMetadata > Task :react-native-svg:javaPreCompileRelease > Task :expo-constants:writeReleaseAarMetadata > Task :expo-file-system:writeReleaseAarMetadata > Task :expo-font:writeReleaseAarMetadata > Task :expo-keep-awake:writeReleaseAarMetadata > Task :react-native-svg:generateReleaseRFile > Task :expo-mail-composer:writeReleaseAarMetadata > Task :expo-modules-core:writeReleaseAarMetadata > Task :expo-notifications:writeReleaseAarMetadata > Task :expo-permissions:writeReleaseAarMetadata > Task :expo-splash-screen:writeReleaseAarMetadata > Task :react-native-async-storage_async-storage:writeReleaseAarMetadata > Task :react-native-community_datetimepicker:writeReleaseAarMetadata > Task :react-native-async-storage_async-storage:bundleLibCompileToJarRelease > Task :react-native-community_datetimepicker:bundleLibCompileToJarRelease > Task :expo:mergeReleaseShaders > Task :expo:compileReleaseShaders NO-SOURCE > Task :expo:generateReleaseAssets UP-TO-DATE > Task :expo:packageReleaseAssets > Task :expo-application:mergeReleaseShaders > Task :expo-application:compileReleaseShaders NO-SOURCE > Task :expo-application:generateReleaseAssets UP-TO-DATE > Task :expo-application:packageReleaseAssets > Task :expo-constants:mergeReleaseShaders > Task :expo-constants:compileReleaseShaders NO-SOURCE > Task :expo-constants:createReleaseExpoConfig Execution optimizations have been disabled for task ':expo-constants:createReleaseExpoConfig' to ensure correctness due to the following reasons: - Gradle detected a problem with the following location: '/home/expo/workingdir/build/android'. Reason: Task ':expo-constants:createReleaseExpoConfig' uses this output of task ':app:compileReleaseRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. - Gradle detected a problem with the following location: '/home/expo/workingdir/build/android'. Reason: Task ':expo-constants:createReleaseExpoConfig' uses this output of task ':app:createBundleReleaseJsAndAssets' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. - Gradle detected a problem with the following location: '/home/expo/workingdir/build/android'. Reason: Task ':expo-constants:createReleaseExpoConfig' uses this output of task ':app:generateReleaseResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. - Gradle detected a problem with the following location: '/home/expo/workingdir/build/android'. Reason: Task ':expo-constants:createReleaseExpoConfig' uses this output of task ':app:mapReleaseSourceSetPaths' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. > Task :expo-constants:copyReleaseExpoConfig > Task :expo-constants:generateReleaseAssets UP-TO-DATE > Task :expo-constants:packageReleaseAssets > Task :expo-file-system:mergeReleaseShaders > Task :expo-file-system:compileReleaseShaders NO-SOURCE > Task :expo-file-system:generateReleaseAssets UP-TO-DATE > Task :expo-file-system:packageReleaseAssets > Task :expo-font:mergeReleaseShaders > Task :expo-font:compileReleaseShaders NO-SOURCE > Task :expo-font:generateReleaseAssets UP-TO-DATE > Task :expo-font:packageReleaseAssets > Task :expo-keep-awake:mergeReleaseShaders > Task :expo-keep-awake:compileReleaseShaders NO-SOURCE > Task :expo-keep-awake:generateReleaseAssets UP-TO-DATE > Task :expo-keep-awake:packageReleaseAssets > Task :expo-mail-composer:mergeReleaseShaders > Task :expo-mail-composer:compileReleaseShaders NO-SOURCE > Task :expo-mail-composer:generateReleaseAssets UP-TO-DATE > Task :expo-mail-composer:packageReleaseAssets > Task :expo-modules-core:mergeReleaseShaders > Task :expo-modules-core:compileReleaseShaders NO-SOURCE > Task :expo-modules-core:generateReleaseAssets UP-TO-DATE > Task :expo-modules-core:packageReleaseAssets > Task :expo-notifications:mergeReleaseShaders > Task :expo-notifications:compileReleaseShaders NO-SOURCE > Task :expo-notifications:generateReleaseAssets UP-TO-DATE > Task :expo-notifications:packageReleaseAssets > Task :expo-permissions:mergeReleaseShaders > Task :expo-permissions:compileReleaseShaders NO-SOURCE > Task :expo-permissions:generateReleaseAssets UP-TO-DATE > Task :expo-permissions:packageReleaseAssets > Task :expo-splash-screen:mergeReleaseShaders > Task :expo-splash-screen:compileReleaseShaders NO-SOURCE > Task :expo-splash-screen:generateReleaseAssets UP-TO-DATE > Task :expo-splash-screen:packageReleaseAssets > Task :react-native-async-storage_async-storage:mergeReleaseShaders > Task :react-native-async-storage_async-storage:compileReleaseShaders NO-SOURCE > Task :react-native-async-storage_async-storage:generateReleaseAssets UP-TO-DATE > Task :react-native-async-storage_async-storage:packageReleaseAssets > Task :react-native-community_datetimepicker:mergeReleaseShaders > Task :react-native-community_datetimepicker:compileReleaseShaders NO-SOURCE > Task :react-native-community_datetimepicker:generateReleaseAssets UP-TO-DATE > Task :react-native-community_datetimepicker:packageReleaseAssets > Task :expo:processReleaseJavaRes NO-SOURCE > Task :expo-application:processReleaseJavaRes NO-SOURCE > Task :expo-constants:cleanupReleaseExpoConfig > Task :expo-constants:processReleaseJavaRes NO-SOURCE > Task :expo-file-system:processReleaseJavaRes NO-SOURCE > Task :expo-font:processReleaseJavaRes NO-SOURCE > Task :expo-keep-awake:processReleaseJavaRes NO-SOURCE > Task :expo-mail-composer:processReleaseJavaRes NO-SOURCE > Task :expo-modules-core:processReleaseJavaRes NO-SOURCE > Task :expo-notifications:processReleaseJavaRes NO-SOURCE > Task :expo-permissions:processReleaseJavaRes NO-SOURCE > Task :expo-splash-screen:processReleaseJavaRes NO-SOURCE > Task :react-native-async-storage_async-storage:processReleaseJavaRes NO-SOURCE > Task :react-native-async-storage_async-storage:bundleLibResRelease NO-SOURCE > Task :react-native-community_datetimepicker:processReleaseJavaRes NO-SOURCE > Task :react-native-community_datetimepicker:bundleLibResRelease NO-SOURCE > Task :expo:mergeReleaseJniLibFolders > Task :expo:mergeReleaseNativeLibs NO-SOURCE > Task :expo:copyReleaseJniLibsProjectOnly > Task :expo-application:mergeReleaseJniLibFolders > Task :expo-application:mergeReleaseNativeLibs NO-SOURCE > Task :expo-application:copyReleaseJniLibsProjectOnly > Task :expo-constants:mergeReleaseJniLibFolders > Task :expo-constants:mergeReleaseNativeLibs NO-SOURCE > Task :expo-constants:copyReleaseJniLibsProjectOnly > Task :expo-file-system:mergeReleaseJniLibFolders > Task :expo-file-system:mergeReleaseNativeLibs NO-SOURCE > Task :expo-file-system:copyReleaseJniLibsProjectOnly > Task :expo-font:mergeReleaseJniLibFolders > Task :expo-font:mergeReleaseNativeLibs NO-SOURCE > Task :expo-font:copyReleaseJniLibsProjectOnly > Task :expo-keep-awake:mergeReleaseJniLibFolders > Task :expo-keep-awake:mergeReleaseNativeLibs NO-SOURCE > Task :expo-keep-awake:copyReleaseJniLibsProjectOnly > Task :expo-mail-composer:mergeReleaseJniLibFolders > Task :expo-mail-composer:mergeReleaseNativeLibs NO-SOURCE > Task :expo-mail-composer:copyReleaseJniLibsProjectOnly > Task :expo-modules-core:configureCMakeRelWithDebInfo[arm64-v8a] > Task :react-native-svg:compileReleaseJavaWithJavac [stderr] Note: /home/expo/workingdir/build/node_modules/react-native-svg/android/src/main/java/com/horcrux/svg/VirtualView.java uses or overrides a deprecated API. [stderr] Note: Recompile with -Xlint:deprecation for details. [stderr] Note: Some input files use unchecked or unsafe operations. [stderr] Note: Recompile with -Xlint:unchecked for details. > Task :react-native-svg:bundleLibRuntimeToJarRelease > Task :expo-modules-core:compileReleaseKotlin > Task :react-native-svg:writeReleaseAarMetadata > Task :react-native-svg:bundleLibCompileToJarRelease > Task :react-native-svg:mergeReleaseShaders > Task :react-native-svg:compileReleaseShaders NO-SOURCE > Task :react-native-svg:generateReleaseAssets UP-TO-DATE > Task :react-native-svg:packageReleaseAssets > Task :react-native-svg:processReleaseJavaRes NO-SOURCE > Task :react-native-svg:bundleLibResRelease NO-SOURCE > Task :expo-notifications:mergeReleaseJniLibFolders > Task :expo-notifications:mergeReleaseNativeLibs NO-SOURCE > Task :expo-notifications:copyReleaseJniLibsProjectOnly > Task :expo-permissions:mergeReleaseJniLibFolders > Task :expo-permissions:mergeReleaseNativeLibs NO-SOURCE > Task :expo-permissions:copyReleaseJniLibsProjectOnly > Task :expo-splash-screen:mergeReleaseJniLibFolders > Task :expo-splash-screen:mergeReleaseNativeLibs NO-SOURCE > Task :expo-splash-screen:copyReleaseJniLibsProjectOnly > Task :react-native-async-storage_async-storage:mergeReleaseJniLibFolders > Task :react-native-async-storage_async-storage:mergeReleaseNativeLibs NO-SOURCE > Task :react-native-async-storage_async-storage:copyReleaseJniLibsProjectOnly > Task :react-native-community_datetimepicker:mergeReleaseJniLibFolders > Task :react-native-community_datetimepicker:mergeReleaseNativeLibs NO-SOURCE > Task :react-native-community_datetimepicker:copyReleaseJniLibsProjectOnly > Task :react-native-svg:mergeReleaseJniLibFolders > Task :react-native-svg:mergeReleaseNativeLibs NO-SOURCE > Task :react-native-svg:copyReleaseJniLibsProjectOnly > Task :expo:prepareReleaseArtProfile > Task :expo-application:prepareReleaseArtProfile > Task :expo-constants:prepareReleaseArtProfile > Task :expo-file-system:prepareReleaseArtProfile > Task :expo-font:prepareReleaseArtProfile > Task :expo-keep-awake:prepareReleaseArtProfile > Task :expo-mail-composer:prepareReleaseArtProfile > Task :expo-notifications:prepareReleaseArtProfile > Task :expo-permissions:prepareReleaseArtProfile > Task :expo-splash-screen:prepareReleaseArtProfile > Task :react-native-async-storage_async-storage:prepareReleaseArtProfile > Task :react-native-community_datetimepicker:prepareReleaseArtProfile > Task :react-native-svg:prepareReleaseArtProfile > Task :expo-modules-core:buildCMakeRelWithDebInfo[arm64-v8a] > Task :app:createBundleReleaseJsAndAssets Error: Unable to resolve module ../firebase.json from /home/expo/workingdir/build/src/firebase.js: None of these files exist: * firebase.json(.native|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx|.android.js|.native.js|.js|.android.jsx|.native.jsx|.jsx|.android.json|.native.json|.json) * firebase.json/index(.native|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx|.android.js|.native.js|.js|.android.jsx|.native.jsx|.jsx|.android.json|.native.json|.json) 20 | } from "firebase/firestore"; 21 | import {getDownloadURL, getStorage, ref, uploadBytes} from "firebase/storage"; > 22 | import config from "../firebase.json"; | ^ 23 | import "firebase/firestore"; 24 | import {Alert} from "react-native"; 25 | at ModuleResolver.resolveDependency (/home/expo/workingdir/build/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:137:15) at DependencyGraph.resolveDependency (/home/expo/workingdir/build/node_modules/metro/src/node-haste/DependencyGraph.js:260:43) at Object.resolve (/home/expo/workingdir/build/node_modules/metro/src/lib/transformHelpers.js:177:21) at Graph._resolveDependencies (/home/expo/workingdir/build/node_modules/metro/src/DeltaBundler/Graph.js:432:35) at Graph._processModule (/home/expo/workingdir/build/node_modules/metro/src/DeltaBundler/Graph.js:218:38) at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) at async Graph._addDependency (/home/expo/workingdir/build/node_modules/metro/src/DeltaBundler/Graph.js:314:20) at async Promise.all (index 11) at async Graph._processModule (/home/expo/workingdir/build/node_modules/metro/src/DeltaBundler/Graph.js:263:5) [stderr] error Unable to resolve module ../firebase.json from /home/expo/workingdir/build/src/firebase.js: [stderr] None of these files exist: [stderr] * firebase.json(.native|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx|.android.js|.native.js|.js|.android.jsx|.native.jsx|.jsx|.android.json|.native.json|.json) [stderr] * firebase.json/index(.native|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx|.android.js|.native.js|.js|.android.jsx|.native.jsx|.jsx|.android.json|.native.json|.json) [stderr] 20 | } from "firebase/firestore"; [stderr] 21 | import {getDownloadURL, getStorage, ref, uploadBytes} from "firebase/storage"; [stderr] > 22 | import config from "../firebase.json"; [stderr] | ^ [stderr] 23 | import "firebase/firestore"; [stderr] 24 | import {Alert} from "react-native"; [stderr] 25 | > Task :app:createBundleReleaseJsAndAssets FAILED > Task :expo-modules-core:configureCMakeRelWithDebInfo[armeabi-v7a] > Task :expo-modules-core:compileReleaseKotlin w: Argument -Xopt-in is deprecated. Please use -opt-in instead w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/adapters/react/permissions/PermissionsService.kt:157:30 'getPackageInfo(String, Int): PackageInfo!' is deprecated. Deprecated in Java w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/core/utilities/EmulatorUtilities.kt:30:13 'SERIAL: String!' is deprecated. Deprecated in Java w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/Promise.kt:68:18 This declaration overrides deprecated member but not marked as deprecated itself. This deprecation won't be inherited in future releases. Please add @Deprecated annotation or suppress. See https://youtrack.jetbrains.com/issue/KT-47902 for details w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/activityresult/ActivityResultsManager.kt:52:24 Parameter 'activity' is never used w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/activityresult/AppContextActivityResultRegistry.kt:119:51 'getParcelableExtra(String!): T?' is deprecated. Deprecated in Java w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/activityresult/AppContextActivityResultRegistry.kt:180:26 'getParcelable(String?): T?' is deprecated. Deprecated in Java w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/activityresult/AppContextActivityResultRegistry.kt:271:83 'getParcelable(String?): T?' is deprecated. Deprecated in Java w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/activityresult/DataPersistor.kt:67:20 'getSerializable(String?): Serializable?' is deprecated. Deprecated in Java w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/activityresult/DataPersistor.kt:85:26 'getSerializable(String?): Serializable?' is deprecated. Deprecated in Java w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/events/KModuleEventEmitterWrapper.kt:90:7 'constructor Event<T : Event<(raw) Event<*>>!>(Int)' is deprecated. Deprecated in Java w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/jni/JavaScriptObject.kt:59:33 Parameter 'null' is never used w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/jni/JavaScriptObject.kt:100:5 Parameter 'null' is never used w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/modules/Module.kt:43:7 'coroutineScope: CoroutineScope' is deprecated. Use a scope from the AppContext w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/types/Either.kt:24:11 Parameter 'type' is never used w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/types/Either.kt:27:11 Parameter 'type' is never used w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/types/Either.kt:44:11 Parameter 'type' is never used w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/types/Either.kt:59:11 Parameter 'type' is never used w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/types/JSTypeConverterHelper.kt:44:17 'get(String!): Any?' is deprecated. Deprecated in Java w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/views/ViewManagerDefinitionBuilder.kt:125:30 'ViewGroupDefinitionLegacyBuilder' is deprecated. Use `ViewGroupDefinitionBuilder` instead. w: file:///home/expo/workingdir/build/node_modules/expo-modules-core/android/src/main/java/expo/modules/kotlin/views/ViewManagerDefinitionBuilder.kt:128:38 'ViewGroupDefinitionLegacyBuilder' is deprecated. Use `ViewGroupDefinitionBuilder` instead. [stderr] FAILURE: Build completed with 2 failures. [stderr] 1: Task failed with an exception. [stderr] ----------- [stderr] * What went wrong: [stderr] Execution failed for task ':app:createBundleReleaseJsAndAssets'. [stderr] > Process 'command 'node'' finished with non-zero exit value 1 [stderr] * Try: [stderr] > Run with --stacktrace option to get the stack trace. [stderr] > Run with --info or --debug option to get more log output. [stderr] > Run with --scan to get full insights. [stderr] ============================================================================== [stderr] 2: Task failed with an exception. [stderr] ----------- [stderr] * What went wrong: [stderr] java.lang.StackOverflowError (no error message) [stderr] * Try: [stderr] > Run with --stacktrace option to get the stack trace. [stderr] > Run with --info or --debug option to get more log output. [stderr] > Run with --scan to get full insights. [stderr] ============================================================================== [stderr] * Get more help at https://help.gradle.org [stderr] BUILD FAILED in 4m 2s Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness. Please consult deprecation warnings for more details. 233 actionable tasks: 233 executed Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information. 뭐가 중요한지 잘 모르겠어서 다 올려봅니다 ㅜㅜ 특히Error: Unable to resolve module ../firebase.json from /home/expo/workingdir/build/src/firebase.js: 552 None of these files exist: 553 * firebase.json(.native|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx|.android.js|.native.js|.js|.android.jsx|.native.jsx|.jsx|.android.json|.native.json|.json) 554 * firebase.json/index(.native|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx|.android.js|.native.js|.js|.android.jsx|.native.jsx|.jsx|.android.json|.native.json|.json) 555 20 | } from "firebase/firestore"; 556 21 | import {getDownloadURL, getStorage, ref, uploadBytes} from "firebase/storage"; 557 > 22 | import config from "../firebase.json"; 558 | ^ 559 23 | import "firebase/firestore"; 560 24 | import {Alert} from "react-native"; 561 25 |firebase.json 은 멀쩡히 잘 있는데 왜 이부분을 에러로 잡는 것인지 이해가 안되네요 ㅜㅜfirebase.json은 eas.json과 같은 위치에 존재하며 이렇게 되어있습니다..{ "apiKey": "가리겠습니다.", "authDomain": "jlog-68247.firebaseapp.com", "projectId": "jlog-68247", "storageBucket": "jlog-68247.appspot.com", "messagingSenderId": "3256831280", "appId": "1:3256831280:web:6775122b75c903b78accf5", "measurementId": "G-DZSQ5BPSSM", "hosting": { "public": "public", "ignore": [ "firebase.json", "**/.*", "**/node_modules/**" ] } }깃헙주소는 https://github.com/KongGeon/jlog2 입니다.
-
미해결스프링 시큐리티 OAuth2
oauth2clinet api 사용 이유?
시큐리티 필터체인 구성 시 oauth2login api를 사용하면 되는데 굳이 oauth2client를 사용할 이유가 어떤것이 있을까요?
-
미해결[리뉴얼] React로 NodeBird SNS 만들기
글작성시 userId가 데이터에 저장을 안해서 게시글을 가져올려고 해도 안가져와집니다.
1. 뭔가 프론트는 문제가 없는거같은데 백에서는 어디에서 문제가 있는지 잘모르겠습니다 ㅠㅠ에러는 없습니다3. const express = require("express"); const { Post, Image, Comment, User } = require("../models"); const { isLoggedIn } = require("./middlewares"); const router = express.Router(); router.post("/", isLoggedIn, async (req, res) => { try { const post = await Post.create({ content: req.body.content, UserId: req.user.id, }); const fullPost = await Post.findOne({ where: { id: post.id }, include: [ { model: Image, }, { model: Comment, include: [ { model: User, // 댓글 작성자 attributes: ["id", "nickname"], }, ], }, { model: User, // 게시글 작성자 attributes: ["id", "nickname"], }, { model: User, // 좋아요 누른 사람 as: "Likers", attributes: ["id"], }, ], }); res.status(201).json(fullPost); } catch (error) { console.error(error); next(error); } }); router.post("/:postId/comment", isLoggedIn, async (req, res) => { try { const post = await Post.findOne({ where: { id: req.params.postId }, }); if (!post) { return res.status(403).send("존재하지 않는 게시글입니다"); //return을 붙여줘야지 send하고 밑에 json이 동시에 실행안됨 } const comment = await Comment.create({ content: req.body.content, PostId: req.params.postId, UserId: req.user.id, }); res.status(201).json(comment); } catch (error) { console.error(error); next(error); } }); router.delete("/", (req, res) => { res.json({}); }); module.exports = router; import { Form, Input, Button } from "antd"; import { useCallback, useRef, useEffect, useState } from "react"; import { useDispatch, useSelector } from "react-redux"; import { ADD_POST_REQUEST } from "../reducers/post"; import useInput from "./hooks/useInput"; const PostForm = () => { const { imagePaths, addPostDone, addPostLoading } = useSelector( (state) => state.post ); const [text, setText] = useState(""); const dispatch = useDispatch(); const imageInput = useRef(); useEffect(() => { if (addPostDone) { setText(""); } }, [addPostDone]); const onSubmitForm = useCallback(() => { dispatch({ type: ADD_POST_REQUEST, data: text, }); }, [text]); const onChangeText = useCallback((e) => { setText(e.target.value); }, []); const onClickImageUpload = useCallback(() => { imageInput.current.click(); }, [imageInput.current]); return ( <Form style={{ margin: "10px 0 20px" }} encType="multipart/form-data" onFinish={onSubmitForm} > <Input.TextArea value={text} onChange={onChangeText} maxLength={140} placeholder="어떤 일이 생겼나요" /> <div> <input type="file" multiple hidden ref={imageInput} /> <Button onClick={onClickImageUpload}>이미지 업로드</Button> <Button type="primary" style={{ float: "right" }} htmlType="submit" loading={addPostLoading} > 짹쨱 </Button> </div> <div> {imagePaths.map((v) => ( <div key={v} style={{ display: "inline-block" }}> <img src={v} style={{ width: "200px" }} alt={v} /> <div> <Button>제거</Button> </div> </div> ))} </div> </Form> ); }; export default PostForm; //saga - AddPost function addPostAPI(data) { return axios.post("/post", { content: data }); } function* addPost(action) { try { const result = yield call(addPostAPI, action.data); yield put({ //put : dispatch type: ADD_POST_SUCCESS, data: result.data, }); yield put({ type: ADD_POST_TO_ME, data: result.data.id, }); } catch (err) { yield put({ type: ADD_POST_FAILURE, data: err.response.data, }); } } // reducer case ADD_POST_REQUEST: draft.addPostLoading = true; draft.addPostDone = false; draft.addPostError = null; break; case ADD_POST_SUCCESS: draft.addPostLoading = false; draft.addPostDone = true; draft.mainPosts.unshift(action.data); break; case ADD_POST_FAILURE: draft.addPostLoading = false; draft.addPostError = action.error; break;
-
해결됨스프링 입문 - 코드로 배우는 스프링 부트, 웹 MVC, DB 접근 기술
회원가입 테스트 코드는 실행이 잘 되지만 실제 DB에는 올라가지 않아요
학습하는 분들께 도움이 되고, 더 좋은 답변을 드릴 수 있도록 질문전에 다음을 꼭 확인해주세요.1. 강의 내용과 관련된 질문을 남겨주세요.2. 인프런의 질문 게시판과 자주 하는 질문(링크)을 먼저 확인해주세요.(자주 하는 질문 링크: https://bit.ly/3fX6ygx)3. 질문 잘하기 메뉴얼(링크)을 먼저 읽어주세요.(질문 잘하기 메뉴얼 링크: https://bit.ly/2UfeqCG)질문 시에는 위 내용은 삭제하고 다음 내용을 남겨주세요.=========================================[질문 템플릿]1. 강의 내용과 관련된 질문인가요? (예/아니오)2. 인프런의 질문 게시판과 자주 하는 질문에 없는 내용인가요? (예/아니오)3. 질문 잘하기 메뉴얼을 읽어보셨나요? (예/아니오)[질문 내용]안녕하세요 TEST코드가 실행은 잘 되지만 실제 DB에 올라가지 않는 문제가 있습니다. 도움을 받을 수 있을까 해서 올려봅니다.https://drive.google.com/file/d/1dLceWpDp71m9dsvZXlVEfKa1db8M885g/view?usp=sharing파일링크입니다!
-
해결됨20년 경력자의 알기쉬운 컴퓨터네트워크
무선 라우터에서 buffer frame
다음과 같은 토폴로지에서 ED0에서 Server0으로 ping 테스트를 진행했을때, 패킷이 server0에 도착하였을때쯤 갑자기 Wireless Router0에서 End Device 전체로 메시지가 전송됨을 확인했습니다.패킷 상세를 확인해보니, buffer 가 되어있던 메시지를 보낸거라고 하는데.( “The device takes out this frame from the buffer and sends it.”) 왜 buffer에 메시지가 저장된건가요? 패킷 낭비같은데..이걸 막을 수 있는 방법은 없나요?
-
미해결2025 정보처리기사 필기
POINT 50
포인트 50에 대한 강의가 누락된 것 같은데 확인 가능할까요??