So, I have connected to my phone using the adb connect command and now everything is going fine. Only issue is after a successful connection and the assembleDebug process the flutter run just get stuck. It's like the debugger is not able to start for some reason. Did anyone face an issue like this ?
System Info:
Flutter SDK Version: Flutter 3.0.2
Device Model: Samsung Galaxy M31
CPU Architecture: Android ARM64
Android Version: Android 12
If yes, I would like to know how you made your way around it. Any help is appreciated ! Thanks in advance.
Related
I'm starting developing mobile using flutter on vscode IDE. I was debbuging the app using a samsung device, everything was ok, but I tryed debug the app using a xiaomi device, however this time i've got an error
Launching lib/main.dart on 166216e0 in debug mode...
Built build/app/outputs/flutter-apk/app-debug.apk.
adb: insufficient permissions for device: missing udev rules? user is in the plugdev group
See [http://developer.android.com/tools/device.html] for more information
Error: ADB exited with exit code 1
adb: insufficient permissions for device: missing udev rules? user is in the plugdev group
See [http://developer.android.com/tools/device.html] for more information
Error launching application on 166216e0.
Exited (sigterm)
There's a difference of android version. Samsung is android 11 and xiaomi is a MIUI Global 12.0.4 android 10.
apart from having usb debug enabled, i've enabled the option to install via usb and usb debugging.
I don't know how to solve this. Any suggestion?
I've updated SDK Manager adding android 10
after that i runned
flutter doctor --android-licenses
but I still not working
I am facing a difficult problem now. Right now I can't do a flutter debug on my real Vivo-v2020 phone device. I've tried everything possible, but I still get this error and can't debug. However, the installed app works properly.
In my device everything is okay, Developer Mode ON, USB Debugging mode also ON
Any solution to this? Please help me... This is very important for me.
log:
Launching lib\main.dart on V2022 in debug mode...
Running Gradle task 'assembleDebug'...
Parameter format not correct -
√ Built build\app\outputs\flutter-apk\app-debug.apk.
Installing build\app\outputs\flutter-apk\app.apk...
I/flutter ( 4243): Observatory listening on ************************************
Actullay i faced this issue in my realme mobiles and vivo mobiles
The way i found to get out of it is.Uninstalling the debugging application using adb command-it remove application from all users and it works fine again
command: adb uninstall com.example.packagename
replace it with our package name
update to android 12 there must be resolved
I also had this problem with my vivo-v2025. But I solved the issue by following a simple step.
First, you just run the app on your phone using debug mode as usual.
Then you will see an error as shown below:
" Launching lib/main.dart on V2025 in debug mode...
✓ Built build/app/outputs/flutter-apk/app-debug.apk.
I/flutter (22675): Observatory listening on***************** "
After this, you just TERMINATE the program and start a fresh new run. The app will open. It worked in my case.
Posting an output image here .
vivo now runs flutter, update to the latest may 1st 2022 patch. You need to upgrade your device by accepting the latest update.
I'm launching the app in a real device.
Anyone knows why this is happening?
Launching lib/main.dart on GT I9063T in debug mode...
✓ Built build/app/outputs/apk/debug/app-debug.apk.
Error waiting for a debug connection: Bad state: No element
Error launching application on GT I9063T.
Exited (sigterm)
Even the hello-world app is showing this error.
Run flutter clean.
This works for me.
I had this error with a clean install on MacOS X (Mojave), and after trial and error discovered that the main user who is running flutter debug needs to be an admin user.
Clue was the line:
log: Must be admin to run 'stream' command
when running from command line.
After this VS Code and command line work.
Build always works on my VS code normally. Updating to the latest Flutter 1.12 also started showing this and most times, my code either shows up on my device first before showing that debug has started or the program just quits. Any fix with VS code because I am not an Android Studio fan.
Try to change flutter channel to beta using "flutter channel beta". it worked for me to fix issue which is because flutter version is updated to "v1.12.13+hotfix.5".
I ended reinstalling flutter sdk.
Ubuntu 16.04
VSCODE
Started with Flutter 12. It seems that the user must be admin now.
Rolling back to a previous Flutter version will do for now.
flutter version v1.9.1+hotfix.6
I changed the channel of flutter to the master and works, I was using the stable channel.
You can use the command:
flutter channel master
or just flutter channel to see another channel.
In the 'Developer Options' of my phone, when I changed the 'Select Debug app' option to 'Nothing', the error was solved.
Try to downgrade the libglvnd package to version 1.2.0 in arch linux.
This started occuring after i updated xcode to 14.1.
Simple Restarting mac works with flutter clean
Could you guys please help me with the problems I currently have?
I'm trying to follow the steps of how to release apk android from: https://flutter.dev/docs/deployment/android, The program which I tried to release is only the NewFlutterApplication which created from template of Flutter
The problem is: Have been followed all the steps, still I can't run the release apk which i build from flutter
The Error which I got:
Error: ADB exited with exit code 1
Performing Streamed Install
adb: failed to install E:\FlutterProject\flutter_app_1\build\app\outputs\apk\app.apk: Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]
Install failed
The things that I have tried:
Tried from this site Flutter release apk is not installing on device, but there is no hope
Tried from this site Can't build release APK for flutter, but still no hope
Tried using the flutter run --release in the real device, it's directly crash and return stopped working
Tried using the flutter build apk && flutter install, it's not running and give the error from top error
Tried using flutter run -v it don't give any error and run smoothly and the debug it's still run smoothly, only the release APK is the problem which can't be run
UPD: This answer is outdated, Flutter now supports x86/x64
You can't run release build on emulator, because currently flutter doesn't support x86 release binaries
See this issue, and put thumb up reaction on it to increase priority:
https://github.com/flutter/flutter/issues/9253
This issue also affects devices that use Intel Atom and some Chromebooks, but don't worry, they will be excluded from supported devices by Google Play automatically
INSTALL_FAILED_NO_MATCHING_ABIS is when you are trying to install an app that has native libraries and it doesn't have a native library for your cpu architecture. For example if you compiled an app for armv7 and are trying to install it on an emulator that uses the Intel architecture instead it will not work.
I try to Packaging project with Android Runtime For BlackBerry I done every thing
-Simulator, ADT- for eclipse .. when i test the app i got this error :
[2013-04-13 13:16:04 - BlackBerryTest] Packaging project BlackBerryTest
[2013-04-13 13:16:11 - BlackBerryTest] Launching BlackBerry Android Runtime...
[2013-04-13 13:16:20 - BlackBerryTest] Connecting to ADB...
[2013-04-13 13:17:23 - BlackBerryTest] Status ERROR: net.rim.ajde code=4 Connecting 192.168.72.128 to ADB failed! null children=[Status ERROR: net.rim.ajde code=0 Please check if the Android player was fully started when you got this error. If not, you can either increase the Android player launch timeout on the BlackBerry->BlackBerry Android Development Tools preference page or wait until the Android player is fully started and try again. null]
in the Simulator there is splash screen contain blackberry 10 logo start about 2 sec and then close and eclipse still Connecting to ADB... about a minute then I got error to connect.
**
UPDATE :
**
Now I got this message
04-25 12:01:15.539: I/navigatorshell(17789061): no app URI, just launch AP and exit
Any Idea ?
This is usually caused by the Android Runtime taking a very long time to load, and in some cases, never actually loading.
The root cause is that the simulator is running very slowly. If you haven't already, enable virtualisation in your BIOS, this makes a massive difference to simulator performance and solved this issue for me.
There's a video about this here: http://devblog.blackberry.com/2012/08/performance-increase-blackberry-10-simulator/