Skip to content

Commit 27051b7

Browse files
committed
doc(ios): update 12.x-2025.01-snapshot
1 parent aa0dc7e commit 27051b7

File tree

2 files changed

+386
-224
lines changed

2 files changed

+386
-224
lines changed

www/docs/en/12.x-2025.01/guide/platforms/ios/index.md

Lines changed: 33 additions & 59 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,18 @@ The table below outlines Cordova-iOS's prerequisites by version. Additionally, X
4949
</tr>
5050
</thead>
5151
<tbody>
52+
<tr>
53+
<td>8.x</td>
54+
<td>13.0</td>
55+
<td>
56+
<ul>
57+
<li>Cocoapods: >=1.16.0</li>
58+
<li>ios-deploy: >=1.12.2</li>
59+
<li>Node: >=20.17.0</li>
60+
<li>Xcode (xcodebuild): >=15.0.0</li>
61+
</ul>
62+
</td>
63+
</tr>
5264
<tr>
5365
<td>7.x</td>
5466
<td>11.0</td>
@@ -102,7 +114,7 @@ There are two ways to download Xcode:
102114

103115
Once Xcode is installed, several command-line tools need to be enabled
104116
for Cordova to run. From the command line, run:
105-
```bash
117+
```zsh
106118
$ xcode-select --install
107119
```
108120

@@ -113,7 +125,7 @@ to launch iOS apps on an iOS Device from the command-line.
113125

114126
Install ios-deploy via [Homebrew](https://brew.sh/) by running:
115127

116-
```bash
128+
```zsh
117129
$ brew install ios-deploy
118130
```
119131

@@ -123,7 +135,7 @@ The [CocoaPods](https://cocoapods.org/#install) tools are needed to build iOS ap
123135

124136
To install CocoaPods, run the following from command-line terminal:
125137

126-
```bash
138+
```zsh
127139
$ brew install cocoapods
128140
```
129141

@@ -137,15 +149,15 @@ For more details on installing and using the CLI, refer to [Create your first ap
137149

138150
To preview the app in the iOS simulator:
139151

140-
1. Open the workspace file (`platforms/ios/HelloWorld.xcworkspace`) from Xcode, _or_ from the command line:
152+
1. Open the workspace file (`platforms/ios/App.xcworkspace`) from Xcode, _or_ from the command line:
141153

142-
```bash
143-
$ open ./platforms/ios/HelloWorld.xcworkspace/
154+
```zsh
155+
$ open ./platforms/ios/App.xcworkspace/
144156
```
145157

146158
2. Make sure the `HelloWorld` project is selected in the left panel (1).
147159

148-
![]({{ site.baseurl }}/static/img/guide/platforms/ios/xcode10-run-project.png)
160+
![]({{ site.baseurl }}/static/img/guide/platforms/ios/xcode26-helloworld-run-project.png)
149161

150162
3. Select the intended device from the toolbar's __Scheme__ menu, such
151163
as the iPhone XR Simulator as highlighted in (2)
@@ -155,7 +167,7 @@ To preview the app in the iOS simulator:
155167
application in the simulator. A separate simulator application opens
156168
to display the app:
157169
158-
![]({{ site.baseurl }}/static/img/guide/platforms/ios/HelloWorld-running-xr.png)
170+
<img src="{{ site.baseurl }}/static/img/guide/platforms/ios/xcode26-helloworld-running-simulator.png" alt="iOS Simulator" width="400"/>
159171
160172
Only one simulator may run at a time, so if you want to test the app
161173
in a different simulator, you need to quit the simulator application
@@ -278,8 +290,10 @@ There is also support to mix and match command line arguments and parameters in
278290

279291
If you have a custom situation where you need to pass additional build flags to Xcode you would use one or more `--buildFlag` options to pass these flags to `xcodebuild`. If you use an `xcodebuild` built-in flag, it will show a warning.
280292

281-
cordova build --device --buildFlag="MYSETTING=myvalue" --buildFlag="MY_OTHER_SETTING=othervalue"
282-
cordova run --device --buildFlag="DEVELOPMENT_TEAM=FG35JLLMXX4A" --buildFlag="-scheme TestSchemeFlag"
293+
```zsh
294+
cordova build --device --buildFlag="MYSETTING=myvalue" --buildFlag="MY_OTHER_SETTING=othervalue"
295+
cordova run --device --buildFlag="DEVELOPMENT_TEAM=FG35JLLMXX4A" --buildFlag="-scheme TestSchemeFlag"
296+
```
283297

284298
You can also specify a `buildFlag` option in [`build.json` above](#using-buildjson) (the value for the `buildFlag` key is a string or an array of strings).
285299

@@ -294,69 +308,29 @@ Cordova for iOS projects can be opened in Xcode. This can be useful if
294308
you wish to use Xcode built in debugging/profiling tools or if you are
295309
developing iOS plugins. Please note that when opening your project in Xcode,
296310
it is recommended that you do NOT edit your code in the IDE. This will edit the code
297-
in the ```platforms``` folder of your project (not ```www```), and changes are liable to be overwritten.
298-
Instead, edit the ```www``` folder and copy over your changes by running ```cordova build```.
311+
in the `platforms` folder of your project (not `www`), and changes are liable to be overwritten.
312+
Instead, edit the `www` folder and copy over your changes by running `cordova build`.
299313

300-
Plugin developers wishing to edit their native code in the IDE should use the ```--link``` flag when adding their
314+
Plugin developers wishing to edit their native code in the IDE should use the `--link` flag when adding their
301315
plugin to the project via cordova plugin add. This will link the files so that changes to the plugin files in the
302316
platforms folder are reflected in your plugin's source folder (and vice versa).
303317
304-
Once the ios platform is added to your project and built using ```cordova build```, you can open it from
305-
within Xcode. Double-click to open the `${PROJECT_NAME}/platforms/ios/${PROJECT_NAME}.xcworkspace`
318+
Once the ios platform is added to your project and built using `cordova build`, you can open it from
319+
within Xcode. Double-click to open the `${PROJECT_NAME}/platforms/ios/App.xcworkspace`
306320
file or open Xcode from your terminal:
307321
308-
```bash
309-
$ open -a Xcode platforms/ios
322+
```zsh
323+
$ open -a Xcode platforms/ios/App.xcworkspace
310324
```
311325
312326
The screen should look like this:
313327
314-
![]({{ site.baseurl }}/static/img/guide/platforms/ios/xcode10-review-settings.png)
315-
316-
## Platform Centered Workflow
317-
318-
cordova-ios includes a number of scripts that allow the platform to be used
319-
without the full Cordova CLI. This development path may offer you a greater
320-
range of development options in certain situations than the cross-platform cordova CLI.
321-
For example, you need to use shell tools when deploying a custom
322-
Cordova WebView alongside native components. Before using this
323-
development path, you must still configure the SDK environment
324-
as described in [Requirements and Support](#link-requirements-and-support)
325-
above.
326-
327-
For each of the scripts discussed below, refer to
328-
[Cordova CLI Reference][cli] for more information on their
329-
arguments and usage. Each script has a name that matches the corresponding CLI
330-
command. For example, `cordova-ios/bin/create` is equivalent to
331-
`cordova create`.
332-
333-
To get started, either download the cordova-ios package from
334-
[npm](https://www.npmjs.com/package/cordova-ios) or
335-
[Github](https://github.com/apache/cordova-ios).
336-
337-
To create a project using this package, run the `create` script in the `bin`
338-
folder:
339-
340-
```bash
341-
$ cordova-ios/bin/create ...
342-
```
343-
344-
To run the app, use the `run` script in the `bin` folder:
345-
346-
```bash
347-
$ cordova-ios/bin/run
348-
```
349-
350-
The created project will have a folder named `cordova` inside that contains
351-
scripts for the project-specific Cordova commands (e.g. `run`, `build`, etc.).
352-
353-
To install plugins in this project, use the [Cordova Plugman Utility](../../../plugin_ref/plugman.html).
328+
![]({{ site.baseurl }}/static/img/guide/platforms/ios/xcode26-helloworld-general-settings.png)
354329
355330
## Upgrading
356331
357332
Refer to [this](./upgrade.html) article for instructions to upgrade your ```cordova-ios``` version.
358333
359-
360-
(Mac®, OS X®, Apple®, Xcode®, App Store℠, iPad®, iPhone®, iPod® and Finder® are Trademarks of Apple Inc.)
334+
(macOS®, Mac®, OS X®, Apple®, Xcode®, App Store℠, iPad®, iPhone®, iPod® and Finder® are Trademarks of Apple Inc.)
361335
362336
[cli]: ../../../reference/cordova-cli/index.html

0 commit comments

Comments
 (0)