Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The problem seems to have been that I was using <a href="http://code.google.com/p/json-framework/" rel="nofollow noreferrer">json-framework</a> in my app, and including it as an additional SDK per <a href="http://code.google.com/p/json-framework/wiki/InstallationInstructions#Option_2:_Use_the_iPhone_Custom_SDK" rel="nofollow noreferrer">the instructions in the wiki</a>. My guess is that XCode got confused by the presence of >1 SDK, and thus couldn't find the default ResourceRules.plist like it's supposed to.</p> <p>I found two solutions (well, workarounds, anyway):</p> <ol> <li>Use the "Code Signing Resource Rules Path" build setting (which is blank by default) to specify the path to the file XCode should use: <code>$(SDKROOT)/ResourceRules.plist</code>. This works, and <em>seems</em> reasonably harmless, but is frustrating in the sense that XCode should be able to figure this out on its own. (I found this solution in a <a href="http://code.google.com/p/json-framework/issues/detail?id=18" rel="nofollow noreferrer">very old issue</a> filed on json-framework.)</li> <li>Don't use the SDK approach. Instead, just include the files directly into the project, and update the <code>#import</code> statements with local paths. This is the approach I ended up taking, since we made a general decision to fold all of the external dependencies into the project itself (so that other developers have less configuration to do on their machines to get up and running).</li> </ol> <p>I'm not sure whether this is a bug in XCode, or something wrong with json-framework but I've <a href="http://code.google.com/p/json-framework/issues/detail?id=58" rel="nofollow noreferrer">filed an issue</a> on the latter just in case.</p> <p><strong>UPDATE, 30 June 2010:</strong> the issue I filed has been closed, and Mr. Brautaset plans to remove support for the SDK option in the next release (2.3) of the project. Also, the <a href="http://github.com/stig/json-framework" rel="nofollow noreferrer">code now lives on GitHub</a>, though the Google Code pages still exist for now.</p>
    singulars
    1. This table or related slice is empty.
    1. POCan't upload application binary to the App Store
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USSixten Otto
    1. USSixten Otto
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCan't upload application binary to the App Store
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI soooo love you man. Just got hit with the same issue and was banging my head for almost an hour. I also got installed Xcode 3.2.2 beta, so started to contemplate re-installing all. You rule!
      singulars
      1. PO
      1. USAleksandar Vacić
    2. COI had a very similar problem with the core-plot SDK I was using. Setting the "Code Signing Resource Rules Path" as described above solve my problem. Thanks a lot.
      singulars
      1. PO
      1. USaogan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload