build-error

Adding a Configuration as a dependency is a confusing behavior which isn't recommended

天大地大妈咪最大 提交于 2021-02-07 09:19:23
问题 I have encountered the following warning after trying to build my Kotlin project with Gradle 7. > Configure project :app Adding a Configuration as a dependency is a confusing behavior which isn't recommended. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. If you're interested in inheriting the dependencies from the Configuration you are adding, you should use Configuration#extendsFrom instead. See https://docs.gradle.org/6.7/dsl/org.gradle.api.artifacts

Adding a Configuration as a dependency is a confusing behavior which isn't recommended

倾然丶 夕夏残阳落幕 提交于 2021-02-07 09:17:58
问题 I have encountered the following warning after trying to build my Kotlin project with Gradle 7. > Configure project :app Adding a Configuration as a dependency is a confusing behavior which isn't recommended. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. If you're interested in inheriting the dependencies from the Configuration you are adding, you should use Configuration#extendsFrom instead. See https://docs.gradle.org/6.7/dsl/org.gradle.api.artifacts

Build error due to conflict between Androidx and Android Support recent version

陌路散爱 提交于 2021-01-29 11:34:56
问题 I am stuck with a build error due to some conflict as defined in the title. Here is my error: Manifest merger failed : Attribute application@appComponentFactory value=(android.support.v4.app.CoreComponentFactory) from [com.android.support:support-compat:28.0.0] AndroidManifest.xml:22:18-91 is also present at [androidx.core:core:1.0.0] AndroidManifest.xml:22:18-86 value=(androidx.core.app.CoreComponentFactory). Here are my build.grade files: apply plugin: 'com.android.application' apply plugin

Android resource linking failed AAPT: unknown option '--proguard-minimal-keep-rules'

馋奶兔 提交于 2020-06-29 04:08:12
问题 My Android Studio was working fine, everything was good but after updating Android Studio to the latest version and updating gradle I got the following error Could you please provide the solution, thank you Task :app:processDebugResources FAILED AGPBI: {"kind":"error","text":"Android resource linking failed","sources":[{}],"original":"AAPT: unknown option '--proguard-minimal-keep-rules'.\n\naapt2 link [options] -o arg --manifest arg files...\n\nOptions:\n -o arg Output path.\n --manifest arg

Unity Build failed [closed]

蹲街弑〆低调 提交于 2020-05-17 05:54:05
问题 Closed . This question needs details or clarity. It is not currently accepting answers. Want to improve this question? Add details and clarify the problem by editing this post. Closed 9 days ago . When I tried to build my 3D game for Windows I had this error: at UnityEditor.BuildPlayerWindow+DefaultBuildMethods.BuildPlayer (UnityEditor.BuildPlayerOptions options) [0x002bb] in <17b72532ee2c4da1b6f632d3f1705fe0>:0 at UnityEditor.BuildPlayerWindow.CallBuildMethods (System.Boolean

Invalid value 'armeabi' in $(AndroidSupportedAbis). This ABI is no longer supported. Xamarin.Forms - VS2019

删除回忆录丶 提交于 2020-03-18 04:21:11
问题 I have a Mobile App built with Xamarin.Forms when I am trying to upgrade my project from VS2017 to VS2019 I get this error in Android Project Invalid value 'armeabi' in $(AndroidSupportedAbis). This ABI is no longer supported. Please update your project properties I tried to delete bin and obj folders to force the project to rebuild everything, but the error still appears Can I get an explanation about the error above and how to solve it? Note: the error doesn't appear in VS2017 回答1: armeabi

Invalid value 'armeabi' in $(AndroidSupportedAbis). This ABI is no longer supported. Xamarin.Forms - VS2019

放肆的年华 提交于 2020-03-18 04:20:27
问题 I have a Mobile App built with Xamarin.Forms when I am trying to upgrade my project from VS2017 to VS2019 I get this error in Android Project Invalid value 'armeabi' in $(AndroidSupportedAbis). This ABI is no longer supported. Please update your project properties I tried to delete bin and obj folders to force the project to rebuild everything, but the error still appears Can I get an explanation about the error above and how to solve it? Note: the error doesn't appear in VS2017 回答1: armeabi

How to hide android system' s bottom navigation bar in React Native App without changing MainActivity? Maybe through AndroidManifest?

百般思念 提交于 2020-01-23 16:59:05
问题 I want to hide the system's bottom navigation bar. I used "react-native-navigation-bar-color" but it causes a build error, strangely while release build only. I thought I could remove this package(react-native-navigation-bar-color) and permanently hide the navbar by changing MainActivity but the MainActivity in React Native does not inherit AppCompatActivity in order for it to have "onCreate" method in which I can write the code(as per android studio documentation) to hide. Following is the

Error when building Mongodb on ubuntu server

Deadly 提交于 2020-01-15 04:54:27
问题 I am trying to build mongodb (r2.4.8) with the --ssl option on a ubuntu server (13.10) I get these errors: scons --ssl --64 all src/third_party/boost/boost/date_time/posix_time/posix_time_io.hpp: In function 'std::basic_ostream<_CharT, _Traits>& boost::posix_time::operator<<(std::basic_ostream<_CharT, _Traits>&, const boost::posix_time::time_duration&)': src/third_party/boost/boost/date_time/posix_time/posix_time_io.hpp:183:51: error: typedef 'std_ptime_facet' locally defined but not used [

Error when building Mongodb on ubuntu server

只谈情不闲聊 提交于 2020-01-15 04:54:27
问题 I am trying to build mongodb (r2.4.8) with the --ssl option on a ubuntu server (13.10) I get these errors: scons --ssl --64 all src/third_party/boost/boost/date_time/posix_time/posix_time_io.hpp: In function 'std::basic_ostream<_CharT, _Traits>& boost::posix_time::operator<<(std::basic_ostream<_CharT, _Traits>&, const boost::posix_time::time_duration&)': src/third_party/boost/boost/date_time/posix_time/posix_time_io.hpp:183:51: error: typedef 'std_ptime_facet' locally defined but not used [