| OLD | NEW |
|---|
| 1 <table class="intro"> | 1 <h2 id="debugging">Debugging</h2> |
| 2 <tr> | |
| 3 <th scope="col"></th> | |
| 4 <th scope="col"></th> | |
| 5 </tr> | |
| 6 <tr> | |
| 7 <td><strong>Description:</strong></td> | |
| 8 <td>Use <code>chrome.pushMessaging</code> to enable to | |
| 9 enable apps and extensions to receive message data sent | |
| 10 through <a href="cloudMessaging.html">Google Cloud Messaging</a>.</td> | |
| 11 </tr> | |
| 12 <tr> | |
| 13 <td><strong>Availability:</strong></td> | |
| 14 <td>Google Chrome 24</td> | |
| 15 </tr> | |
| 16 <tr> | |
| 17 <td><strong>Permissions:</strong></td> | |
| 18 <td><code>"pushMessaging"</code></td> | |
| 19 </tr> | |
| 20 <tr> | |
| 21 <td><strong>Learn more:</strong></td> | |
| 22 <td><a href="cloudMessaging.html">Google Cloud Messaging for Chrome</a><br> | |
| 23 <a href="gcm_server.html">API Reference for GCM service</a></td> | |
| 24 </tr> | |
| 25 </table> | |
| 26 | 2 |
| 27 <h2 id="debugging">Debugging</h2> | |
| 28 | |
| 29 <h3 id="internal-server-error">Internal Server Error</h3> | 3 <h3 id="internal-server-error">Internal Server Error</h3> |
| 30 | 4 |
| 31 <p> | 5 <p> |
| 32 The Push Messaging server responds with HTTP status code 500 | 6 The Push Messaging server responds with HTTP status code 500 |
| 33 (internal server error) if the app that calls the pushMessaging API | 7 (internal server error) if the app that calls the pushMessaging API |
| 34 is not found in the Chrome Web Store. This ownership check | 8 is not found in the Chrome Web Store. This ownership check |
| 35 is designed to prevent people from sending messages to your app | 9 is designed to prevent people from sending messages to your app |
| 36 without your permission. Commonly this error occurs during | 10 without your permission. Commonly this error occurs during |
| 37 development if you run a version of your app without the correct | 11 development if you run a version of your app without the correct |
| 38 <code>key</code> attribute in its manifest file. | 12 <code>key</code> attribute in its manifest file. |
| 39 </p> | 13 </p> |
| 40 | 14 |
| 41 <p> | 15 <p> |
| 42 To fix this problem, simply install your app from | 16 To fix this problem, simply install your app from |
| 43 the Chrome Web Store and copy the <a href="manifest.html#key">key</a> | 17 the Chrome Web Store and copy the <a href="manifest.html#key">key</a> |
| 44 field from manifest.json in the installed app to manifest.json in | 18 field from manifest.json in the installed app to manifest.json in |
| 45 the version of the app that you are developing | 19 the version of the app that you are developing |
| 46 (see <a href="cloudMessaging.html#test-cloud">Testing in the cloud</a> for | 20 (see <a href="cloudMessaging.html#test-cloud">Testing in the cloud</a> for |
| 47 detailed instructions). Note that you need to remove the <code>key</code> | 21 detailed instructions). Note that you need to remove the <code>key</code> |
| 48 field from manifest.json before you upload the app to the Chrome Web Store again
. | 22 field from manifest.json before you upload the app to the Chrome Web Store again
. |
| 49 </p> | 23 </p> |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 12996003:
Dynamically generate a heading for Extension Docs API pages (Closed)
Base URL: https://chromium.googlesource.com/chromium/src.git@master