I'm absolute newb to flutter, with objective to focus more on windows-desktop apps. It seems that flutter running on windows-desktop require way more DLLs than mentioned on https://docs.flutter.dev/development/platform-integration/windows/building page. I have created and build absolute minimum Flutter application on my dev machine (Win10 22H2). All went fine, starts and runs as expected.
I have then put mentioned DLL in the folder, along the runner app (testapp.exe) and copied over to test machine running Windows Server 2019 Version 1809 as VMWare image. Both Debug and Release versions of Flutter app (testapp.exe) fails. Debug version fails with MessageBox shown "Code execution cannot proceed because MSVCP140D.dll was not found" which I assume is a debug version of msvcp140.dll (this was present in the testapp.exe location while running).
Trying to run Release version produce no error message at all, application is visible in TaskManager for brief second and exits. Running ProcMon against test application shows it seeks numerous other DLLs which were not mentioned in the flutter docs (see attached pic for reference)
Question - is there some more comprehensive list of Flutter windows-build requirements ?
I am trying to setup flutter on my device, so far I have been able to download the flutter SDK and android studio and satisfy the conditions of flutter doctor to start learning android application development:-
flutter doctor
I ignored the absence of visual studio as I don't want my app to be compatible with windows(as I am trying to develop for Android) but I am not able to fix the missing java bundle, any help on how would I do that?
I just ignored it for a second and moved on to set up my emulator but on running, it shows a pop up which says "Attach a debugger or ESC to cancel"(the pop-up is something like this.) how would I fix it.
This doesn't run the app on the emulator so how would I fix that?
Also on trying to debug, it throws this error, I am totally confused on how to proceed further to at least run my app so that I could start developing and learning flutter?
I am following along this to run my application.
Edit:
I have the java bundle in place but don't know how would I configure Android Studio to get it.
java's prescence
Also that the emulator is now showing that the System UI is not responding and on closing it, it further shows this.
It's been a week since I am trying to work out the setup of flutter but some way or the other some issue happens, please help.
Thanks in advance.
you have to install java runtime environment and It'll work. get from here
it'll show like this if you have JDK installed properly.
I am using flutter version 1.22.6, I have already published my application and have to make minor changes in my application that is why I do not wish to upgrade flutter sdk in my application. But when I try to build my application it says:
Xcode build failed due to concurrent builds
It pops up till some time and then it displays the error:
unable to attach DB: error: accessing build database
database is locked Possibly there are two concurrent builds running in the same filesystem location.
I have tried the solutions such as closing the Xcode and building only from my VS Code editor, also tried flutter clean and then build. Can someone help me with this if I do not have to upgrade flutter?
Don't do anything, just wait another minute or two and then it works (for me, at least).
Note: I'm just starting to work with end-to-end testing so please forgive my noobness.
The problem
I am trying to execute end-to-end test using Protractor with Jasmine and Appium on a iOS device on a simple dummy application created with Ionic v1. All what I am trying to make the test do is just click a button located with: element(by.css('a[icon-on=ion-ios-chatboxes]')).
What I am getting is a timeout but I wasn't able to track down the problem to the root.
Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
The interesting part is that on an Android device works without any problem.
Environment
Appium version: v1.6.5
Last Appium version that did not exhibit the issue: -
Desktop OS/version used to run Appium: macOS Sierra 10.12.3
Node.js version (unless using Appium.app|exe): v7.8.0
Mobile platform/version under test: iOS 10.3.1
Real device or emulator/simulator: Real Device
Appium CLI or Appium.app|exe: Appium CLI
Link to Appium, Protractor and webDriver logs
https://gist.github.com/SpedsT/e16e4ee6093fde873c18467e96392296
Safari doesn't support the async javascript calls Protractor uses to determine if Angular is ready. You can try if your tests will work when you disable wait for Angular. You can find more about how to do this here.
Issues concerning Safari can be found here
I've read every StackOverflow that I could find on this issue, but I still can't work it out.
I'm trying to deploy an app to actual device (NOT emulator). But I receive the following error when i try to build:
Severity Code Description Project File Line
Error Error : DEP6100 : The following unexpected error occurred during bootstrapping stage 'Connecting to the device '30F105C9-681E-420b-A277-7C086EAD8A4E'.':
SEHException - External component has thrown an exception. App1
and
Severity Code Description Project File Line
Error Error : DEP6200 : Bootstrapping 'Device' failed. Device cannot be found. App1
It's worth mentioning that I went from Windows 7 to Windows 10. It's also worth mentioning that my computer was missing the IpOverUsbSvc.exe (not just the registry post, but the actual service was missing). Couldn't find any way to get this back so, so my colleague sent over the .exe and the DLLs and I placed it in it's location. And the service is now running and no longer gives any errors. My device is recognized by the PC, it's running Windows 10 Mobile (but I've also tried with a device running Windows 8.1).
Specs on PC:
Windows 10 Pro (Build 10240)
Using Visual Studio 2015
UWP Tools
Any suggestions to fix my nightmare? Thanks!
Steps that helped me. I have windows 10 mobile build 10581 (and now 10586) installed on phone
Turn off Developer mode on your phone.
Deploy app (UWP or SL) by VS2015 -> Error.
Turn on Developer mode on your phone.
Deploy app (UWP or SL) by VS2015 -> Working.
If you change another device or re-connect you must close VS2015, re-launch and do again!
Finally managed to find a solution to this illusive bug.
It seems that if I didn't have the Windows Phone 8.1 Tools installed I couldn't build to an ARM device (not even Windows 10 Mobile).
So my step to solve this was:
Go to Control Panel -> Programs and Features -> Microsoft Visual Studio ... 2015 -> Modify. And then select the Windows Phone 8.1 Tools.
Pretty pissed that one can't get a reasonable error message when things like this is missing.
I had this issue after updating my device to win10 ver:10.0.10581.0. I tried many things but finally after installing latest sdk and emulators i got it working. You may try installing from this page sdk and emulator:
https://dev.windows.com/en-us/downloads/windows-10-developer-preview
Somehow the new emulators were not visible in vs, they got visible after few restarts and then on device debugging started to work.
But one problem still remain from me that vs crashes after ending debug session with device.
desktop-->my computer--> right click--> management--> service--> start the service Windows Phone IP over USB Transport (IpOverUsbSvc) although maybe the starttype is set as automatic
Seems like there are many issues causing the same error message.
This one worked for me Windows Phone deploy Issue
Essentially you need to remove/uninstall the device from Windows. Then after unplugging and plugging back in, the device and drivers are reinstalled.
I tried many of the suggested solutions to no avail.
After changing the USB-C cable from a USB 3.1 port to a USB 2.0 port on my computer, the error goes away. YMMV
I see it is quite an old post...but I still get this problem. In my case, this happened after I deployed to a second phone I had for testing. After that, VS 2017 now only wants to deploy to that phone and not to the other phone no more. If I start another project, the other phone is recognized and deployable to (listed as device under debug).
Restarting system fixes this...
Also, if I add another project as reference (like a background task) to my project, I will loose the ability to select the devices and emulators under debug. VS 2017 simply then seems to deploy to the last device selected...(really no clue what this is). I have not been able to get the selection of emulators and devices back yet on this one. I only will have the "Start" and "Download new emulators" options. I think this has to do with the fact that VS maybe doesn't know the type (like arm/86/64) of the reference project because it is not set (not needed as this defies the purpose of referencing a project for dynamic references and not the compiled device specific file...)
Hope it helps someone ....
I uninstalled the existing version of the app in device and re-ran it and it worked for me
I got that error for a really simple reason...just opened a new solution I downloaded from GitHub, pressed F5, and got it!
I had left my build configuration in the default "Debug - ARM" setting, when I changed to "Debug - x64" it worked fine!
(Just adding another reason for completeness, not likely to affect your case!)
In case it's helpful for others... I got: DEP6701 bootstrapping failed ... access denied.
Thanks to comments here, I only dev-locked then dev-unlocked my phone (was originally dev-unlocked). Totally works now (took some time installing missing frameworks at first). All good.
Thanks
One more thing could be tried.
Uninstall the existing app if any and then deploy from Visual Studio.
Try on another usb port. It worked