Are you getting kAMDApplicationVerificationFailedError when you try to run your app on a device?
- Check the status of your provisioning profile’s certificate in the Keychain Utility. It may be expired. If so, go to the program portal and create a new one.
Archive for July, 2009
iPhone Developer Bits 2
Jul 9
“Maps” works in Starbucks without an AT&T account. I used it a few days ago to help someone find a local bank. I suddenly realized that I had not logged into anything. A quick test showed that the web browser would not access anything without logging into AT&T first (I use the Starbucks Gold membership to get the free wifi occasionally.) It could be that the data is relaying through Apple.com. Or, perhaps Google has its own deal with AT&T or Starbucks?
iPhone & iPod Touch Tips
Jul 9
Accessing anything that ends in “Apple.com” works in Starbucks for free (without any of the paid account types.) No doubt this is how Apple got iTunes to work with the store’s music to tell you what was currently playing. I havent’ seen this work in a while. Going to the iTunes store shows that they can’t tell me, but I can access the store. It is fun to look at the Apple “I’m a Mac, I’m a PC” ads at Apple.com/getamac/ads.
Time to do something about the network bottleneck this time. How can I do more with what is already here?
Since Firewire can be used to run IP network traffic, and the Mac I was looking to speed up was close to the X-Serve, this seemed natural. Since the Mac in question was a recent-model Intel-based tower, there was a FireWire-800 port available on both ends. And, since we had a cable for that leftover from a hard drive purchase, we were in business.
`
Its pretty easy to setup a FireWire network connection; just plug the cable into each machine. Think of it as a crossover cable (yeah, I know Macs haven’t needed those for a long time…) Once that’s done, all you have to do is setup the network panel on each end.
I deliberately chose to change the subnet to something not used elsewhere on the network. I don’t think I really had to, but it kept it clear which network interface was being used. The office network used numbers like 192.168.10.x for main office computers and 192.168.11.x for the satellite office. For clarity and unlikely collisions later, I chose 192.168.110.x for the FireWire. So the two computers became 192.168.110.50 for the server (which used 192.168.10.50 on ethernet) and 192.168.110.33 for the Mac (which was 10.33 on ethernet)
Setting things up in the Network panel of System Preferences was easy. I selected the FireWire port in the list, set “configure” to “Manually” (required, there won’t be a DHCP server this way), then put in the IP Address (192.168.110.33 or 110.50) and Subnet Mask of 255.255.255.0. The “Router”, “DNS Server” and “Search Domains” entries were not needed. (Ethernet gets the connection to the internet.) Note that you may have to add the FIrewire port to the list with the “+” button first.
Once all that was done, it was just a matter of connecting FileMaker with correct IP number. I went into “Open Remote” and added the new IP as a “Favorite Hosts” entry and removed the old one. Just specifying the FireWire IP address is enough to make the connection go over FireWire.
Now when the user connects, they get 800 MegaBits of speed instead of 100 MegaBits on ethernet. Better yet, the FireWire connection is completely unshared. No one else in that office uses it. No file-sharing traffice, no printer traffic, no internet traffic.
The main user of the Mac reported that the connection was much better than ethernet had been. He experience far faster performance. And thats good, because up to 4 people at once use this Mac for accessing the FileMaker Server. How’s that? Well, that’s a topic for another post. Hint: VNC
The main downsides to networking with FireWire:
1. The computer must be really close to the server. This one happened to be close enough for a 4-foot cable. You can get longer cables, but I don’t know the limits. A quick google shows a 33-feet length claimed for FireWire-400 (still better than 100-Megabit ethernet).
2. FireWire hard drives become unpredictable for disconnect-reconnect. This downside was irritating. The external backup drive for the X-Serve would always mount on the Mac tower whenever we re-connected it. Eventually I broke down and conencted the drive to the X-Serve with USB-2. I could not get it to reliably re-mount to the X-Serve. This could be a show-stopper in other places.
The drive stayed mounted on the X-Serve just fine if we connected it BEFORE connecting the Mac. But once the Mac was connected to FireWire, the drive always mounted on the Mac. Even dismounting it manually with Disk Utility would not let me mount it on the X-Serve. Wherever the drive was mounted it did work fine.