I’m getting a lot of error that I can’t find the answer in stackoverflow, github etc …
This is the first error I’m getting on Fastlane step, all the others might be fixed if I fixed this one :
`Compiling expo-dev-menu Pods/expo-dev-menu » DevMenuManager.swift
❌ (ios/Pods/Headers/Private/expo-dev-menu/EXDevMenu/DevMenuRCTBridge.h:3:9)
2 |
3 | #import <React/RCTBridge+Private.h>
| ^ 'React/RCTBridge+Private.h' file not found
4 |
5 | NS_ASSUME_NONNULL_BEGIN
6 | `
I don’t know what is is related to.
To provide some more information, my previous build was successful.
With my next build, I needed to upgrade expo update.
I did so, and I get these errors on Pod install step :
[!] Unable to find a specification for EXUpdatesInterface depended upon by EXUpdates
[!] Unable to find a specification for expo-dev-launcher depended upon by expo-dev-client
[!] Unable to find a specification for expo-dev-menu-interface depended upon by expo-dev-launcher
[!] Unable to find a specification for expo-dev-menu depended upon by expo-dev-client
After installing theses packages with expo instal … and launch the new build, I managed to pass the Pod install step, but now I get the error I mentionned at the beginning
Workflow : Managed
SDK : 46
Related
I'm not sure what exactly is happening but I am unable to run react-native link without errors occuring
CLI Output:
react-native link --verbose
debug Available platforms: iOS, Android
debug Targeted platforms: iOS, Android
debug Getting project config for iOS...
debug Getting project config for Android...
error No package found. Are you sure this is a React Native project?
error Unexpected close tag
Line: 22
Column: 24
Char: >
debug Error: Unexpected close tag
Line: 22
Column: 24
Char: >
at error (/Users/Dellybro/Desktop/App/AppReactNativeApp/node_modules/xmldoc/node_modules/sax/lib/sax.js:666:10)
at strictFail (/Users/Dellybro/Desktop/App/AppReactNativeApp/node_modules/xmldoc/node_modules/sax/lib/sax.js:692:7)
at closeTag (/Users/Dellybro/Desktop/App/AppReactNativeApp/node_modules/xmldoc/node_modules/sax/lib/sax.js:885:9)
at SAXParser.write (/Users/Dellybro/Desktop/App/AppReactNativeApp/node_modules/xmldoc/node_modules/sax/lib/sax.js:1447:13)
at new XmlDocument (/Users/Dellybro/Desktop/App/AppReactNativeApp/node_modules/xmldoc/lib/xmldoc.js:199:15)
at readManifest (/Users/Dellybro/Desktop/App/AppReactNativeApp/node_modules/#react-native-community/cli/build/tools/android/readManifest.js:44:10)
at Object.projectConfig (/Users/Dellybro/Desktop/App/AppReactNativeApp/node_modules/#react-native-community/cli/build/tools/android/index.js:66:46)
at Object.keys.forEach.platform (/Users/Dellybro/Desktop/App/AppReactNativeApp/node_modules/#react-native-community/cli/build/commands/link/getProjectConfig.js:25:62)
at Array.forEach (<anonymous>)
at getProjectConfig (/Users/Dellybro/Desktop/App/AppReactNativeApp/node_modules/#react-native-community/cli/build/commands/link/getProjectConfig.js:22:35)
This randomly started happening after attempting to npm install react-native-firebase.
What I've tried
clear-caches
remove node_modules and npm install
Checking out my code back to a previous commit
Adding my package name to the manifest locaed in /android/app/src/debug/AndroidManifest.xml
Removing the app from my computer and cloning it from github
Running react-native link on another project, which works, but i just can't run react-native link on this specific project.
So the answer to my question was that in my android manifest xml file, there was an incorrect closing brace for one of my intent filters.
So for anyone that this happens to ensure that all of your Android files have correct syntax.
I fixed this problem by closing some unclosed tag in android/app/src/main/androidManifest.xml. Try checking the file line by line.
After upgrade to react-native 0.56(using react-native-git-upgrade ,and update babel-preset-react-native to 5.0.2),
react-native run-ios works fine and app run OK.
But when run react-native run-android, error occur:
/Users/shouhuasun/dev/stage/upgrade-test/mobile-upgrade-test/node_modules/react-native-wechat/android/build/intermediates/res/merged/release/values-v24/values-v24.xml:3: AAPT: Error retrieving parent for item: No resource found that matches the given name 'android:TextAppearance.Material.Widget.Button.Borderless.Colored'.
Other names not found such as:'TextAppearance.Material.Widget.Button.Colored,android:keyboardNavigationCluster',etc.
Other libs like react-native-fetch-blob also got the error.
What's the error?
Thanks!
I got the solution(thanks for Reynald Liandra on facebook React-Native Community Q&A):
The react-native-wechat(same other third libs) android module needs to be compiled using sdk 26 after update to rn v0.56.
Open node_modules/react-native-wechat/android/build.gradle ,
change compileSdkVersion to 26, and buildToolsVersion to 26.0.3
Then run react-native run-android and got the correct result.
If there are several third libs , it is noisy to change several build.gradle files.
And if update any libs version (or yarn add new libs),the node_moudle is refreshed and all changes in build.gradle will lost.
you can force gradle use specified sdk version by this(without modify build.gradle in node_modules anymore):
gradle force build tools version on third party libraries
Make sure your npm version is above 8.0
Hope you could help me here:
I'm currently building an app which I created through CRNA and then ejected. I get the ios version right on but I'm currently struggling a lot with the android version.
When running react-native run-android all I can get is the following error:
Error type 3
Error: Activity class {com.myapp/com.myapp.MainActivity} does not exist.
I've checked app/build.gradle, app/src/main/AndroidManifest.xml, app/src/main/java/com/myapp/MainActivity.java and app/src/main/java/com/myapp/MainActivity.java for name errors on package. I've tried moving from com.myapp to com.mebius.myapp and com aswell.
Seems this comes from the only plugin I'm using. I'm keeping on the investigation
Any hints?
There are 3 possible reasons for the android app build fails to make
1. You need to define sdk path in android/local.properties
if local.properties doesn't place then make a file names with that
add
sdk.dir = home/user/AndroidApp/local/Sdk
You can match with their system path..
2. Your genymotion or avd must enable with the android studio
3. You must have to go with the following command
npm start
in new terminal .
Please go through with it.
Thanks
Actually I had a problem with my gradle config which look like:
include ':react-native-sensors'
project(':react-native-sensors').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-sensors/android')
rootProject.name = 'accelapp'
I needed to add: include ':app'
I don't know if it's due to the process of ejecting from CRNA or if it's due to react-native link react-native-sensors though.
EDIT After some investigation, I couldn't reproduce this issue. This leads me to say it was a faulty copy/paste...
I am trying to compile the master branch of the react-native repo to submit a PR. I am following the docs https://facebook.github.io/react-native/docs/android-building-from-source.html
But doing exactly what do docs says, I get the following error on android:
Requiring unknown module "react/lib/ReactPropTypesSecret
Also running on ios gives similar kind of error:
Unable to resolve module react/lib/ReactPropTypesSecret from /Users/aakash/Projects/TestingPR/node_modules/react-native/Libraries/Utilities/deprecatedPropType.js: Unable to find this module in its module map or any of the node_modules directories under /Users/node_modules/react/lib/ReactPropTypesSecret
This issue occurs when an ReactNative-App based on RN 0.28 or older is upgraded to RN 0.30 or newer without to update also the "react"-package to at least 15.3.0.
Have you tried this?
If this will not solve your issue, you should provide your package.json.
Its been almost 3 hours and I'm not able to build this. Please can anybody provide the steps. All the documents suggest to use hcatalog-src-0.5.0-incuvating.tar.gz but this is not available anywhere on internet (ad far as I've searched). Then I downloaded the branch 0.5.0 but as per the documentation
http://docs.hortonworks.com/HDPDocuments/HDP1/HDP-1.2.0/ds_HCatalog/install.pdf
of version 0.5.0 you have to build l=using command
ant_home/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=forrest_home tar
Now the problem is that the build.xml do not have a target named 'tar'. So I just browsed the build.xml and tried the same command using target as 'package'
ant_home/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=forrest_home package
but then its showing me error.
BUILD FAILED
C:\Users\admnilesh\Desktop\hcatalog-branch-0.5\build.xml:71: The following error
occurred while executing this line:
C:\Users\nilesh\Desktop\hcatalog-branch-0.5\build-support\ant\deploy.xml:67:
Unable to resolve artifact: Unable to get dependency information: Unable to read
the metadata file for artifact 'com.sun.jersey:jersey-core:jar': Cannot find pa
rent: net.java:jvnet-parent for project: com.sun.jersey:jersey-project:pom:1.9.1
for project com.sun.jersey:jersey-project:pom:1.9.1
com.sun.jersey:jersey-core:jar:1.9.1
from the specified remote repositories:
apache.snapshots (http://repository.apache.org/snapshots),
central (http://repo1.maven.org/maven2),
glassfish-repository (http://maven.glassfish.org/content/groups/glassfish),
datanucleus (http://www.datanucleus.org/downloads/maven2)
Path to dependency:
1) org.apache.hcatalog:webhcat:jar:0.5.0-SNAPSHOT
Please help me out.
We've been having the same trouble and discussing it over at the hcatalog-user mailing list for the last couple of days. You can have a look at https://issues.apache.org/jira/browse/HCATALOG-601 to see what's being done about this problem.
Quick summary though : Jersey 1.9 depended on a glassfish maven repo, which no longer exists. Bump your jersey dep version from 1.9 to 1.14 and you should be able to build.
Edit : One more thing - we're still going through the release process to release the 0.5.0 incubating candidate, the latest candidates are being put up currently on http://people.apache.org/~travis/ . We should see a public release in a couple of days. In the meanwhile, I suggest poking over at our hcatalog-user mailing list : http://incubator.apache.org/hcatalog/mailing_lists.html
I got the same error while giving target "tar". On specifying the target as "package", the build proceeds ahead but fails with following error:
satish#dev1$ /usr/bin/ant -Dhcatalog.version=0.5.0 -Dforrest.home=/home/satish/work/forrest/apache-forrest-0.9 package
[artifact:dependencies] Unable to resolve artifact: Missing:
[artifact:dependencies] ----------
[artifact:dependencies] 1) org.apache.hcatalog:hcatalog-core:jar:0.5.0
[artifact:dependencies]
[artifact:dependencies]
[artifact:dependencies] Path to dependency:
[artifact:dependencies] 1) org.apache.hcatalog:hcatalog-pig-adapter:jar:0.5.0- incubating
[artifact:dependencies] 2) org.apache.hcatalog:hcatalog-core:jar:0.5.0
[artifact:dependencies] ----------
This issue got resolved by specifying project.version as "0.5.0-incubating" instead of "0.5.0" in build command line. The reason for error is that build installs hcatalog-core artifact as hcatalog-core-0.5.0-incubating.jar. However because of wrong project.version, the dependent projects were instead searching for hcatalog-core-0.5.0.jar.
Build succeeded with:
satish#dev1$ /usr/bin/ant -Dhcatalog.version=0.5.0-incubating -Dforrest.home=/home/satish/work/forrest/apache-forrest-0.9 package