Содержание
- [Expo 35]Keep getting error Could not determine «artifacts for com.github.Raizlabs.DBFlow:dbflow:4.2.4» #5847
- Comments
- Footer
- Android build/installation error: Cannot download from bintray #295
- Comments
- Android Build failing, unable to download from Google Repository #568
- Comments
- Русские Блоги
- Android Could not determine artifacts for XXXX: Skipped due to earlier error
- Интеллектуальная рекомендация
- Платформа Hybris E-Commerce Platform Service Практика
- Метод даты JS.
- Расчетная схема мультиплексной пересылки RTSP / RTMP на основе шифрования AES
- Инициализация сеанса ненормальная проблема в рамках web.py
- FAQ по программному обеспечению MD sp1
- Could not resolve all task dependencies for configuration ‘:app:debugCompileClasspath’ #71104
- Comments
- Steps to Reproduce
- Steps to Reproduce
[Expo 35]Keep getting error Could not determine «artifacts for com.github.Raizlabs.DBFlow:dbflow:4.2.4» #5847
My project is ejected from Expo 35.
I checked my app/build.gradle and I do not have any DBFlow stuff in it.
But when I run gradlew build or gradlew test . I am keeping getting this error:
I am not familiar with gradle and I am not sure where this comes from.
Can anyone help?
The text was updated successfully, but these errors were encountered:
I think it comes from here:
annotationProcessor » com.github.Raizlabs.DBFlow:dbflow-processor: $ < safeExtGet(‘dbFlowVersion’, ‘4.2.4’) >«
If that is the case, we should update the docs to tell users to upgrade DbFlow instead of removing it
#5749
I just fixed this by adding below code to my app/build.gradle :
I had the same error when upgrading from 34 to 35, but it went away by clearing the cache with expo r -c (Without having to add DBFlow back to app/build.gradle )
@NiciusB was that all you did? I’ve tried your way, deleting all the gradle caches I could find, and node_modules, and tried adding back with updated version as described above. Still, I always get this:
Not sure what the earlier error is supposed to be about. gradle-5.1.1 due to some firebase things added.
@aslakrin I don’t know much about gradle, but maybe opening android studio and updating gradle helps? I did that before getting the error (and then clearing the cache), but it doesn’t seem to be related to the problem
@NiciusB I tried your solution. It didn’t work.
I’m facing a same error.
In my case, my local build ( ./gradlew bundleDebug on my Mac) works but production build on Bitrise ( $ /Users/vagrant/git/android/gradlew «:app:bundleRelease» ) fails.
I tried solutions above but did not work;
- Add dependenies of com.github.Raizlabs.DBFlow in app/build.gradle
- Clear cache before gradlew command by expo publish —clear —release-channel my-production-channel
- Update gradle version by opening the project with Android Studio
Does anyone know other things I can try?
I am stuck with this issue.
these lines do not exist in my app/build.gradle file and still getting the error
annotationProcessor «com.github.Raizlabs.DBFlow:dbflow-processor:4.2.4»
implementation «com.github.Raizlabs.DBFlow:dbflow-core:4.2.4»
implementation «com.github.Raizlabs.DBFlow:dbflow:4.2.4»
> Could not determine artifacts for com.github.Raizlabs.DBFlow:dbflow:4.2.4:
cannot build. any help you be greatly appreciated
Gradle seems to be able to sync for me when I change android/build.gradle -> allprojects < repositories < /* . others. */ maven < url ‘https://jitpack.io’ >. and add www in front, so it’s www.jitpack.io
Gradle seems to be able to sync for me when I change android/build.gradle -> allprojects < repositories < /* . others. */ maven < url ‘https://jitpack.io’ >. and add www in front, so it’s www.jitpack.io
It also works for me! Thank you!!
@aslakrin Have you also added this back ?
© 2023 GitHub, Inc.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
Android build/installation error: Cannot download from bintray #295
After following the docs and installing the library I try to build and get the following error, seems bintray has been sunset:
Stack:
@notifee/react-native: 4.0.1
react-native: 0.64
The text was updated successfully, but these errors were encountered:
Worked after an hour, bintray was down
I keep periodically getting issues with accessing bintray when I build, can we bypass bintray please?
@MrShakes you can, you need to update react-native though, it’s out of control of this module. Use react-native 0.65 or greater. 0.66.4 is current now — https://react-native-community.github.io/upgrade-helper/
@MrShakes you can, you need to update react-native though, it’s out of control of this module. Use react-native 0.65 or greater. 0.66.4 is current now — https://react-native-community.github.io/upgrade-helper/
Hi @mikehardy — we are currently on react-native version 0.61.2 and likely to update to 0.63.4 in the near future but 0.65 is out of the question. Does Notifee only support 0.65 and higher and do you suggest those versions because jcenter is removed from Android templates?
We are getting this error which I believe to be the same:
We can remove the dependency on jcenter but would like to know if it’s hosted on some other maven repo — is there anyway it’s possible?
I can only say you should really revisit the «out of the question» project constraint for moving forward to newer react-native versions.
react-native 0.65 is the first version that even builds with current Xcode versions (Xcode 12.5+)
react-native 0.65 is the first version that no longer depends on jcenter, which is flaky now
But I must emphasize: This is out of control of this module
Notifee does not use jcenter. The basic android build system for react-native
Thanks for the feedback @mikehardy — like I said, we can bypass jcenter in react-native 0.61.2 (we already do), using 0.65 is not possible for us. If notifee does not use jcenter, then why do we only get these errors after installing notifee? In the notifee docs, it says that 0.60.0+ is supported, is that not the case? If you do support 0.60 then there must be a solution.. Many thanks!
Find jcenter in our source tree (clone it, run simple recursive grep), and we can continue searching for solutions here. Otherwise your problem is elsewhere
Also worth noting, we could be compatible with react-native 0.54, and it would still not work. Because react native that old won’t work
All false positives from test fixtures and the like. jcenter is not in use. Notifee is jcenter-clean.
Proof it works, even as far back as react-native 0.61.2 (though that was a mess: metro-react-native-babel-preset has issues, and you have to use Xcode 12.4, and who knows what incompatibilities that has with android 12 / iOS15 etc. )
This issue is closed from a notifee perspective. jcenter is not in this module. It is out of our control.
Источник
Android Build failing, unable to download from Google Repository #568
Android builds were working fine until I updated the google play services libs to version 7.8 which lives in the Google Repository. So how can the build task be configured to fetch modules from the Google Repository at build time?
2015-09-22T02:02:08.5243267Z ##[error]FAILURE: Build failed with an exception.
2015-09-22T02:02:08.5374425Z ##[error]* What went wrong:
2015-09-22T02:02:08.5374425Z ##[error]A problem occurred configuring project ‘:app’.
2015-09-22T02:02:08.5374425Z ##[error]> Could not resolve all dependencies for configuration ‘:app:_debugCompile’.
2015-09-22T02:02:08.5374425Z ##[error]> Could not find com.google.android.gms:play-services-gcm:7.8.0.
2015-09-22T02:02:08.5374425Z ##[error]Searched in the following locations:
The text was updated successfully, but these errors were encountered:
Is there a way to pass additional repository locations as part of a config file or something in your project?
It can be installed using a command.
android update sdk —no-ui —all —filter «extra-google-m2repository»
Travis CI was having a similar issue :
travis-ci/travis-ci#2470
Hi @jd-alexander, I verified we are packing google play services ver. 7.8 currently, and I just submitted a change to update our hosted VM image to the latest Android SDK versions. I am not sure if we should dynamically update the SDK version at this moment though.
Please reopen or create a new issue if you run into similar problems again.
Источник
Русские Блоги
Android Could not determine artifacts for XXXX: Skipped due to earlier error
Эта ошибка com.github.cymchad: baserecyclecleviewaDapterhelper: 2.9.0: Эта погашенная упаковка не загружается, больше синхронизации несколько раз, возможно, скачать его, попробуйте еще больше
Интеллектуальная рекомендация
Платформа Hybris E-Commerce Platform Service Практика
Диаграммы поиска платформы электронной коммерции С быстрым развитием платформы электронной коммерции и количеству продаж товаров становится более сложным из большого количества товаров в большом колич.
Метод даты JS.
содержание Дата JavaScript Дата JavaScript.
Расчетная схема мультиплексной пересылки RTSP / RTMP на основе шифрования AES
Многие разработчики недавно консультировались с нами. За исключением того, что аудио- и видеоданные, собранные и закодированные с помощью нашего push-терминала Windows, могут быть зашифрованы, что, ес.
Инициализация сеанса ненормальная проблема в рамках web.py
При определении сеанса настройка начального значения используется для использования инициализатора, например, как Здесь я хочу сохранить два ключа в сеансе для входа в систему и имени, и инициализиров.
FAQ по программному обеспечению MD sp1
FAQ по программному обеспечению MD sp1 Сущность №:40 С форума: Липкие медведи онлайн «MD / MP3 / Walkman Forum» Описание содержания: 1. Мой компьютер не распознает NETMD! Что делать? .
Источник
Could not resolve all task dependencies for configuration ‘:app:debugCompileClasspath’ #71104
Steps to Reproduce
- Run flutter create first_app .
- Run cd first_app
- Run flutter run
I used the starter template app that I got with flutter create
Expected results:
App to start on the plugged in android device
Actual results:
Error build failed.
Some extra info:
I am new to flutter and just tested creating and running the template app when i got this error. I tried running it in Android Studio (with the plugin) but same problem. I googled around the entire day yesterday with no luck. Found a couple of similarly titled problems and tried the solutions but nothing helped [flutter clean; flutter upgrade; flutter pub cache repair; to name a few] . I am using an old version of Mac mini; OS X El Capitan (10.11.6). I don’t know if that can be part of the problem but shouldn’t be as I am trying to run it on android device not an apple device [also why old version of xcode shouldn’t matter]. The flutter doctor says that the flutter and dart plugins aren’t installed but they actually are and i have seen thats a bug but shouldn’t affect the build. Also I am using a plugged in galaxy s7 to run. Thank you for the help.
The text was updated successfully, but these errors were encountered:
@eliper3
Can you try to switch to latest master and try again to see if it works or get similar issue ?
Thanks.
@eliper3
Can you try to switch to latest master and try again to see if it works or get similar issue ?
Thanks.
I already have the latest stable version (1.22.4). I just downloaded it yesterday. Unless you want me to download the last unstable one?
@eliper3
You may try that to check if this is specific to stable version or not. Also provide app level and project level build.gradle files.
Steps to Reproduce
- Run flutter create first_app .
- Run cd first_app
- Run flutter run
I used the starter template app that I got with flutter create
Expected results:
App to start on the plugged in android device
Actual results:
Error build failed.
Logs
Some extra info:
I am new to flutter and just tested creating and running the template app when i got this error. I tried running it in Android Studio (with the plugin) but same problem. I googled around the entire day yesterday with no luck. Found a couple of similarly titled problems and tried the solutions but nothing helped [flutter clean; flutter upgrade; flutter pub cache repair; to name a few] . I am using an old version of Mac mini; OS X El Capitan (10.11.6). I don’t know if that can be part of the problem but shouldn’t be as I am trying to run it on android device not an apple device [also why old version of xcode shouldn’t matter]. The flutter doctor says that the flutter and dart plugins aren’t installed but they actually are and i have seen thats a bug but shouldn’t affect the build. Also I am using a plugged in galaxy s7 to run. Thank you for the help.
i have same issue for this flutter version.
Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don’t hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v .
All system setups can be slightly different, so it’s always better to open new issues and reference related issues.
Источник
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
Comments
My project is ejected from Expo 35.
I checked my app/build.gradle
and I do not have any DBFlow
stuff in it.
But when I run gradlew build
or gradlew test
. I am keeping getting this error:
Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
Could not determine artifacts for com.github.Raizlabs.DBFlow:dbflow:4.2.4
I am not familiar with gradle and I am not sure where this comes from.
Can anyone help?
Copy link
Contributor
Author
Copy link
Contributor
Author
If that is the case, we should update the docs to tell users to upgrade DbFlow
instead of removing it
#5749
Copy link
Contributor
Author
I just fixed this by adding below code to my app/build.gradle
:
annotationProcessor "com.github.Raizlabs.DBFlow:dbflow-processor:4.2.4"
implementation "com.github.Raizlabs.DBFlow:dbflow-core:4.2.4"
implementation "com.github.Raizlabs.DBFlow:dbflow:4.2.4"
I had the same error when upgrading from 34 to 35, but it went away by clearing the cache with expo r -c
(Without having to add DBFlow back to app/build.gradle
)
@NiciusB was that all you did? I’ve tried your way, deleting all the gradle caches I could find, and node_modules, and tried adding back with updated version as described above. Still, I always get this:
FAILURE: Build failed with an exception.
* What went wrong:
Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
> Could not determine artifacts for com.github.Raizlabs.DBFlow:dbflow:4.2.4: Skipped due to earlier error
Not sure what the earlier error is supposed to be about. gradle-5.1.1 due to some firebase things added.
@aslakrin I don’t know much about gradle, but maybe opening android studio and updating gradle helps? I did that before getting the error (and then clearing the cache), but it doesn’t seem to be related to the problem
Copy link
Contributor
Author
@NiciusB I tried your solution. It didn’t work.
I’m facing a same error.
In my case, my local build (./gradlew bundleDebug
on my Mac) works but production build on Bitrise ($ /Users/vagrant/git/android/gradlew ":app:bundleRelease"
) fails.
> Task :app:preReleaseBuild FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:preReleaseBuild'.
> Could not resolve all dependencies for configuration ':app:releaseRuntimeClasspath'.
> Could not determine artifacts for com.github.Raizlabs.DBFlow:dbflow:4.2.4: Skipped due to earlier error
I tried solutions above but did not work;
- Add dependenies of
com.github.Raizlabs.DBFlow
in app/build.gradle - Clear cache before gradlew command by
expo publish --clear --release-channel my-production-channel
- Update gradle version by opening the project with Android Studio
Does anyone know other things I can try?
I am stuck with this issue.
these lines do not exist in my app/build.gradle file and still getting the error
annotationProcessor «com.github.Raizlabs.DBFlow:dbflow-processor:4.2.4»
implementation «com.github.Raizlabs.DBFlow:dbflow-core:4.2.4»
implementation «com.github.Raizlabs.DBFlow:dbflow:4.2.4»
> Could not determine artifacts for com.github.Raizlabs.DBFlow:dbflow:4.2.4:
cannot build. any help you be greatly appreciated
Gradle seems to be able to sync for me when I change android/build.gradle
-> allprojects { repositories { /* ...others... */ maven { url 'https://jitpack.io' } ...
and add www in front, so it’s www.jitpack.io
AlexBungiu, 0x2539, and enriccamacho reacted with laugh emoji
AlexBungiu, 0x2539, and enriccamacho reacted with hooray emoji
0x2539, AlexBungiu, and enriccamacho reacted with heart emoji
0x2539, AlexBungiu, and enriccamacho reacted with rocket emoji
Gradle seems to be able to sync for me when I change
android/build.gradle
->allprojects { repositories { /* ...others... */ maven { url 'https://jitpack.io' } ...
and add www in front, so it’swww.jitpack.io
it’s helped me
It also works for me! Thank you!!
Copy link
Contributor
Author
@aslakrin Have you also added this back ?
annotationProcessor "com.github.Raizlabs.DBFlow:dbflow-processor:4.2.4"
implementation "com.github.Raizlabs.DBFlow:dbflow-core:4.2.4"
implementation "com.github.Raizlabs.DBFlow:dbflow:4.2.4"
lock
bot
locked and limited conversation to collaborators
Apr 15, 2020
Я только что создал новый конвейер Jenkins, который читает из скрипта Jenkinsfile в репозитории. Я создал ветку, а затем передал этот скрипт в репо. Теперь я пытаюсь создать эту ветку на jenkins, но получаю следующую ошибку, и я не уверен, что делаю неправильно, поскольку я в основном скопировал Jenkinsfile из существующего репо, который я могу успешно построить. Это моя первая сборка для этого проекта, но она не работает. пожалуйста посоветуй. когда написано «пропущено из-за более раннего сбоя», что это означает и как определить этот сбой?
Commit message: "Project Foundation"
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
[Pipeline] sh
+ git describe --tags
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
Stage "Build" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Test)
Stage "Test" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish Dev)
Stage "Publish Dev" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // withCredentials
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 128
Finished: FAILURE
1 ответ
Лучший ответ
Похоже, в вашем репозитории нет тегов для описания.
Дженкинс достигает запуска sh
сценария оболочки git describe --tags
(см. Знак плюса +
в начале строки, что означает, что он был запущен), но он терпит неудачу с показанным кодом выхода 128 в конце вывода консоли:
ОШИБКА: скрипт вернул код выхода 128
Судя по всему, git describe
выходит с этим кодом, если нечего описывать (теги в вашем случае).
Чтобы продолжить отсюда, вы можете удалить строку или добавить игнорировать ошибку, добавив || true
в команду:
sh "git describe --tags || true"
0
Travenin
23 Окт 2020 в 10:06
1 / 1 / 0
Регистрация: 10.12.2021
Сообщений: 215
1
Ошибки при сборке проекта
30.10.2022, 14:38. Показов 849. Ответов 6
Уже какой раз бьюсь с ошибкой, 2й день пошел. В гугле ищу решение не помогает, в чем причина может быть?
Код
CommandInvokationFailure: Gradle build failed. E:UnityHubEditor2020.3.30f1EditorDataPlaybackEnginesAndroidPlayerOpenJDKbinjava.exe -classpath "E:UnityHubEditor2020.3.30f1EditorDataPlaybackEnginesAndroidPlayerToolsgradlelibgradle-launcher-6.1.1.jar" org.gradle.launcher.GradleMain "-Dorg.gradle.jvmargs=-Xmx4096m" "assembleRelease" stderr[ E:UnityHubCyber MoneyTempgradleOutlaunchersrcmainAndroidManifest.xml Error: uses-sdk:minSdkVersion 19 cannot be smaller than version 21 declared in library [:com.unity3d.mediation.mediation-adapter-1.1.0:] C:UsersAlexey.gradlecachestransforms-2files-2.1f3a57b5ffa81942f492123da0e8ee5afcom.unity3d.mediation.mediation-adapter-1.1.0AndroidManifest.xml as the library might be using APIs not available in 19 Suggestion: use a compatible library with a minSdk of at most 19, or increase this project's minSdk version to at least 21, or use tools:overrideLibrary="com.unity3d.mediation.mediationadapter" to force usage (may lead to runtime failures) FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':launcher:processReleaseManifest'. > Manifest merger failed : uses-sdk:minSdkVersion 19 cannot be smaller than version 21 declared in library [:com.unity3d.mediation.mediation-adapter-1.1.0:] C:UsersAlexey.gradlecachestransforms-2files-2.1f3a57b5ffa81942f492123da0e8ee5afcom.unity3d.mediation.mediation-adapter-1.1.0AndroidManifest.xml as the library might be using APIs not available in 19 Suggestion: use a compatible library with a minSdk of at most 19, or increase this project's minSdk version to at least 21, or use tools:overrideLibrary="com.unity3d.mediation.mediationadapter" to force usage (may lead to runtime failures) * 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 BUILD FAILED in 10s Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 ] stdout[ > Configure project :launcher WARNING: The option setting 'android.enableR8=false' is deprecated. It will be removed in version 5.0 of the Android Gradle plugin. You will no longer be able to disable R8 > Task :launcher:preBuild UP-TO-DATE > Task :launcher:preReleaseBuild UP-TO-DATE > Task :unityLibrary:preBuild UP-TO-DATE > Task :unityLibrary:preReleaseBuild UP-TO-DATE > Task :unityLibrary:compileReleaseAidl NO-SOURCE > Task :launcher:compileReleaseAidl NO-SOURCE > Task :unityLibrary:packageReleaseRenderscript NO-SOURCE > Task :launcher:compileReleaseRenderscript NO-SOURCE > Task :launcher:generateReleaseBuildConfig UP-TO-DATE > Task :launcher:javaPreCompileRelease UP-TO-DATE > Task :launcher:generateReleaseResValues UP-TO-DATE > Task :launcher:generateReleaseResources UP-TO-DATE > Task :unityLibrary:compileReleaseRenderscript NO-SOURCE > Task :launcher:createReleaseCompatibleScreenManifests UP-TO-DATE > Task :unityLibrary:generateReleaseResValues UP-TO-DATE > Task :unityLibrary:generateReleaseResources UP-TO-DATE > Task :unityLibrary:packageReleaseResources UP-TO-DATE > Task :unityLibrary:extractDeepLinksRelease UP-TO-DATE > Task :launcher:extractDeepLinksRelease UP-TO-DATE > Task :unityLibrary:processReleaseManifest > Task :unityLibrary:compileReleaseLibraryResources UP-TO-DATE > Task :launcher:mergeReleaseResources UP-TO-DATE > Task :unityLibrary:parseReleaseLocalResources UP-TO-DATE > Task :unityLibrary:generateReleaseRFile UP-TO-DATE > Task :unityLibrary:generateReleaseBuildConfig UP-TO-DATE > Task :unityLibrary:javaPreCompileRelease UP-TO-DATE > Task :launcher:processReleaseManifest FAILED See http://g.co/androidstudio/manifest-merger for more information about the manifest merger. > Task :unityLibrary:compileReleaseJavaWithJavac UP-TO-DATE 17 actionable tasks: 2 executed, 15 up-to-date ] exit code: 1 UnityEditor.Android.Command.WaitForProgramToRun (UnityEditor.Utils.Program p, UnityEditor.Android.Command+WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) UnityEditor.Android.Command.Run (System.Diagnostics.ProcessStartInfo psi, UnityEditor.Android.Command+WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) UnityEditor.Android.Command.Run (System.String command, System.String args, System.String workingdir, UnityEditor.Android.Command+WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) UnityEditor.Android.AndroidJavaTools.RunJava (System.String args, System.String workingdir, System.Action`1[T] progress, System.String error) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) UnityEditor.Android.GradleWrapper.Run (UnityEditor.Android.AndroidJavaTools javaTools, System.String workingdir, System.String task, System.Action`1[T] progress) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) Rethrow as GradleInvokationException: Gradle build failed UnityEditor.Android.GradleWrapper.Run (UnityEditor.Android.AndroidJavaTools javaTools, System.String workingdir, System.String task, System.Action`1[T] progress) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) UnityEditor.Android.PostProcessor.Tasks.BuildGradleProject.Execute (UnityEditor.Android.PostProcessor.PostProcessorContext context) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) UnityEditor.Android.PostProcessor.PostProcessRunner.RunAllTasks (UnityEditor.Android.PostProcessor.PostProcessorContext context) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) Rethrow as BuildFailedException: Exception of type 'UnityEditor.Build.BuildFailedException' was thrown. UnityEditor.Android.PostProcessor.CancelPostProcess.AbortBuild (System.String title, System.String message, System.Exception ex) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) UnityEditor.Android.PostProcessor.PostProcessRunner.RunAllTasks (UnityEditor.Android.PostProcessor.PostProcessorContext context) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) UnityEditor.Android.PostProcessAndroidPlayer.PostProcess (UnityEditor.BuildTarget target, System.String stagingAreaData, System.String stagingArea, System.String playerPackage, System.String installPath, System.String companyName, System.String productName, UnityEditor.BuildOptions options, UnityEditor.RuntimeClassRegistry usedClassRegistry, UnityEditor.Build.Reporting.BuildReport report) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) UnityEditor.Android.AndroidBuildPostprocessor.PostProcess (UnityEditor.Modules.BuildPostProcessArgs args, UnityEditor.BuildProperties& outProperties) (at <762caba6f98a4d7e9d56f7b5bd6e35d6>:0) UnityEditor.PostprocessBuildPlayer.Postprocess (UnityEditor.BuildTargetGroup targetGroup, UnityEditor.BuildTarget target, System.String installPath, System.String companyName, System.String productName, System.Int32 width, System.Int32 height, UnityEditor.BuildOptions options, UnityEditor.RuntimeClassRegistry usedClassRegistry, UnityEditor.Build.Reporting.BuildReport report) (at <68089899e4c84456bfc1de3436accf4a>:0) UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)
Код
E:UnityHubCyber MoneyTempgradleOutlaunchersrcmainAndroidManifest.xml Error: uses-sdk:minSdkVersion 19 cannot be smaller than version 21 declared in library [:com.unity3d.mediation.mediation-adapter-1.1.0:] C:UsersAlexey.gradlecachestransforms-2files-2.1f3a57b5ffa81942f492123da0e8ee5afcom.unity3d.mediation.mediation-adapter-1.1.0AndroidManifest.xml as the library might be using APIs not available in 19 Suggestion: use a compatible library with a minSdk of at most 19, or increase this project's minSdk version to at least 21, or use tools:overrideLibrary="com.unity3d.mediation.mediationadapter" to force usage (may lead to runtime failures) FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':launcher:processReleaseManifest'. > Manifest merger failed : uses-sdk:minSdkVersion 19 cannot be smaller than version 21 declared in library [:com.unity3d.mediation.mediation-adapter-1.1.0:] C:UsersAlexey.gradlecachestransforms-2files-2.1f3a57b5ffa81942f492123da0e8ee5afcom.unity3d.mediation.mediation-adapter-1.1.0AndroidManifest.xml as the library might be using APIs not available in 19 Suggestion: use a compatible library with a minSdk of at most 19, or increase this project's minSdk version to at least 21, or use tools:overrideLibrary="com.unity3d.mediation.mediationadapter" to force usage (may lead to runtime failures) * 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 BUILD FAILED in 10s Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
Добавлено через 2 минуты
Это происходит при билде. Причем если взять мой 2й проект, то все билдится нормально. Хотя все тоже самое установлено. Может в плагинах каких-то дело?
Добавлено через 30 минут
Еще вот эта ошибка вылазиет
Код
FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring project ':launcher'. > Could not resolve all artifacts for configuration ':launcher:classpath'. > Could not resolve org.jetbrains.kotlin:kotlin-stdlib-common:1.3.31. Required by: project :launcher > com.android.tools.build:gradle:3.4.3 > org.jetbrains.kotlin:kotlin-stdlib-jdk8:1.3.31 > org.jetbrains.kotlin:kotlin-stdlib:1.3.31 > Could not resolve org.jetbrains.kotlin:kotlin-stdlib-common:1.3.31. > Could not get resource 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-stdlib-common/1.3.31/kotlin-stdlib-common-1.3.31.pom'. > Could not GET 'https://jcenter.bintray.com/org/jetbrains/kotlin/kotlin-stdlib-common/1.3.31/kotlin-stdlib-common-1.3.31.pom'. Received status code 502 from server: Bad Gateway > Could not resolve org.glassfish.jaxb:jaxb-runtime:2.2.11. Required by: project :launcher > com.android.tools.build:gradle:3.4.3 > com.android.tools.build:builder:3.4.3 > com.android.tools:sdklib:26.4.3 > com.android.tools:repository:26.4.3 > Skipped due to earlier error * 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 BUILD FAILED in 20s Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
__________________
Помощь в написании контрольных, курсовых и дипломных работ, диссертаций здесь
0
Здравствуйте.
Создаю на react native приложение для android.
Делаю сборку приложения командой
$ cd android && ./gradlew assembleRelease
В результате в консоли получаю ошибку:
* What went wrong: A problem occurred configuring project ':app'. > Could not resolve all dependencies for configuration ':app:_debugApkCopy'. > Could not resolve com.android.support:appcompat-v7:23.0.1. Required by: project :app project :app > com.facebook.react:react-native:0.55.4 > Skipped due to earlier error > Could not resolve javax.inject:javax.inject:1. Required by: project :app > com.facebook.react:react-native:0.55.4 > Skipped due to earlier error > Could not resolve com.facebook.fbui.textlayoutbuilder:textlayoutbuilder:1.0 .0. Required by: project :app > com.facebook.react:react-native:0.55.4 > Skipped due to earlier error > Could not resolve com.facebook.fresco:fresco:1.3.0. Required by: project :app > com.facebook.react:react-native:0.55.4 > Skipped due to earlier error > Could not resolve com.facebook.fresco:imagepipeline-okhttp3:1.3.0. Required by: project :app > com.facebook.react:react-native:0.55.4 > Skipped due to earlier error > Could not resolve com.facebook.soloader:soloader:0.1.0. Required by: project :app > com.facebook.react:react-native:0.55.4 > Skipped due to earlier error > Could not resolve com.google.code.findbugs:jsr305:3.0.0. Required by: project :app > com.facebook.react:react-native:0.55.4 > Skipped due to earlier error > Could not resolve com.squareup.okhttp3:okhttp:3.6.0. Required by: project :app > com.facebook.react:react-native:0.55.4 > Skipped due to earlier error > Could not resolve com.squareup.okhttp3:okhttp-urlconnection:3.6.0. Required by: project :app > com.facebook.react:react-native:0.55.4 > Skipped due to earlier error > Could not resolve com.squareup.okio:okio:1.13.0. Required by: project :app > com.facebook.react:react-native:0.55.4 > Skipped due to earlier error > Could not resolve org.webkit:android-jsc:r174650. Required by: project :app > com.facebook.react:react-native:0.55.4 > Skipped due to earlier error * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. * Get more help at https://help.gradle.org BUILD FAILED in 4m 24s
Помогите исправить