React cli fails to run app on device, but runs from Xcode - ios

When I run my react-native app from Xcode to my iPhone it runs successfully. When I run from react cli to my device, the app suddenly stops, without giving a specific error.

Related

Flutter iOS App not launching after removing USB

So i'm testing a flutter app that builds and installs successfully on an iOS simulator as well as a physical devices. However, when building and installing the app with xcode via the USB, it successfully installs and launches but when the USB is disconnected from my mac and i try to run the already installed device on the iPhone, it shows only the launch / splash screen and fades and closes.
Is there something i'm doing wrong that causes this to happen? As the app works fine when connected with the USB and it's being run.
If the build is in debug mode - it won't open.
if you want to open application after disconnecting, try profile / release mode
flutter run --profile
or
flutter run --release
In iOS, debug build doesn't work without USB. To use the app without USB trying making a release build using flutter run --release

App is not installed using react native command

I have react native cli application and when I tried to run it on simulator using npx react-native run-ios command it builds app successfully, bundler gets started and it shows 100% complete of bundler process but on simulator app is not being installed.
Note: simulator opens automatically but app not installed. When I use Xcode to run app it is working fine
Can you please help me with this.
Video
Thanks
Finally I get it working by clearing all cash using DevCleaner(From app store) also deleted all core simulators and added few again. I specified name of simulator as well with command as npx react-native run-ios --simulator="iPhone 11"

re-natal not showing the app in iOS simulator

I've created an app using re-natal init and but when I run react-native run run-ios, the build does finish and the simulator opens too, but the app icon never shows up. How can I fix that?

How to start Meteor app on specific iOS simulator

After my Xcode upgraded to version 7.3 I'm not able to start my Meteor apps on simulators other then iPhone-6s-Plus. When I enter command
meteor run ios
having no any simulator running it automatically starts iPhone-6s-Plus. But if I start some other simulator using Xcode then that's what I get trying to run app (using --verbose)
No target specified for emulator. Deploying to iPhone-6s-Plus, 9.3
simulator
** RUN SUCCEEDED **
An error was encountered processing the command
(domain=com.apple.CoreSimulator.SimError, code=159): Invalid device
state
How I can run my apps on any other simulator then iPhone-6s-Plus?
OK, seems it is normal behaviour with Meteor v1.3 described in documentation: http://guide.meteor.com/mobile.html#running-your-app
Currently, this will always run your app on a simulated iPhone 6s
Plus. Use ios-device to open Xcode and select another simulator
instead.
So command
meteor run ios-device
will open generated iOS project in Xcode where you will be able to select any other simulator or connected device.

Cordova deploy app on iOS device

I have a app that runs in the iOS-simulator. The app is compiled with cordova 3.4. After that, I can run the app via shell by calling "cordova run iOS" as well as open the project in xCode and press the play button. Both works.
I attempted to put the app on my iOS-device (iPhone-5s, iPad-Retina). But that does work neither with console nor with xCode.
When I try to run the app on the console by "start iOS" the console freezes before the app is installed on the device. I don't get any error logs. It tried that a few times, and sometimes the app is installed, but the console freezes.
Trying to run the app with xCode I get those errors and issues:
I have the current versions of iOS, xCode and MacOS as well as a developer ID, that is requested by the cordova-console when I try to start the app on a real device. The device was set to a working-group of my apple-developer account, too. That shouldn't cause the problems.
The build-location was set to unique and xcode-default. That doesn't change anything.

Resources