I'm trying to generate release version of my app using React-native :
./gradlew assembleRelease
It's progress until app::bundleReleaseJsAndAssets gets stuck at 93% and never progress. I dont have any error on terminal.
About OS I'm on Mac OS.
issue reported https://github.com/facebook/react-native/issues/10078
If you are using realm, please consider that comment:
:app:bundleReleaseJsAndAssets was trying to bundle the default.realm* in the root folder generated from the tests in jest... So it was hanging there.
It couldn't decompile them or whatever. So i just deleted them and it worked again
I used to have realm in my project but removed it. I still had files not tracked by git, hanging around. I simply removed everything related to realm and it worked again
If you are building the react native app in android studio and you are stuck at
app::bundleReleaseJsAndAssets never progress
It could be the issue with "CMD" in the android studio. Please Make sure you install the plugin.
I'm able to resolve the issue.
Related
I abandoned a project I was working on for a while I came back to open it on upgraded flutter and dart plugin in visual studio code windows 10.now I get so many problems. is there a way to automatically update code to solve these errors?
do these steps:
delete build folder
delete .idea folder
run flutter clean
run flutter pub get
run flutter pub upgrade
then try to run your project.
The simple answer is it depends.
Judging by the comments from a reasonably good answer by Hasan Abbasi, this wasn't enough.
Depending on how old your project is, there are 2 choices before or after doing what that answer said:
If it's any more than 2 or 3 years old, I'd probably rewrite it from scratch. In that time, Flutter and Dart have matured greatly, which involves many breaking changes. Also, null-safety has been introduced. Creating a new project after updating Flutter will also fix those Gradle issues because the configuration files will be reset.
If it's less than that, try to fix those Gradle issues either by hand or just deleting the '/android' or '/ios' etc. folders and letting Flutter/Dart automatically recreate them when you run the app next. You'll probably need to migrate to null-safety: read about null-safety so you understand it properly, then try using the dart migrate tool. You will likely need to spend some time changing dependencies for null-safe versions. Then you can try the flutter fix tool to automatically resolve SOME issues.
Hope you can get your app to work soon!
I am new to coding. I recently had a coder update a React Native appI got it to run on Android with an emulator but there are multiple issues when getting the app to run on IOS. I am assuming the main issue is that I need to clean the react native app for IOS, and I have trouble finding information how to do this...WHat I tried was going to the iOS in the terminal and typing "xcodebuild clean" but errors still pursue....I tried opening up xxx. xcodeproj and I got an error that said "yogakit/yogakit.modulemap' not found". Then I tried opening up xxx.xcworkspace and it got an error saying that I need to update to Swift 5 but the update fails. I ve tried to research this issue everywhere but could not find a solution. What is it that I am doing wrong here? How do you take an updated code from Native React and get it to successfully run in Xcode?
After cleaning the build and deploying the app for the first time (both on a physical device and a simulator), it works the way it's supposed to. But after I change something and redeploy, SkiaSharp (libSkiaSharp.framework) and Realm (realm-wrappers.framework) don't get added to the app bundle Frameworks folder.
Other frameworks get added as usual after redeploys, but these two don't.
I already tried to disable incremental builds and device-specific builds, and it didn't fix it. I don't have a clue why this is happening.
After updating to Xamarin.Forms 4.8 the issue was fixed.
So I have been struggling with a weird issue with my expo setup for about the last month or so. I created my project through Expo and when I use exp start in the terminal or try to load the project through Expo XDE, it hangs after dependency graph loaded. I thought it was an NPM issue (and worked on my coding environment for weeks trying to fix it) but then I created a new project using create-react-native-app and noticed there seems to be an issue with the connection with the simulator. When I instantiate a new project with create-react-native-app (not expo) I get this error exp://localhost:19000 — Error while loading: a server with specified hostname could not be found. (code - 1003) Here is a photo of what it looks like:
Then I tried to put the address of the project from the terminal into the simulator:
And it actually works! The app loads!
This is making me think there is a problem with the simulator's connection. Perhaps it is pointed to the wrong port? Using this method, I can run apps that were made from create-react-native-app but not my original projected I created through expo because that still gets hung and won’t launch the simulator. Projects created through Expo don't have an iOS file which is how you launch a create-react-native-app project (yarn run ios).
Any ideas about how I could go about fixing this?
Try uninstalling both Xcode & Expo.
Seems like the ports for the simulator are on different references of some kind.
Make sure that all of x-code, simulators, and expo local version are up to date before you launch the simulator after reinstalling Xcode & Expo.
I currently have a Cordova project with 2 platforms: Android and iOS
I'm trying to add "OSX" with this:
https://github.com/apache/cordova-osx
However the documentation is quite hard to follow and I can't seem to get it to work properly.
Does anyone have any idea on how to do this? or more precise step by step instructions?
The Cordova CLI does not support OSX project targets.
In your project working directory root, type in:
cordova platform list
... to see the available and installed platforms.
just wondering if anyway gots this running ? actually I tried to load cordova from master. Later I tried to applied the patch which did NOT worked. So I did what the patch did by hand.
Anyway after the full cycle still "platform list" does not changed ?
So I assume there are more steps to be done, before OSX is added as a new platform?