You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You're all set. The plugin takes care of initializing Parse platform using the `config.xml` preferences mentioned above.
150
-
To customize push notifications, initialize Parse platform yourself, or use your own `MainApplication.java` in Android,
151
-
see the [Advanced Configuration](#advanced-configuration) section.
154
+
You're all set. The plugin takes care of initializing Parse platform using the `config.xml` preferences mentioned above. The plugin will also take care of saving your installation to the database.
155
+
156
+
To customize push notifications, initialize Parse platform yourself, or use your own `MainApplication.java` in Android, see the [Advanced Configuration](#advanced-configuration) section.
152
157
153
158
154
159
## Usage
@@ -303,6 +308,19 @@ skip it's version of Parse initialization and notification setup, that way it wo
303
308
304
309
## Troubleshooting
305
310
311
+
#### General:
312
+
313
+
- Parse uses the term "client key" to specify a key for both Android and iOS. This is different from the Javascript key.
314
+
In the javascript portion of your Cordova/Phonegap/Ionic app, use the Javascript key. This has nothing to do with the plugin.
315
+
In the `config.xml` preference `ParseClientKey`, use Android and iOS client key. Note that for open source [parse-server](https://github.com/ParsePlatform/parse-server), these keys are optional.
316
+
317
+
- For legacy [Parse.com](https://parse.com), the appropriate key is required depending on your client platform, e.g.,
318
+
Javascript, Android or iOS client, dotNet, REST. For open source [parse-server](https://github.com/ParsePlatform/parse-server),
319
+
a key is only required if you have configured your server with it. In the past, our Android users have
320
+
reported strange errors in their logcat relating to missing permission declarations. It turns out those error messages were red herrings.
321
+
The real problem involved a parse-server that required client keys and a missing `ParseClientKey` preference in `config.xml`.
0 commit comments