{"id":2059,"date":"2011-07-22T09:22:57","date_gmt":"2011-07-22T17:22:57","guid":{"rendered":"https:\/\/blog.mhvt.net\/?p=2059"},"modified":"2011-07-22T09:23:51","modified_gmt":"2011-07-22T17:23:51","slug":"is-mac-os-x-lion-a-nightmare-release-for-software-developers","status":"publish","type":"post","link":"https:\/\/blog.mhvt.net\/?p=2059","title":{"rendered":"Lion Oddities for Mac Software Developers"},"content":{"rendered":"<p><a href=\"\"><img loading=\"lazy\" decoding=\"async\" src=\"mac\/lion_developer_nightmare\/osx_lion_icon.jpg\" width=\"120\" height=\"120\" alt=\"Mac OS X Lion nightmare\" \/><\/a><br \/>\n<br \/><\/br><br \/>\n<br \/><\/br><br \/>\nSo Mac OS X 10.7 is finally out.  This OS release can be quite trouble-making for those who distribute their software products through <strong>Mac App Store<\/strong>, which Apple, Inc. opened in January 6th.<br \/>\n<br \/><\/br><br \/>\n<br \/><\/br><\/p>\n<table width=\"440\" border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tr>\n<td width=\"440\" valign=\"top\"><a href=\"mac\/lion_developer_nightmare\/library_01.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"mac\/lion_developer_nightmare\/library_01.jpg\" width=\"440\" height=\"330\" alt=\"Mac OS X Lion nightmare\" \/><\/a><br \/>\nScreenshot 1 &#8211; Source: MacHouse<\/td>\n<\/tr>\n<\/table>\n<p><\/br><br \/>\n<br \/><\/br><br \/>\nIf you develop Mac software products, you probably know that the primary location where your application is allowed to access and store files is <strong>Application Support<\/strong>.  More specifically, the path is Users\/User\/Library\/Application Support\/(application name)\/.  As you see in Screenshot 1, however, you don&#8217;t find &#8216;Library&#8217; inside the User folder.  Under Mac OS X 10.7, this folder is hidden.  So you have to reveal invisible files at first to access the Library folder.  If you have done so, you may probably want to add it to the sidebar.  (See Screenshot 2.)  If you click on the favorite folder you&#8217;ve just added, whether invisible files have been revealed or not, you can have quick access to the Library folder. &nbsp; <!--more--><br \/>\n<br \/><\/br><br \/>\n<br \/><\/br><\/p>\n<table width=\"440\" border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tr>\n<td width=\"440\" valign=\"top\"><a href=\"mac\/lion_developer_nightmare\/library_02.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"mac\/lion_developer_nightmare\/library_02.jpg\" width=\"440\" height=\"330\" alt=\"Mac OS X Lion nightmare\" \/><\/a><br \/>\nScreenshot 2 &#8211; Source: MacHouse<\/td>\n<\/tr>\n<\/table>\n<p><\/br><br \/>\n<br \/><\/br><\/p>\n<table width=\"440\" border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tr>\n<td width=\"440\" valign=\"top\"><a href=\"mac\/lion_developer_nightmare\/safari_certificate_download_01.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"mac\/lion_developer_nightmare\/safari_certificate_download_01.jpg\" width=\"440\" height=\"330\" alt=\"Mac OS X Lion nightmare\" \/><\/a><br \/>\nScreenshot 3 &#8211; Source: MacHouse<\/td>\n<\/tr>\n<\/table>\n<p><\/br><br \/>\n<br \/><\/br><br \/>\nIn order to upload an application to Apple&#8217;s <strong>iTunes Connect<\/strong>, you must first code-sign and then convert it into a package.  Chances are that you have to go to Developer&#8217;s web site and create\/download certificates.  And you really want to avoid using <strong>Safari<\/strong> to access <strong>Developer Certificate Utility<\/strong>.  If you use Safari, you can probably download one of the certificates by clicking on the Download button.  (See Screenshot 3.)  Now, try downloading another one with Safari.  You may find out that Safari will divide this web page into table parts such that you can no longer click on any of the buttons.  (See Screenshot 4.)  Too bad\u00e2\u20ac\u00a6  You must quit Safari if this oddity occurs.  How inconvenient\u00e2\u20ac\u00a6<br \/>\n<br \/><\/br><br \/>\n<br \/><\/br><\/p>\n<table width=\"440\" border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tr>\n<td width=\"440\" valign=\"top\"><a href=\"mac\/lion_developer_nightmare\/safari_certificate_download_02.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"mac\/lion_developer_nightmare\/safari_certificate_download_02.jpg\" width=\"440\" height=\"330\" alt=\"Mac OS X Lion nightmare\" \/><\/a><br \/>\nScreenshot 4 &#8211; Source: MacHouse<\/td>\n<\/tr>\n<\/table>\n<p><\/br><br \/>\n<br \/><\/br><\/p>\n<table width=\"440\" border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tr>\n<td width=\"440\" valign=\"top\"><a href=\"mac\/lion_developer_nightmare\/show_package_01.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"mac\/lion_developer_nightmare\/show_package_01.jpg\" width=\"440\" height=\"330\" alt=\"Mac OS X Lion nightmare\" \/><\/a><br \/>\nScreenshot 5 &#8211; Source: MacHouse<\/td>\n<\/tr>\n<\/table>\n<p><\/br><br \/>\n<br \/><\/br><br \/>\nFor many years, we&#8217;ve been accustomed to right-button-clicking (or control-clicking) and choosing <strong>Show Package Contents<\/strong> to open the application package.  (See Screenshot 5.)  So you know what will happen next, right?  Under <strong>Snow Leopard<\/strong> and other previous OS versions, Finder will open a new folder window to reveal the Contents folder.  Under Lion, Finder will not open a new folder window.  Rather, it will show Contents under the same folder.  (See Screenshot 6.)  If you need to add files before you make an application package, this change can be a bit tedious for you.<br \/>\n<br \/><\/br><br \/>\n<br \/><\/br><\/p>\n<table width=\"440\" border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tr>\n<td width=\"440\" valign=\"top\"><a href=\"mac\/lion_developer_nightmare\/show_package_02.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"mac\/lion_developer_nightmare\/show_package_02.jpg\" width=\"440\" height=\"330\" alt=\"Mac OS X Lion nightmare\" \/><\/a><br \/>\nScreenshot 6 &#8211; Source: MacHouse<\/td>\n<\/tr>\n<\/table>\n<p><\/br><br \/>\n<br \/><\/br><\/p>\n<table width=\"440\" border=\"0\" cellspacing=\"0\" cellpadding=\"0\">\n<tr>\n<td width=\"440\" valign=\"top\"><a href=\"mac\/lion_developer_nightmare\/missing_architecture.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"mac\/lion_developer_nightmare\/missing_architecture.jpg\" width=\"440\" height=\"267\" alt=\"Mac OS X Lion nightmare\" \/><\/a><br \/>\nScreenshot 7 &#8211; Source: MacHouse<\/td>\n<\/tr>\n<\/table>\n<p><\/br><br \/>\n<br \/><\/br><br \/>\nIn order to upload application packages, you need <strong>Application Loader<\/strong>.  The latest version of <strong>Xcode<\/strong> is 4.1 and includes Application Loader 1.5.  So just launch Application Loader and select a package to upload to iTunes Connect, right?  Well, if you use Application Loader 1.5, you may encounter the following error message.<br \/>\n<br \/><\/br><br \/>\n<br \/><\/br><br \/>\n<strong>The application is invalid.  The executable (application name) is missing a required architecture.  At least, one of the following architecture(s) must be present: i386, x86_64.<\/strong>  (See Screenshot 7.)<br \/>\n<br \/><\/br><br \/>\n<br \/><\/br><br \/>\nYou won&#8217;t get this message because you have a PPC binary.  You used to be able to use Application Loader 1.4 to upload software packages to iTunes Connect before Apple released OS X Lion.  Now, you can&#8217;t.  Indeed, you will see a different error message if you use Application Loader 1.4 to upload packages to iTunes Connect under Snow Leopard.  So what now?  Bring Application Loader 1.5 to a computer running Snow Leopard?  Nope.  After wasting several hours of my valuable time, I&#8217;ve finally figured out a workaround.  <u>Use Application Loader 1.4 under Lion to upload software packages to iTunes Connect<\/u>.<\/p>\n<p>You must use Xcode 4.1 to install <strong>productbuild<\/strong> (CLT) on a computer running OS X Lion.  But don&#8217;t use Application Loader 1.5 that comes with Xcode 4.1?  Instead, use Application Loader 1.4 that comes with Xcode 3.2.5?  That is quite odd, isn&#8217;t it?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>So Mac OS X 10.7 is finally out. This OS release can be quite trouble-making for those who distribute their software products through Mac App Store, which Apple, Inc. opened in January 6th. Screenshot 1 &#8211; Source: MacHouse If you &hellip; <a href=\"https:\/\/blog.mhvt.net\/?p=2059\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":342,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19],"tags":[],"class_list":["post-2059","post","type-post","status-publish","format-standard","hentry","category-apple-mac"],"_links":{"self":[{"href":"https:\/\/blog.mhvt.net\/index.php?rest_route=\/wp\/v2\/posts\/2059","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.mhvt.net\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mhvt.net\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mhvt.net\/index.php?rest_route=\/wp\/v2\/users\/342"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mhvt.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2059"}],"version-history":[{"count":19,"href":"https:\/\/blog.mhvt.net\/index.php?rest_route=\/wp\/v2\/posts\/2059\/revisions"}],"predecessor-version":[{"id":2078,"href":"https:\/\/blog.mhvt.net\/index.php?rest_route=\/wp\/v2\/posts\/2059\/revisions\/2078"}],"wp:attachment":[{"href":"https:\/\/blog.mhvt.net\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2059"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mhvt.net\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2059"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mhvt.net\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2059"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}