I have added latest version of react-native-firebase crashlytics 8.1.1 and I'm getting an error in Android during the build:
Duplicate resources in com_crashlytics_export_strings.xml
Any ideas how is possible to fix this issue? This file was automatically generated by Crashlytics.
P.S: if delete com_crashlytics_export_strings.xml it would be possible to make app build. However, I'm not sure how important that file is. Will Crashlytics work correctly if there wouldn't be this file in the project?
I deleted com_crashlytics_export_strings.xml and after that everything worked as expected!
Related
I am trying to build a project that we have previously built many times on a real device through xcode but not it throws a No Bundle URL present error the moment the app boots.
I have tried updating the app, rebooting and updating the info.plist file but nothing seems to change it.
Other apps are booting fine.
I have my info and the error below.
Error Screen
Check whether you are running correct Project. Clean you build folder and then Run .
Seems like this is a common issue for some. I'd suggest checking out this thread with others that had a similar issue - What is the meaning of 'No bundle URL present' in react-native?
I've got codepush working for a staging build of an app I hope to soon have in production.
On initial download from the app store, the fonts are looking great! My version checking info that I have in the app shows me that I'm using the bundled version of the bundle.js
If I force-quit and re-launch the app (causing an update) the fonts are no longer found in the application. They display the "missing glyph" image (see screenshot below).
I'm hoping for either a solution, some tricks to try, or just some ideas about how to further debug and understand what is causing this. I'm a little stuck because when I try to run the app in debug mode, it just uses the latest codepush version instead of downloading a new one.
I'm building a React Native application that I'm trying to deploy to the App Store.
I used a couple of packages, the ones that I think gives me the errors are
https://www.npmjs.com/package/react-native-modal-datetime-picker/v/7.6.1
https://www.npmjs.com/package/react-native-app-link
https://www.npmjs.com/package/react-native-map-link
I found this solution and I also deleted other files found in the same location with this name RCTWKWebView etc..
Now I get build error with missing files.
I also deleted those same files under pod config files../React/Core
What should I do ? Am I missing something?
It's the first time dealing with this error and I can't seem to find a useful solution.
Thank you in advance
I think your react-native versions cause the problem. You try to remove files include UIWebView in name on the XCode under the React folder. After that, you try to upload it to AppStore.
native, I started using EXPO to build with a
create-react-native-app
It was fine until I decided to actually create a IPA file to upload to apple to have more testing done by other users, so I did an init and created the needed files for ios and android deployment.
I am getting errors from Xcode building my IPA file over telling me that there is no scripts folder inside react-native, like
node_modules/react-native/scripts/ios-install-third-party.sh: cannot
execute: No such file or directory
and sure enough opening the folder for node_modules/react-native there is no scripts folder there. I'm not sure what the problem is, the react version I am using is 0.46.1.
Any help is greatly appreciated.
I have the same issue. I find the solution with using old version 0.44.0 -> react-native init --version="0.44.0" app.
Please check your current directory path and please remove your 'whitespace' in any folder name.This is very important.
I solved the issue using the following links:
Got the solution 1
Got the solution 2
Delete third-party folder from node_modules/react-native/
I am facing a strange compiler error in upload-sym file which is used for firebase crash reporting platform. I am using the latest update from FirebaseCrash 2.0.0.
Please check out this photo in xCode 8.3.2:
I tried cleaning the build path, clean, build,research online for some kind of solution but it seems to be I'm the first one who has faced it.