XCode keep search for flutter windows path - flutter

I try to build IOS version to my flutter app
I'm using virtual box with macOC catalina
after edit flutter & app path in XCode like:
when I start to build app archive, XCode show this code
That mean its still looking for flutter windows path (C:\src\flutter..........)
what's wrong here?!

Before running your project in xcode
Do
flutter clean
flutter pub get
go yo your iOS directory in side terminal and run pod install
And remember to run flutter commands you have to download flutter SDK (in your MacOs)

Related

How do I install Flutter app on Android phone?

I couldn't install flutter app on my android phone. How can I do it? I can run by usb debugging However I want to install it on my phone. Can someone help me please?
If you use IntelliJ Idea (it should also work on Android Studio), you can go to
Build -> Flutter -> Build APK, (in the menu bar)
and after building, your apk will appear in
build/app/outputs/flutter-apk/app-release.apk,
just send the file to your phone and install, your phone will probably tell you not do download cause it isn't checked and secured or something, just ignore and install anyway
Connect your Android device to your computer with a USB cable.
Enter cd [project].
Run flutter install.
Source: here
You need to build the app to get the apk. For building apk use this command in console: flutter build apk and if you want to build your apk in smaller size then use this command in console: flutter build apk --split-per-abi.
After building apk you will find it in [project]\build\app\outputs\flutter-apk\app-armeabi-v7a-release.apk here.
If you don't want to build apk and just want to test your app you can run it in profile mode by using this command in console: flutter run --profile.
In android studio under the tools-> build -> build apk will create and app for you and you can get and the output location will show you after the builing the app

Flutter Project build in macOS

I am windows user and have no experience with macOS. I have developed flutter app in Windows 10 using Android Studio. All working fine and already tested with physical Android Device. Now it is the time to test IOS device. There's the problem started.
I can't build my project in XCode. I already changed user defined build settings as shown in screenshots
When build the project, it is still finding the flutter SDK location of Windows OS
This is my flutter doctor check in macOS
Please guide me.
I found the solution with the help of my friend - flutter developer.
Go to the project directory and run flutter create -i swift . It will recreate the ios folder in project.
Then run pod install command under ios folder

Flutter macOS Desktop project release artifact location

I want to build a macOS app from the Flutter project. I can build it and run fine from Android Studio and command line using the following command:
flutter build macos
flutter run -d macos
The documentation says the '.app' file is self-contained and can be distributed as it. However, it doesn't say where it's generated. Do you know how to locate the '.app' artifact for macOS?
mine was in build/macos/Build/Products/Release/$APPNAME.app
And yes, it seems to be entirely self-contained and distributable.

How to make a Flutter Web App run in an Android Emulator

I have created a web app using Flutter and it is running fine.
I wanted to create a mobile app out of it with as little modification to the code as possible and wanted to run it in an Android Emulator, so I installed Android Studio and then a device in ADV Manager. The code did not show any errors but Android Studio is not able to locate the newly installed device. Am I missing something?
The question could also be reframed as: how to convert a Flutter web app into a mobile app.
Source of this answer is :here
Can you try to run the below command in terminal:
flutter devices
Does it show something like this?
Android SDK built for x86 (mobile)
If not, then try to run the following commands:
flutter config --android-sdk <path to android sdk>
flutter config --android-studio-dir <path to android studio>
Replace with the actual path to the SDK in your machine.
And then restart your Android Studio. You should see your virtual device listed under Flutter Device Selection.
Please note, to find the path to Android SDK, you can go to Preferences as shown in this image

Flutter iOS Build Error: framework not found Flutter

I am able to run the app in android studios but whenever I try in xcode I get a flutter framework not found.
upgrade your flutter by doing
flutter upgrade
and it will upgrade the engine and download necessary tools.
This will even kill flutter daemons.
And run the application again
flutter run
Make sure you open .xcworkspace (and not .xcodeproj in XCode).
Ensure you have 'Flutter.Framework' listed under "Linked Frameworks and Libraries". If not, just drag and drop it from the main project. Like below
I was facing the same error whene I try to archive in Xcode
I fixed it by
flutter upgrade
and
flutter run
I fixed this by switching to the master channel, and switching back to the stable channel. Also remember to run 'flutter upgrade' after switching.
Delete the flutter directory.
Download new flutter
Extract it and put it where you want.
Run the command export PATH="$PATH:`pwd`/flutter/bin"
if the command does not work then specify your path like bellow
export PATH="$PATH: /Users/{your user name}/Documents/src/flutter/bin"
Restart your machine and you are ready to go.
After that - inside your project's ios directory -
delete the .symlink directory
delete the Pods directory
delete the Podfile.lock file
and now run -
flutter clean
flutter packages upgrade
flutter build ios
For me nothing worked except, deleting my flutter files fully and reinstalling.
Use this flutter docs for reinstallation: Flutter Installation Link
I tried everything nothing worked except:-
Flutter upgrade
Flutter run
and boom- Build succeeded!
Please try the following steps:
Delete the flutter SDK
Download the same flutter SDK and re-install it
restart the android studio
It should be worked well.
Fixed by switching branches from beta to master