title: Socket API: not allowed in packaged apps?
body: <p>I'm trying to use the new <a href="https://developer.chrome.com/trunk/extensions/apps/socket.html" rel="nofollow">Socket API</a> for Chrome extensions, and I'm encountering a confusing error.  The manifest for my sample app looks like this:</p>
  
  <pre><code>{
    "name":"Yet Another Socket App",
    "version":"0.0.1",
    "manifest_version":2,
    "permissions":[
      "experimental", "socket"
    ],
    "app":{
      "launch":{
          "local_path":"index.html"
      }
    }
  }
  </code></pre>
  
  <p>The app is loading (i.e., no error alerts), but a warning appears beneath its entry in <code>chrome://extensions</code>: <code>'socket' is not allowed for specified package type (theme, app, etc.).</code></p>
  
  <p><strong>Notes:</strong> <code>index.html</code> exists and is a simple HTML document (and <code>chrome.socket</code> is indeed <code>undefined</code> within it). I have enabled experimental APIs via <code>chrome://flags</code>. I am running the Dev channel of Chrome (<code>v22.0.1229.6 dev</code>) on Ubuntu.</p>
  
  <p>Is this a momentary hiccup in socket support (this is the Dev channel, after all), or am I setting up my app incorrectly somehow? Also, I had to uninstall Chrome Stable to install Dev; is it possible that <code>apt-get purge google-chrome-stable</code> and <code>rm -rf ~/.config/google-chrome</code> was insufficient to clear out every piece of the Stable channel?</p>