open -R `find ~/Library/Developer/CoreSimulator/Devices -type d -depth 5 -name "*.app" -print0 | xargs -0 stat -f "%m %N" | sort -rn | head -1 | cut -f2- -d" "`

Read on for some historical AppleScript which applies to Xcode versions previous to 6.

Here’s another Applescript* tool for dealing with the Simulator, since I seem to be on an Applescript/Simulator kick**. Maybe I’m the only one with this problem: a common use of the Simulator for me is testing code that writes out to the Documents folder of the app. And yet, it’s always an unpleasant process to locate the app’s Simulator install folder inside of the Application Support/Simulator folder. It’s not always 100% obvious which SDK folder I ought to be looking in, the containing folder name changes, it’s not self-evidently named, etc. So, I have an Applescript that just finds and opens the Simulator install folder for whatever Simulator app I built and ran last.

[politepix-blog-inline-text-ad]

Or at least, I had an Applescript, but it was dog-slow. But I recently asked for help on MacScripter here and it’s now optimized into a speed demon thanks to Hank and Stefan. The script, to be entered and saved in your Applescript Editor:

# By StefanK at MacScripter: https://macscripter.net/viewtopic.php?pid=140141

property findtype : quoted form of "kMDItemContentType = \"com.apple.application-bundle\""

set simulatorFolder to POSIX path of (path to application support folder from user domain) & "iPhone Simulator/"
set appFiles to paragraphs of (do shell script "mdfind -onlyin " & quoted form of simulatorFolder & " " & findtype)
if appFiles is not {} then
	set mostRecentApp to item 1 of appFiles
	tell application "Finder" to reveal ((POSIX file mostRecentApp) as alias)
	tell application "Finder" to activate
end if

Of you can just download it as an already-saved app if you prefer (it can still be opened and edited in Applescript Editor).

Put it in the dock and click it when you want to see the install folder. I hope it spares you as much annoyance as it spares me. Tip of the hat to MacScripter and regulus6633 and StefanK.

*”What’s the deal with all the Applescript?” you ask. Look, I just want to be well-practiced when Apple rolls out the Applescript Store at WWDC this year.

**My last AppleScript/Simulator post was linked on Alex Curlyo’s blog and it led to a discussion that raised two even better suggestions for accomplishing the same task which are now part of my standard workflow.

I wanted to share a tool that I use in as part of checking an app for behaving correctly under low memory warnings, to the extent that is possible to do so using the Simulator. It’s an Applescript that just sends a low memory warning to the simulator every second or so, so you can go through every function of your app while debugging and see if a low memory warning ever causes a crash due to a required data structure not being available after a low memory warning. It will also smoke out some redraw bugs due to views being released, though for this it is less reliable than the device.

[politepix-blog-inline-text-ad]

In order to use this tool, you need to turn go to Universal Access in the System Preferences and check “Enable access for assistive devices”, and if it doesn’t work immediately, you may need to open the script up in Applescript Editor (usually found in your Utilities folder) and make sure that the simulatorName variable actually corresponds to the name of your simulator app for the version of Xcode you use. You can also change the timer for how frequently simulated memory warnings are invoked.

This doesn’t tell you everything about how your app deals with memory on the device so it is not a substitute for functional device testing, but it will quickly show you if the app can be crashed on the simulator due to a missing data structure, which will often also happen on the device. It isn’t a panacea, just another tool to keep in the toolbox for catching some bugs easily.

If you are using a version of the simulator that has different titling in the menu (I don’t know if there are any around right now but that is likely in the future), you can change the strings in the script which refer to the menu element names.

When you quit the simulator, the script will quit. Since it is a loop that only exits when the simulator is quit, you may have to force quit it if you encounter some circumstance that I haven’t foreseen.

Here is the script uploaded as a zipped applet (you can still open it up in the script editor to edit it):

Politepix Memory Bombardment applet

If you don’t want to download a zipped applet, you can create your own Applescript applet from the following code:

# This requires going to Universal Access in the System Preferences and checking "Enable access for assistive devices".

# This will run until the iOS simulator is quit.

# Created by Halle Winkler, Politepix: /

#If you're using a different simulator version that is called something else, put its name here.
set simulatorName to "iOS Simulator"
# Change the .8 here to whatever interval you want to send simulated memory warnings at. These are seconds, so sleep 1 would mean that it repeats every second.
set repeatRate to "sleep .8"

# If the naming in the simulator menus is different for you, you can change them here

set menuName to "Hardware" # This is the main menu name
set menuItemName to "Simulate Memory Warning" # This is the name of the menu item

tell application simulatorName
	activate
end tell
repeat
	
	tell application "System Events"
		if application process simulatorName exists then
			tell application "System Events"
				tell process simulatorName
					tell menu bar 1
						tell menu bar item menuName
							tell menu menuName
								click menu item menuItemName
							end tell
						end tell
					end tell
				end tell
			end tell
			do shell script repeatRate
		else
			exit repeat
		end if
	end tell
	
end repeat

Hope this is helpful to others.

I’m happy to announce that OpenEars is launched! OpenEars is an open-source iOS library for implementing continuous, multithreaded, and low-overhead speech recognition and text-to-speech, using CMU Pocketsphinx and CMU Flite, for the iPhone and iPad. It uses nice Cocoa-standard cross-project-referenced static libraries and it offers all the easy-to-use Objective-C methods you’ll need to bring round-trip speech functions to your app. The launch version is 0.9.0 and I hope that there will be some cool projects using it.

[politepix-blog-inline-text-ad]