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
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!
Version 2.2.7 of Parse Server
Same app hosted also on Parse.com
You've searched through existing issues. Chances are that your issue has been reported or resolved before.
Steps to reproduce
Open the Config section in the dashboard for a Parse app, and make sure that a few items are there. Also, make a GET on /config (make sure that the Master toggle is on) and see the underlying JSON. Now, still in your hosted dashboard, open the same app, but pointing to the server on api.parse.com/1. When executing /config with master enabled, the results come normally, meaning that the master key is setup correctly.
I opened the web inspector and saw this:
You can see that Safari and Chrome show the type of the request as POST, even though that ConfigStore requests a get from the JS SDK.
Could that be an issue on the Parse JS SDK?
The text was updated successfully, but these errors were encountered:
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Dashboard!
Steps to reproduce
Open the Config section in the dashboard for a Parse app, and make sure that a few items are there. Also, make a
GET
on/config
(make sure that the Master toggle is on) and see the underlying JSON. Now, still in your hosted dashboard, open the same app, but pointing to the server onapi.parse.com/1
. When executing/config
with master enabled, the results come normally, meaning that the master key is setup correctly.I opened the web inspector and saw this:
You can see that Safari and Chrome show the type of the request as
POST
, even though thatConfigStore
requests a get from the JS SDK.Could that be an issue on the Parse JS SDK?
The text was updated successfully, but these errors were encountered: