Develop Reference

Nativescript Android build error: Could not find com.android.tools.build:gradle:7.3

I created a new NativeScript JavaScript project, using an existing project as a template. The new project builds OK on iOS, but fails on Android with the error:
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'nativescript_google_maps'.
> Could not resolve all files for configuration ':classpath'.
> Could not find com.android.tools.build:gradle:7.3..
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/7.3./gradle-7.3..pom
- https://jcenter.bintray.com/com/android/tools/build/gradle/7.3./gradle-7.3..pom
Required by:
project :
This error does NOT occur on the existing project. I hard-coded the versions of the various plugins that aren't at the latest level, to ensure that all the plugins are the same between the two projects. Here's the package.json file:
{
"name": "rrr",
"main": "app/app.js",
"version": "1.0.0",
"private": true,
"dependencies": {
"#bradmartin/nativescript-urlhandler": "^2.0.1",
"#kefah/nativescript-google-maps": "1.0.7",
"#master.technology/permissions": "^2.0.1",
"#nativescript-community/ui-material-bottom-navigation": "7.0.2",
"#nativescript/appversion": "^2.0.0",
"#nativescript/contacts": "2.0.4",
"#nativescript/core": "8.3.5",
"#nativescript/email": "^2.0.5",
"#nativescript/firebase": "^11.1.3",
"#nativescript/geolocation": "8.0.2",
"#nativescript/iqkeyboardmanager": "2.0.0",
"#nativescript/theme": "^3.0.2",
"#triniwiz/nativescript-toasty": "^4.1.3",
"base-64": "^1.0.0",
"nativescript-bitmap-factory": "^1.8.1",
"nativescript-clipboard": "^2.1.1",
"nativescript-danem-google-maps-utils": "^1.0.18",
"nativescript-drop-down": "6.0.1",
"nativescript-pdf-view": "^3.0.0-1",
"nativescript-phone": "^3.0.3",
"nativescript-screenshot": "^0.0.2",
"nativescript-sqlite": "^2.8.6",
"nativescript-ui-listview": "10.0.2",
"nativescript-ui-sidedrawer": "10.0.2",
"patch-package": "^6.5.1"
},
"devDependencies": {
"#nativescript/android": "8.1.1",
"#nativescript/ios": "8.2.3",
"#nativescript/webpack": "5.0.6"
},
"scripts": {
"postinstall": "patch-package"
}
}
When I run tns build android --log trace on the new project I see this info:
Got gradle versions null from runtime v8.1.1
Exec npm view #nativescript/android dist-tags --json
stdout: {
"rc": "8.2.0-rc.0",
"latest": "8.4.0",
"alpha": "8.4.0-alpha.8",
"dev": "8.4.0-dev.2",
"beta": "8.5.0-beta.0"
}
stderr:
Exec npm view #nativescript/android#8.4.0 gradle --json
stdout: {
"version": "7.5",
"android": "7.3."
}
stderr:
Got gradle versions {"gradleVersion":"7.5","gradleAndroidPluginVersion":"7.3."} from the latest runtime v8.4.0
These entries do not appear in the build log for the existing project; it looks like a higher version of cradle is being used on the new project.
I've seen others report similar error messages, but I've not seen working resolutions. For example, I did add the line to buildscript.gradle, but it has no effect:
dependencies {
classpath "com.google.gms:google-services:4.3.4"
classpath "com.android.tools.build:gradle:7.3" // <- added this line
}
I've done repeated tns clean's, updated the Android Studio build tools, etc., but still no luck. I welcome any insight.
Edit 1/22/2022:
Here's the tns doctor output:
✔ Getting environment information
No issues were detected.
✔ Your ANDROID_HOME environment variable is set and points to correct directory.
✔ Your adb from the Android SDK is correctly installed.
✔ The Android SDK is installed.
✔ A compatible Android SDK for compilation is found.
✔ Javac is installed and is configured properly.
✔ The Java Development Kit (JDK) is installed and is configured properly.
✔ Xcode is installed and is configured properly.
✔ xcodeproj is installed and is configured properly.
✔ CocoaPods are installed.
✔ CocoaPods update is not required.
✔ CocoaPods are configured properly.
✔ Your current CocoaPods version is newer than 1.0.0.
✔ Python installed and configured correctly.
✔ The Python 'six' package is found.
✔ Xcode version 13.3.1 satisfies minimum required version 10.
✔ Getting NativeScript components versions information...
⚠ Update available for component nativescript. Your current version is 8.1.5 and the latest available version is 8.4.0.
⚠ Update available for component #nativescript/core. Your current version is 8.3.5 and the latest available version is 8.4.6.
⚠ Update available for component #nativescript/ios. Your current version is 8.2.3 and the latest available version is 8.4.1.
⚠ Update available for component #nativescript/android. Your current version is 8.1.1 and the latest available version is 8.4.0.
Is there a way to control which version of gradle is used?

Upon advice from the NativeSript Android Discord channel, I updated the NativeScript CLI, core, and platforms to the latest versions and can build successfully. This doesn't answer why the existing project would build and the new one wouldn't, but does bypass the problem.

Unreal Engine - ERROR: Missing precompiled manifest for 'SteamShared'

I'm trying to build my project to launch it into my Oculus (Meta) Quest 2, the exact build that I'm choosing is Android (ASTC). But when I try to build, I get the following error
UATHelper: Packaging (Android (ASTC)): ERROR: Missing precompiled manifest for 'SteamShared'. This module was most likely not flagged for being included in a precompiled build - set 'PrecompileForTargets = PrecompileTargetsType.Any;' in SteamShared.build.cs to override.
PackagingResults: Error: Missing precompiled manifest for 'SteamShared'. This module was most likely not flagged for being included in a precompiled build - set 'PrecompileForTargets = PrecompileTargetsType.Any;' in SteamShared.build.cs to override.
I added that line PrecompileForTargets = PrecompileTargetsType.Any; to the SteamShared.build.cs file but it didn't change anything, the error persists.
Here's my Project.Build.cs
PCHUsage = PCHUsageMode.UseExplicitOrSharedPCHs;
PublicDependencyModuleNames.AddRange(new string[] { "Core", "CoreUObject", "Engine", "InputCore", "HeadMountedDisplay", "UMG", "LibOVRPlatform"}); //, "OnlineSubsystem"
PrivateDependencyModuleNames.AddRange(new string[] { "FirebaseFeatures", "OnlineSubsystem", "OnlineSubsystemOculus", "OnlineSubsystemSteam" });
So I'm also using the plugin AdvancedSessions & AdvancedSteamSessions. These plugins are in the Engine's plugins but also in the Project's plugins.
But the SteamSharedModule Plugin that's giving me the error is only in the engine (at C:\Epic\UE_4.27\Engine\Plugins\Runtime\Steam), and the OnlineSubsystemSteam Plugin is also only in the engine (at C:\Epic\UE_4.27\Engine\Plugins\Online).
When I try to disable the SteamSharedModule Plugin, it says "This plugin is required by OnlineSubsystemSteam", and when I try to disable the plugin OnlineSubsystemSteam, it says "This plugin is required by AdvancedSteamSessions".
NOTE: The multiplayer functionality I have made it in blueprints, but the project isn't completely in Blueprints, I do have some C++ classes.

Run errors - Plugins depricated versions and pod

The plugins flutter_webview_plugin, geocoder, location, sms use a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if these plugins support the Android V2 embedding. Otherwise, consider removing them since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.
Launching lib/main.dart on iPhone 13 in debug mode...
Running pod install...
CocoaPods' output:
↳
Preparing
Analyzing dependencies
Inspecting targets to integrate
Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)
Fetching external sources
-> Fetching podspec for `Flutter` from `Flutter`
-> Fetching podspec for `cloud_firestore` from `.symlinks/plugins/cloud_firestore/ios`
cloud_firestore: Using Firebase SDK version '8.11.0' defined in 'firebase_core'
-> Fetching podspec for `firebase_auth` from `.symlinks/plugins/firebase_auth/ios`
firebase_auth: Using Firebase SDK version '8.11.0' defined in 'firebase_core'
-> Fetching podspec for `firebase_core` from `.symlinks/plugins/firebase_core/ios`
firebase_core: Using Firebase SDK version '8.11.0' defined in 'firebase_core'
-> Fetching podspec for `flutter_webview_plugin` from `.symlinks/plugins/flutter_webview_plugin/ios`
-> Fetching podspec for `geocoder` from `.symlinks/plugins/geocoder/ios`
-> Fetching podspec for `google_sign_in` from `.symlinks/plugins/google_sign_in/ios`
-> Fetching podspec for `location` from `.symlinks/plugins/location/ios`
-> Fetching podspec for `sms` from `.symlinks/plugins/sms/ios`
-> Fetching podspec for `url_launcher_ios` from `.symlinks/plugins/url_launcher_ios/ios`
Resolving dependencies of `Podfile`
CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only performed in repo update
[!] CocoaPods could not find compatible versions for pod "cloud_firestore":
In Podfile:
cloud_firestore (from `.symlinks/plugins/cloud_firestore/ios`)
Specs satisfying the `cloud_firestore (from `.symlinks/plugins/cloud_firestore/ios`)` dependency were found, but they required a higher minimum deployment target.
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:317:in `raise_error_unless_state'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:299:in `block in unwind_for_conflict'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:297:in `tap'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:297:in `unwind_for_conflict'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:682:in `attempt_to_activate'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:254:in `process_topmost_state'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:182:in `resolve'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolver.rb:43:in `resolve'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/resolver.rb:94:in `resolve'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer/analyzer.rb:1078:in `block in resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer/analyzer.rb:1076:in `resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer/analyzer.rb:124:in `analyze'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:416:in `analyze'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:241:in `block in resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:240:in `resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/installer.rb:161:in `install!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/command/install.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/claide-1.1.0/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.11.2/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:23:in `load'
/usr/local/bin/pod:23:in `<main>'
Error output from CocoaPods:
↳
[!] `<PBXGroup UUID=`97C146E51CF9000F007C117D`>` attempted to initialize an object with an unknown UUID. `CF3B75C9A7D2FA2A4C99F110` for attribute: `children`. This can be the result of a merge and the unknown UUID is being discarded.
[!] Automatically assigning platform `iOS` with version `9.0` on target `Runner` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.
Error running pod install
Error launching application on iPhone 13.

You must add this script to your "Podfile" in ios folder:
target.build_configurations.each do |config|
config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '13.0'
end
such as the below pic:
after that, you must run pod install or run again to be pod again installed.

How to resolve #bazel_tools//tools/android:databinding_exec when switching from bazel 3.6.0 to 3.7.0

I’ve been using bazel to build an android project, initially starting with a 0.24 version, then using the 2.0 version for a longer time, and now I am trying to switch to the latest 3.7.0 / 3.7.1 versions.
Currently I am using the following important .bazelrc settings for android:
build:androidbuild --crosstool_top=#androidndk//:default_crosstool
build:androidbuild --host_crosstool_top=#bazel_tools//tools/cpp:toolchain
build:android-32 --config=androidbuild --cpu=x86 --fat_apk_cpu=x86
All cc_binary / cc_library targets can still be built the same way we used to, but the android_binary targets no longer builds and I am getting this error:
ERROR: While resolving toolchains for target
#bazel_tools//tools/android:databinding_exec: No matching toolchains
found for types #bazel_tools//tools/cpp:toolchain_type. Maybe
--incompatible_use_cc_configure_from_rules_cc has been flipped and there is no default C++ toolchain added in the WORKSPACE file? See
https://github.com/bazelbuild/bazel/issues/10134 for details and
migration instructions.
I tried to find which was the bazel version that started to throw this error, and I found that I can still build my project with 3.6.0, but I start getting the above error if I switch to 3.7.0 or 3.7.1.
Looking at the 3.6.0 vs 3.7.0 changes, I am wondering if the new create_dummy_sdk_toolchain call in tools/android/android_sdk_repository_template.bzl would cause this failure or there is something else I am missing (like changes in the cc_flags_supplier.bzl / compiler_flag.bzl sources to set incompatible_use_toolchain_transition to True).
I tried the approach of using --platforms instead, but I am still getting errors even in that case:
build:androidbuild --extra_toolchains=#androidndk//:all
build:android-32 --config=androidbuild --cpu=x86 --platforms=//config:android_x86
With:
platform(
name = "android_x86",
constraint_values = [
"#bazel_tools//platforms:x86_32",
"#bazel_tools//platforms:android",
],
cpu_constraints = [
],
os_constraints = [
],
target_platform = True,
)
Error:
ERROR: While resolving toolchains for target
#bazel_tools//tools/android:instrumentation_test_check: No matching
toolchains found for types #bazel_tools//tools/cpp:toolchain_type.
Maybe --incompatible_use_cc_configure_from_rules_cc has been flipped
and there is no default C++ toolchain added in the WORKSPACE file? See
https://github.com/bazelbuild/bazel/issues/10134 for details and
migration instructions.
Can you please advise me on what is missing from the project that is required to solve the problem caused by the 3.6.0 vs 3.7.0 diffs, do we now need to define a proper toolchain for Android (can't we rely anymore on bazel to figure out how to build android targets)?
UPDATE Dec/16/2020
Looks like the problem was caused by this code:
WORKSPACE:
register_execution_platforms(
"//tools/config:host_platform",
)
In the BUILD file:
platform(
name = "host_platform",
constraint_values = [
],
cpu_constraints = [
"#bazel_tools//platforms:x86_32",
"#bazel_tools//platforms:x86_64",
],
host_platform = True,
os_constraints = [
"#bazel_tools//platforms:windows",
],
)
For some reason this works in bazel 3.6.0 even when the host is Linux, but it's no longer working in 3.7.0.

The problem was caused by this code:
WORKSPACE:
register_execution_platforms(
"//tools/config:host_platform",
)
In the BUILD file:
platform(
name = "host_platform",
constraint_values = [
],
cpu_constraints = [
"#bazel_tools//platforms:x86_32",
"#bazel_tools//platforms:x86_64",
],
host_platform = True,
os_constraints = [
"#bazel_tools//platforms:windows",
],
)
For some reason this works in bazel 3.6.0 even when the host is Linux, but it's no longer working in 3.7.0.

when I do bazel build --platforms=//:linux_arm64 it gave me the same error:
hile resolving toolchains for target #io_bazel_rules_go//:cgo_context_data: No matching toolchains found for types #bazel_tools//tools/cpp:toolchain_type. Maybe --incompatible_use_cc_configure_from_rules_cc has been flipped and there is no default C++ toolchain added in the WORKSPACE file? See https://github.com/bazelbuild/bazel/issues/10134 for details and migration instructions.
The follow command works
bazel build --platforms=#io_bazel_rules_go//go/toolchain:linux_arm64

Error: Could not find an installed version of Gradle either in Android Studio, or on your system to install the gradle wrapper

I develop a hybrid app usin cordova. While I was trying to build the android verion of my App, i got this error:
Error: Could not find an installed version of Gradle either in Android Studio,
or on your system to install the gradle wrapper. Please include gradle
in your path, or install Android Studio.
..although Android Studio is already installed and everything worked so far.
Does anybody know the reason for this issue?

The problem is in the file: \cordova\lib\check_reqs.js
When cordova checks the location of graddle is doing this: var androidPath = path.join(process.env['ProgramFiles'], 'Android') + '/';
If you don't have installed in certain location, cordova can't find the file.
So... edit tcheck_reqs.js and do this (i'm using Windows 10 and cordova 7.0.1):
return 'C:\\Android\\sdk\\gradle\\gradle-3.2\\bin\\gradle';
if (androidStudioPath !== null && fs.existsSync(androidStudioPath)) {
var dirs = fs.readdirSync(androidStudioPath);
if(dirs[0].split('-')[0] == 'gradle') {
return path.join(androidStudioPath, dirs[0], 'bin', 'gradle');
}
} else {
//OK, let's try to check for Gradle!
return forgivingWhichSync('gradle');
}
It's not a real fix, but if you are sure of your gradle location it will be fine, hope cordova fix this.

http://www.bubuko.com/infodetail-2108699.html，
its about your cordova version;