I'm on an M1 Mac Mini, Monterey 12.0.1, with XCode 13.1 & it's command-line tools and freshly-installed Flutter MacOS 2.8.0. I create a base Flutter project with
flutter create appname
When I do "flutter run" in the ios folder (in the parent folder it launches ok in Chrome), I get the message:
Could not build the application for the simulator.
Error launching application on iPhone 13.
I tried it with the simulator running, and not. It looks like the Runner XCode project build stages runs a script, xcode_backend.sh. I also tried loading the project in the XCode UI to build and get 'Command PhaseScriptExecution failed with a nonzero exit code' on that script.
If I go and run this script directly, from the project folder of the ios folder:
guy#Guys-Mac-mini ios % /bin/sh "$FLUTTER_ROOT/packages/flutter_tools/bin/xcode_backend.sh"
I get the message:
error: Your Xcode project is incompatible with this version of Flutter. Run "rm -rf ios/Runner.xcodeproj" and "flutter create ." to regenerate.
I tried the steps indicated, which I also found on Google, and removed the folder and regenerated the project, but the same message is appearing. (I did export the FLUTTER_ROOT environment variable, both in the shell and it's also defined in the XCode project settings.
I can build and run the flutter apps to Chrome, but not for the iOS simulator. I also have no problem building and running Swift apps I've coded on the simulator.
I got my Windows and Android setup running in minutes, but on the M1 Mac it's been hours without success. Any ideas?
I'm a developer with decent of experience, but this is my first stab at Flutter and cross-platform (other than Xamarin). Any help is appreciated.
I can't fully explain it, but the problem I was having was related to my having the project files on an SMB share I was accessing from the Mac.
I setup the project on an SMB share so I could access it from my Windows and Mac workstations. I found that any flutter project on that share would fail compilation.
To test this, I created a new flutter app on my Mac Documents folder, comiled and ran it succesfully in the iOS simulator using 'flutter run'. When I moved that project to the SMB share and tried to run it, I got the compilation error again, and it wouldn't run (I also tried clean and run). I moved the project back to the local drive Documents folder, and was able to run it again.
I also noticed that the Mac access to the SMB share is painfully slow, though I tried a required_signon fixes from
https://kb.synology.com/en-us/DSM/tutorial/What_can_I_do_to_fix_slow_SMB_file_transfers_on_OS_X_10_11_5 but it didn't help.
I had even tried to factory reset my Mac, and I thought that fixed it, but it was only because I hadn't connected to the share yet, and made a test project on the local drive.
PS: I don't expect to use the exact same Flutter project between the Mac and Windows workstations because of paths and SDK locations, but I am using it as a convenient place for transfering the source files.
My team was able to solve this by supplying an absolute path to the xcode_backend script in a run phase and running it. Running it once seemed to be enough and we could remove it thereafter:
/bin/sh "/absolute-path-to-flutter/packages/flutter_tools/bin/xcode_backend.sh" thin
/bin/sh "/absolute-path-to-flutter/packages/flutter_tools/bin/xcode_backend.sh" embed
I'm getting a strange error popup I suspect it has something to do with a built in integration of Docker in IntelliJ.
I'm running the following:
Mac OS Big Sur 11.4
IntelliJ 21.1.3
Docker Desktop 3.5.2.18
Docker version 20.10.7, build f0df350
When I launch Docker Desktop, it launches IntelliJ for some reason and I get an error popup immediately:
Title: Cannot execute command
Body: Can not open file /Users/myuser/Library/Containers/com.docker.docker/Data/--list-extensions
I've tried reinstalling both several times and used the Clear cache and clear data options in the Docker settings. I should also note that i've tried removing all projects from IntelliJ and docker and have even disabled the "Docker" plugin in IntelliJ but still get the same error.
Does anyone have any ideas on how to prevent this popup on launch? It is more of an annoyance than a blocker as I can simply close it and then use the tools without problems but its odd that this would happen. Originally I dismissed it as some random system specific configuration but today found that it is not specific to my environment as I got it on a fresh install on a new machine with new user.
It seems a bug of Docker Development Environments Preview. The IntelliJ IDEA is opened by this process.
/Applications/Docker.app/Contents/MacOS/com.docker.dev-envs
You can degrade the Docker Desktop to version 3.4.0 to temporarily fix this problem.
What worked for me today:
Upgrade to Big Sur (wanted to do that anyway).
Remove Intelli-J
Uninstall Docker
Install Docker 3.6.x
Install latest Intelli-J
Problem gone.
I'm using the open source Titanium CLI for updating an app that's currently in the Apple app store. It builds and runs in the simulator without any problems using the command
ti build -p ios
When I try to build for the app store I use the command
ti build -p ios -T dist-appstore -R <company> -P <distribution certificate>
and get an error message
[ERROR] titanium_prep failed to run (10)
[ERROR] This application cannot be built with the Titanium open source SDK because it is an Appcelerator Platform registered application. Please use the Appcelerator Platform CLI tools or Appcelerator Studio to build this application.
I've unregistered the application with the Appcelerator Platform, but it hasn't corrected the problem.
I'm using Titanium Command-Line Interface, CLI version 5.0.6, Titanium SDK version 6.0.0.v20160131225447 and Node version 0.12.7.
Any help resolving this would be greatly appreciated.
There is a migration guide at https://github.com/m1ga/from_zero_to_app/blob/master/appc_to_ti.md
It seems you need to use a GUID that is not registered with appcelerator in the tiapp.xml.
It's also worth removing any <appc-...> or <property name="appc-..."> references to appcelerator services that will be turned off, and set <analytics>false</analytics>
I'm on a Mac with node 0.12 and I was having the same issue with Titanium SDK 5.X.X, but I have changed it to 4.X.X and now I can compile without errors.
I hope you don't need Titanium SDK 5.X.X. or 6.X.X to make your code run...
I met the same problem.
Solution:
re-create your app using $ ti create
or, just build this app using $appc ti build ...
Long explanation:
Our experience is: don't create ti app using $ appc create, just use $ ti create ...
in China mainland, the appc command is not usable at all because of GFW.
I found the related file is the titanium_prep file, which is binary, I can't see any useful information there.
You can't simply edit tiapp.xml and remove the appc/acs attributes to solve this problem
this problem will not occur if you run your app on IOS simulator.
Also, don't downgrade to Titanium 4.X. That means your app won't run at the latest devices.
I'm trying to build a blank cordova application into my iPad Air 2 with Visual Studio 2015 Enterprise edition as i've already done it with success with the release candidate version.
I've got node.js v 4.2.2 on both machines since version 5.2.0 was hanging the build indefinitely, i've also got latest version of iTunes (12.3.1) as well as iOS 9.2 on the mobile device.
I've got the remote MAC set up and everything works fine for the building part, infact i've checked and the .ipa file is there at the end of the build into the folder ...\Documents\Visual Studio 2015\Projects\BlankCordovaApp1\BlankCordovaApp1\bin\iOS\Debug and if i launch that it will correctly install into iTunes and the iPad itself.
The problem is that the build action with Configuration "iOS" and "Local Device" with the iPad connected to the windows 7 PC will hang indefinitely after copying back said .ipa file after writing this line into the Build Output:
2>------ Deploy started: Project: BlankCordovaApp1, Configuration: Debug iOS ------
No matter how much time i wait it wont start the debug session even if i authorized the pc onto the iPad and have my web Inspector turned on onto the safari options. At this point i have to interrupt the build to be able to work again.
What really gets me is that if i connect the iPad to the MAC machine and build with "Remote Device" option the build works fine and i can debug remotely from my windows pc, unfortunately working like that isn't an option since the Apple machine isn't in the same room of my developing machine.
Any insight about this issue would be really appreciate, thanks in advance.
You are using a recent version of node and thus will also need to use a recent version of Cordova.
Specifically, you need to use Cordova 5.3.3 to be able to use Node.js 4.x.x+. The hang you are experiencing is exactly why. It's an incompatibility with a down stream node module and Node 4.x.x. You can downgrade to Node 0.12.x or upgrade your Cordova project to 5.3.3.
http://cordova.apache.org/news/2015/09/22/tools-release.html
Note that Node 5.x.x is only supported in Cordova 5.4.1.
This should be addressed in the latest VS Tools for Cordova Update 6. Deploying to local device is now available.
Take a look at http://microsoft.github.io/vstacoblog/2016/02/04/announcing-update-6.html.
I'm trying to do some testing of a website through the Blackberry simulator, while the simulator works fine, I can't get to any sites in the Blackberry Browser.
Here is the specific setup I'm using.
I'm Windows 7 (64-bit) Home Edition
I have the latest (at the time) MDS installation - BlackBerry Email and MDS Services Simulators 4.1.4
Finally, I have the latest (at the time) Blackberry Simulator - BlackBerry Smartphone Simulators 5.0.0 (5.0.0.442) - 9700
I first start the MDS service, it briefly pops up the command-prompt and then closes it. I'm assuming that when it does that, it started the MDS service. Then I open the Blackberry simulator (9700), which opens up fine and loads the Blackberry OS. Then with the Blackberry OS all loaded up, I navigate to the browser and for example type www.google.com and then at the bottom it just says "sending request" and loads for about a minute. Then times out and says it can't find a connection.
Anyone have any thoughts on what I'm missing? Or, does anyone know of an online simulator for the Blackberry, because thus far this has been a huge pain for testing sites on a Blackberry.
Thank you!
Ben
I started cmd.exe as "Run as Administrator" and then entered
cd "C:\Program Files\Research In Motion\BlackBerry Email and MDS Services Simulators 4.1.4\MDS"
then
run.bat
and now i have the MDS Simlator 4.1.4 working.
It needs the administrator rights to run
The MDS needs to be open when you want to access internet through your Simulator.
In the run configuration setup activate Launch Mobile Data System Connection Service (MDS-CS) with simulator
If the MDS window closes ( the console app ) this is probably because you have a problem with your JDK installation.
Make sure the JDK is in your windows Path.
Here is a screenshot in eclipse.
alt text http://livinloud.ca/documents/MDS.jpg
This is what I did to solve the problem:
Install from BlackBerry Java Plugin (Eclipse IDE) in the directory other than C (Windows directory). This software package includes eclipse IDE for developing BB application, the BB simulator and MDS
You can run the MDS from this location D:\Eclipse_BB\plugins\net.rim.ejde.componentpack6.0.0_6.0.0.30\components\MDS
Just double click "run.bat" file. Wait until the process is finished. In the end you should get something like this
Now, you can run the simulator from this location
D:\Eclipse_BB\plugins\net.rim.ejde.componentpack6.0.0_6.0.0.30\components\simulator
Just double click "9800.bat". the name of this bat file can vary depends on the simulator type.
If you still can't connect to the internet, the default port of MDS may have been used by another software.
You can test it from your browser by opening this address: http://127.0.0.1:8080/
The normal condition should result in something like this
If this isn't the case, you can try to change the port number by editing "rimpublic.property" file at this location:
D:\Eclipse_BB\plugins\net.rim.ejde.componentpack6.0.0_6.0.0.30\components\MDS\config
Replace "WebServer.listen.port=8080" with "WebServer.listen.port=8000" or other port number (e.g 8081, 8082, etc)
(I'm using the BlackBerry Email and MDS Services Simulator Package version 4.1.4, downloaded from here: https://www.blackberry.com/Downloads/browseSoftware.do. I'm running Windows 7.)
When you click on MDS in your start menu, it's running a batch file: C:\Program Files\Research In Motion\BlackBerry Email and MDS Services Simulators 4.1.4\MDS\run.bat
Edit this file and replace !BMDS_CLASSPATH!;!BMDS_CLASSPATH2! with %BMDS_CLASSPATH%;%BMDS_CLASSPATH2%.
Also, you need to run that batch file as an administrator.
I tried changing the shortcut to run.bat to "Run as administrator", but for some reason that didn't work. I ended up making my own batch file that contains this:
C:
cd "C:\Program Files\Research In Motion\BlackBerry Email and MDS Services Simulators 4.1.4\MDS"
run.bat
I made a shortcut to my batch file and set that shortcut to "Run as administrator". I'm not quite sure why that works, but it does.
The batch file starting the MDS simulator requires the environment variable JAVA_HOME to be set.
If this variable has not been set or does not point to a valid Java installation the MDS Simulator just quits.
It should point to the JDK or JRE installation path - e.g. C:\Program Files\Java\jre6
You can test this on command line by entering set JAVA_HOME=C:\Program Files\Java\jre6 before executing the MDS run.bat
When you start up the MDS simulator it should open a command prompt window and stay open. If it's closing immediately then there is something wrong with your environment - perhaps the Java binaries aren't in your path?
I was trying this on Windows 64-bit and had the same problem - the service would launch and then immediately exit. Turns out the error was caused by being unable to create a /logs directory under C:\Program Files (x86)\Research In Motion\BlackBerry Email and MDS Services Simulators 4.1.2.
My solution was to change the permission on that directory to be "Full Control", then the service can start. If you then restart the Device Simulator you can finally browse the web.
Many hours of peoples life must be wasted trying to figure this one out. I just spent a few so I hope my solution works for you all.
I did the set Environmental Variable thing.
I use 4.1.4 and JDK 1.6 something
WIndows 64bit
Uninstall MDS program from C:\Program Files (86x)
Install elsewhere. I installed on my desktop as administrator.
I don't know if the Environmental Variable thing helped but MDS worked right after I installed administratively on the desktop.
If you started the simulator before starting MDS then it creates some .dmp files that appear to impede the connection between the device simulator and MDS. Try deleting the .dmp files from the simulator directory and see if that helps.
I just spent 2 days trying various of the tips online about MDS (and there are many) but none helped me.
For me, the solution was to turn off network registration upon simulator launch in eclipse.
(posted in case someone with my problem googles to this page)
For those of you who might still have issues, I found this to be the simplest, easiest solution:
Copy the installed MDS folder to somewhere outside of Program Files (e.g. c:\blackberry\mds")
Make sure you have a JAVA_HOME environment variable pointing to the root of the directory where your Java SDK is installed.
follow steps here first: http://supportforums.blackberry.com/t5/Testing-and-Deployment/BlackBerry-MDS-Simulator-does-not-launch/ta-p/446126
then run cmd.exe as Administrator and Go to MDS directory and run the "run.bat" file:
type at cmd prompt,
cd C:\Program Files\Research In Motion\BlackBerry Email and MDS
Services Simulators 4.1.4\MDS
then type,
run.bat
and press enter
The MDS simulator will start running. Then you can open the simulator for the phone and it should work automatically to connect to internet.
I followed all of the above advisals, but MDS didn't still start!
What was wrong? I had installed J2EE (java_ee_sdk-5_01-windows.exe) instead of J2SE (jdk-6u26-windows-i586.exe), with the latter MDS worked properly
This installation lost me one awful day and a terrible night.
I have it working, what I did....
(Windows 7-64bit)
a) confirmed my Java environment vars:
JAVA_HOME=....\Java\jdk1.6.0_24
JDK_DIR=...same...
JDK_ROOT=...same...
JRE_HOME=...\Java\jre6
(different things need different vars...)
b) installed the "BlackBerry_JDE_6.0.0.0.exe" to non-magic location (E:\Emulators)
c) launched the start-menu item "MDS-CS"
The command window stays open, it is logging the comm events.
d) launched the start-menu item "Device Simulator"
The "BlackBerry 9800 Simulator" launched. I then started the browser and connected to "www.google.com"
Everything was launched as a regular user (no admin privs).