How do I manually update pubspec.yaml? - flutter

I am trying to get dependencies for my pubspec yaml file after I made changes. However, first, I can't even see my IOS Emulator anymore (it seems to have disappeared). I am using MacOS.
Could you please tell me how to update pubspec yaml manually on Android Studio, normally there is a ribbon which shows, but after I made changes, no ribbon has showed up. Also, if you know how to make my IOS emulator (Xcode simulator) show up again, that would be much appreciated. Thanks.

Go to menu bar > Xcode > Open Developer Tool > Simulator

Related

Using AppCode with Flutter plugin

How can I use AppCode for the ios-specific parts of my Flutter plugin?
I've created the plugin with flutter create --template=plugin --platforms=ios myplugin
The command doesn't generate an XCode project or workspace for the plugin itself but it includes an example app for which it does generate these. Running flutter build ios in example then creates symlinks to the plugin code in example/ios/.symlinks that I can use to edit the actual Swift code with auto completion, code navigation etc. When I open these files in AppCode however, I get the below error and no coding assistance is available at all:
I previously used AppCode quite a lot to maintain some Flutter plugins' iOS code (but switched jobs and didn't need AppCode or Xcode). However, I recently started making a free app, and also wanted to contribute to a Flutter plugin for iOS, I wanted AppCode again. I got AppCode working again, so I wanted to share.
In your flutter directory:
For editing/debugging/running Flutter apps' iOS code: run appcode ios
For Flutter plugins, run appcode example/ios (not appcode ios)
Some principles:
The files don't show up immediately, use Command + Shift + O to find your file. Then Opt + F1 to show it in the project navigator.
Built at least once using flutter run or Xcode (to make sure configuration is set up).
You cannot escape Xcode. Xcode and AppCode are complementary. Find the balance 😂🤓. Refactoring code, debugging the application, searching and reading code works really well in AppCode. Xcode does reading configuration better or debugging builds.
If you get random errors (e.g. everything fails but the error is build failed in AppCode, you should open in Xcode or build/run the flutter app for iOS: flutter run and read the error messages.
If you want to debug both Flutter and iOS simultaneously, start the iOS debugger, then "Flutter attach" in android studio (maybe this is possible in VSCode too, but I don't use that).
Here's an example screenshot of AppCode with debugger working. You might be curious if telemetry flag you set in Flutter was actually being set in the iOS side... maybe there's a bug. But I take privacy seriously and confirm the telemetry is disabled. I also watch network traffic sometimes. 😂. If you're interested, you can then follow that to it's dependencies (manually, using by reading package.swift), and find out it is set to true by default.
UserDefaults.standard.register(defaults: [
#keyPath(UserDefaults.MGLMapboxMetricsEnabled): true
])

Flutter project on android Studio 4.2.1 no database inspector, profiler and emulator window

Two months and no answer. Am I the only one having this problem?
Yesterday I downloaded and installed Android Studio Arctic Fox 2020.3.1 on my new laptop (Windows 10 64 bit, i7-8565U) and HAVE THE SAME PROBLEM AGAIN!!
Android projects I have all tools, Flutter project missing emulator window, database inspector and profiler!
Android Studio 4.2.1 on Windows 10. Latest stable Flutter version.
If I create an Android project I have all tools: database inspector, profiler and the emulator window.
If I create a Flutter project I have no database inspector, no profiler and no emulator window.
Flutter doctor gives no error.
Everything worked fine until the upgrade to 4.2.1
What's going on? Thank you
I've had this issue and been following this question from the time you posted it. Finally found a solution to it on another SO question.
Solution: Enable the Android Facet It turned out that I had to enable
the Android Facet for this project:
Go to File → Project Structure Choose Facets Press the small + Button
at the top Select Android from the list Confirm your project by
clicking the project_name and press OK
Please check out the full answer here:
https://stackoverflow.com/a/68839489/8362593
I hope it works for you too.
If it's not showing then you can do one thing go to
Help > Find action or ctrl+shift+A > Then search.
Try Windows -> Restore default (Shift+F12 by default)
And also you can specify which windows to show: In bookMark View
I think you might rather have the PATH wrong (which means: using an outdated emulator),
because the emulator now resides in directory called emulator (which wasn't always the case).
This can be easily verified:
emulator -v
emulator: Android emulator version 30.8.4.0 (build_id 7600983) (CL:N/A)
If you'd get anything less than the current version 30.8.4.0 (despite having installed version 30.8.4.0 with the SDK Manager), you'd know what the actual cause is. Once having fixed the PATH, the proper version of the emulator should become accessible / usable ...and even an upgrade to Arctic Fox should then be possible, at least while the Flutter build.gradle scripts are compatible with Gradle 7.1.1.
Your workaround in words, you probably found this out, and did not bother to document it.
It is just for the next person :-).
Start your flutter app in debug mode.
Select your android folder in flutter project.
Right click -> Flutter -> Open in Android Studio.
Do NO upgrade Gradle Plugin, when suggested.
It might break flutter build and is not needed.
Android Window:
Click Debug Icon.
Wait a bit.
Click something in your app, so your db is active.
Android Window:
Click App Inspection at bottom of android window.
Result:
The Database Inspector shows up, and you can inspect db content in android window.
-- You have to switch between windows, and yes, it is a pain in the but.
-- Flutter plugin and Android integration is lackluster since 2018, but probably very hard to keep up with all that upstream in sync :-(.
Right, basically it doesn't work. That's it. Maybe one day it will. In the meantime I'm using AS 4.1.3 so that I can get all the available tools.
Remember to set environment: sdk: ">=2.12.0 <3.0.0" to have null-safety enabled and to go to Project Structure and set an SDK otherwise you'll get the old ADB.exe file not found when starting the Emulator which means also no Profiler and a bunch of other tools.

Unity can't build game for android

I wanted to try if I can build a game for android. I created a new project and switch to Android platform.
Installed all ndk,sdk.(automatically and manually. I tried both). But I can't build. When click create, nothings happen.
Screenshoot
Did you give the apk a name?
Nothing happens, what do you mean, the window closes and nothing further?
And yes, if you use a device, then you have to give Build and Run

Application project wont run/debug over device

I'm building an android app using Eclipse, and when I want to run/debug it on my android device, it wont run, even if it is just a "hello word" project.
The information shown on console tab is:
"Installation failed due to invalid APK file!"
I'm wondering what was wrong, and how to fix it.
I found this thread that almost had the same problem with yours: Eclipse installation failed due to invalid APK file?
Please apply those solutions first, then get back to me if it's still not fix
You may have made changes to your versions in your Android manifest file. Delete the app from your device and run it again!

Eclipse using Android emulator

I wonder if anyone has faced the same problem.
When we done some modification on the code, as the emulator is running; is there any way we could see the instant change without closing the emulator?
Sometimes when I made changes on the code then run the emulator, the amendment that I made doesn't seem to show on the emulator even after I clean the project.
Does anyone have any idea how to solve this?
Thanks.
Eclipse has an option under 'Run' in the menu bar to build, and run. This will re-package the application and send it to either your AVD, or attached android phone.