-
Notifications
You must be signed in to change notification settings - Fork 2
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
layout error #295
Comments
same issue |
Same issue any one found any solution ? |
+1 |
1 similar comment
+1 |
Same issue any one found any solution ? |
+1 |
2 similar comments
+1 |
+1 |
Same after upgrading to RN latest version. |
Same issue after upgrading to RN 0.75.4 |
+1 |
1 similar comment
+1 |
+1. EDIT to add: upgrading to RN 0.76. |
Updating android studio to android-studio-2024.2.1.11 can solve this problem |
+1, I updated android-studio, but it didn't solve the problem. I updated the node, and I've been stuck with this for days. |
+1 Same RN 0.76.5 |
+1 |
e: file:///C:/Users/Jitesh/OneDrive/Desktop/gurujiastroapp/node_modules/@react-native/gradle-plugin/settings-plugin/src/main/kotlin/com/facebook/react/ReactSettingsExtension.kt:26:16 Unresolved reference: layout
Here is my build.gradle file
buildscript {
ext {
buildToolsVersion = "34.0.0"
minSdkVersion = 21
compileSdkVersion = 34
targetSdkVersion = 34
// Remove any sourceCompatibility and targetCompatibility here if present
// Instead, use:
androidXCore = "1.10.1"
kotlinVersion = "1.8.0"
reactNativeGradlePluginVersion = "5.0.4"
}
repositories {
google()
mavenCentral()
}
dependencies {
classpath("com.android.tools.build:gradle")
classpath("com.facebook.react:react-native-gradle-plugin")
classpath("org.jetbrains.kotlin:kotlin-gradle-plugin")
classpath("com.facebook.react:react-native-gradle-plugin:$reactNativeGradlePluginVersion")
}
apply plugin: "com.facebook.react.rootproject"
// Top-level build file where you can add configuration options common to all sub-projects/modules.
plugins {
// ...
// id 'com.google.gms.google-services' version '4.4.1' apply false
}
The text was updated successfully, but these errors were encountered: