-
-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attempt to invoke virtual method 'java.io.File com.parse.ParsePlugins.getFilesDir()' on a null object reference #983
Comments
Thanks for opening this issue!
|
Please, if possible, provide more explanations step by step |
In my manifest
I initialize like this
when i do a fresh install i get i dont know it is a miss configration but install object is not saved in the database yet I/flutter (27336): API Request (_Installation : ParseApiRQ.save) : server response :
|
These items you added in the manifest are for Parse Android, these items are not needed for Parse Flutter, please check the push notifications document again. |
after removing the manifest, the app doesnt crash on fresh install , but at least one ID field (deviceToken, installationId) must be specified in this operation {"code":135,"stack":"Error: at least one ID field (deviceToken, installationId) must be specified in this operation\n at RestWrite.handleInstallation (node_modules/parse-server/lib/RestWrite.js:954:11)\n at node_modules/parse-server/lib/RestWrite.js:105:17\n at runMicrotasks ()\n at processTicksAndRejections (node:internal/process/task_queues:96:5)"} thanks for your help |
Is the current user logged in? |
when user is not logged in |
New Issue Checklist
Issue Description
Attempt to invoke virtual method 'java.io.File com.parse.ParsePlugins.getFilesDir()' on a null object reference
after following steps for push notificationActual Outcome
it fails the first time the apk getting install , the second time i run debug , the app opens perfectly
Expected Outcome
Environment
Parse Flutter SDK
7.0.0
3.16.3
3.2.3
macos 14.2 (23C64)
Server
6.4.0
Logs
The text was updated successfully, but these errors were encountered: