Migrating my native script application to 8.1.5 version.
Fixed the errors that occurs when migrating the native script application.
Application build successfully in the emulator. After build successfully getting error in the application.
How to fix this issue?
Try this:
Go to AVD Manager, and click wipe data on the selected emulator:
Restart your machine (adb connection might be lost).
Then restart your project by running:
ns clear
ns run android
If that doesn't open the app on the emulator, run:
ns devices
Spot the emulator ID you want to run the app on
ns build android
ns deploy --device EMULATOR-ID
Note:
Make sure you've done all 4 blue steps in the cli message (in blue).
Related
I am flowing the official tutorial to install flutter and run the default app on my iPhone Device. After I execute the flutter run, the app is installed and launched on my iPhone but the logs show the bellow error. How do I solve it?
Launching lib/main.dart on My iPhone 6 in debug mode...
Automatically signing iOS for device deployment using specified development team
in Xcode project: XXXXXXXXXX
Running Xcode build...
└─Compiling, linking, and signing... 50.2s
Xcode builds done. 90.1s
Installing and launching... 41.1s
Error launching the application on My iPhone 6. <-- Error Here
It happens that there are some process needed to Flutter plugin correctly run on physical devices. I struggled with that and finally found that the processes idevicesyslog and iproxy were being silently blocked by MacOS.
You may have noticed already a message liked this:
or a similar one for idevicesyslog.
Once I went to System Preferences -> Security & Privacy in General tab and allowed this apps, everything works. Note that this screen shows only the last app that you tried to run. So I'd recommend that you run flutter app with preferences opened so you can (hopefully) see the messages appearing and click allow.
MacOS may warn you one more time about the file being downloaded from the internet. Just click open and you're good.
The error do not show again after reboot the iPhone.
Same error -- Running fine through Xcode, when I ran with flutter CLI, the app would open, but the terminal log output would crash with the error as in the post.
I ran flutter update and simultaneously turned iPhone off and back on. After doing that, the below popup appeared (on mac).
I believe after the install finished, I ran the below (which I ran several times before updating flutter and installing the popup):
flutter clean
rm -rf ios/Pods
flutter pub get
cd ios && pod install && cd ..
run the flutter app using flutter run from command line, then the MacBook will ask for permission to open the app and app runs,
(lldb) warning: libobjc.A.dylib is being read from process memory. This indicates that LLDB could not find the on-disk shared cache for this device. This will likely reduce debugging performance.
Error launching application on device-XXXXX.
Building & Replace with a newest version ios-deploy solved problems list aboved. Flutter SDK bundled a pre-built command ios-deploy in __PATH_TO_YOUR_Flutter_SDK_/bin/cache/artifacts/ios-deploy/, just replace it.
Please reference to: Flutter Error launching application on device issue .
i just created a react native project on windows, using expo. After Creating the project i ran npm start and then expo start the next logical thing to do is to press the a button which will launch, the project on the android virtual device, but instead it gave me this error Couldn't start project on Android: Error running adb: Error running app. Error: Activity not started, unable to resolve Intent { act=android.intent.action.VIEW dat=exp://192.168.43.148:19000 flg=0x10000000 }
when i tried running it on my android phone with the expo android app it ran smoothly, i don't know what to do please help thanks
I had the same problem and I got it fixed as follows:
Go to SDK Manager in Android studio > SDK Tools and check whether there is any update for Android SDK Build-Tools. If there is any, please make sure you update it.
Close any Android virtual device currently running and then go to Android Studio Virtual Device Manager and wipe the data of your Android virtual device.
Make sure you have enough internal storage allocated for your Android virtual device to install apps.
Check whether Android Debug Bridge utility is installed in your device. If not please install it. To install in mac, I used the below command (Assuming that you have HomeBrew installed in your mac device):
brew install android-platform-tools
Start your Android virtual device ( This step should be done before running the expo development server)
In the Developer options menu of your Android virtual device, make sure USB debugging option is enabled.
Finally, try running the development server by expo start and press on the button to run on your Android emulator.
I'm getting the following error while running my first flutter app in the terminal
Launching lib/main.dart on vivo 1802 in debug mode...
Running Gradle task 'assembleDebug'...
(This is taking an unexpectedly long time.)
I already tried downloading the gradle distribution separately and copy pasting it in my project's gradle wrapper and restarting android studio but it still doesn't resolve the issue.
I'm using Linux Mint 19.
Make sure you have an internet connection.When running an app for the first time, gradle needs to download some additional content
Check your connection to your virtual phone or your phone well. Make sure it doesn't disconnect while you are running the app
Before starting this building process, make sure:
USB debugging is enabled on your phone,
No app is currently running (and you are on your home screen),
While running your app for the first time on a phone, your phone will get a pop-up asking you to allow the installation of apps via USB.
Click 'allow' on it.
Not clicking 'allow' or simply ignoring it will make it seem like the build process is never-ending.
I'm using Eclipse Juno (build 20120920-0800) on openSUSE 12.2 to code Android applications.
I have installed the SDK by uncompressing it into my home directory (if I install the SDK via YaST package I can't download stuff unless I'm root). I installed ADT from Eclipse Marketplace, configured the path of the SDK and configured a couple of emulator configurations.
I can run and debug fine on my phone, and I guess the same applies to my tablet even if I haven't tried yet.
The real problem is that I can't run the emulator. Clicking on the bacarozzo debug icon prompts me to run the application on the device but doesn't show me available emulators.
If I open the device manager I'm shown with the virtual devices I created but I can't just start any. The progress bar reaches the end, I see no emulator screen and if I try to delete the emulator I'm warned that the instance is running... (OK in the screenshot there is only one, I already managed to delete the other)
I urge to test some GUI features in an outdated version of Android. I have done all the field tests of the business logic code in my program on a JB device and I know for sure that code works on any device.
Now I only need to be backward-compatible with preferences and layouts.
How can I start the emulator in Linux?
Just by luck I managed to run the emulator from console
djechelon#RAYNOR:~/android-sdk-linux/tools> ./emulator-arm -avd Emulator_cell
It came to life and Eclipse debug is detecting it as active device
I'm going to say upfront, please forgive me. I'm a newbie to android development and fairly new to programming. Also on a Mac. You're going to have to talk...real...slow.
I can't get an AVD to load. I've tried it from Eclipse (Juno) and from the Android SDK Manager (20.0.3). Failed multiple times.
Received the same error each time,
"Failed to parse properties from User/myname/.android/avd/nameIGaveEmulator/config.ini."
EDIT: I tried to solve the path problem on my own by checking folders and moving them around to be in the same folder, then resetting the path in Eclipse preferences, but that didn't work, so I trashed everything except for the zip files, uncompressed and started the entire installation all over again. When I opened up SDK Manager and attempted to download tools and platforms, however, I received the following. I'd forgotten that I received it on the first install. Would this have something to do with the problem?
Preparing to install archives
Downloading Android SDK Platform-tools, revision 14
Installing Android SDK Platform-tools, revision 14
Stopping ADB server failed (code -1).
Installed Android SDK Platform-tools, revision 14
Stopping ADB server succeeded.
Starting ADB server failed (code 255).
Done. 1 package installed.
Sidenotes:
When I open Eclipse and SDK Manager, I don't see anyplace to check that I'm the administrator.
If a path needs to be "changed" what exactly does that mean and how do I go about doing so? Is it simply a matter of moving folders and files into the "correct" locations and then trying to load an AVD again?
Using command line, navigate to the /tools folder in your android SDK, then use the command:
$ ./android avd
This will launch the AVD manager.