Parse Server Version

introduction in this guide, you will learn how to change your parse server version goal change the parse server version prerequisites there are no pre requisites to read this page, however, to change it, you should be the app owner parse server parse server is an open source framework that powers an application backend and it speeds up the time for developers by simplifying complicated programming tasks the parse server community is very active and often new versions are released by changing the version of your app, you will be guaranteed to update to the latest version of parse server all it takes is a single click on the change version option to upgrade or downgrade server versions it’s very simple, all you have to do is go to manage parse server manage parse server available at server settings server settings , this block looks like below now, you can select the version you’d like to have and click on the save button breaking changes before upgrading to a newer version of parse server, it is highly recommended that you keep a development app https //www back4app com/docs/platform/app settings#clone app to apply this change also, in this topic, you can check the most common errors to not stumble upon a breaking change see parse server 6 2 0 in this version, there is a security implementation in terms of acl for users that are not set as public read anymore however, in case you'd like to bypass it (not recommended, as this allows other users and unauthenticated users to read data such as email ), you need to add the following configuration in your custom parse options https //www back4app com/docs/platform/custom parse options { "enforceprivateusers" false } parse server 5 2 3 in this version, there is a security implementation in terms of uploading files to your app it’s required to add the following configuration in your custom parse options https //www back4app com/docs/platform/custom parse options to make it work { "fileupload" { "enableforpublic" true, "enableforanonymoususer" true, "enableforauthenticateduser" true } } enableforpublic is true if file upload should be allowed for anyone, regardless of user authentication enableforanonymoususer is true if file upload should be allowed for anonymous users enableforauthenticateduser is true if file upload should be allowed for authenticated users deprecation database hub connection this version no longer supports connection with datasets from database hub clone is still available parse server 3 7 2 before upgrading to a parse server version equal to or higher than 3 7 2, note that word id id turned into a reserved field and it is related to graphql implementations note that you might not be able to manage your objects with create, read, update, or delete via rest api or sdk parse server 3 1 1 two problems might happen there’s a breaking change through the upgrade from 2 x to 3 x related to the cloud code, and you can read more about the changes here in other words, this update has cleaned up cloud code syntax before you change to this version, there is a possibility provided by parse server which allows the user to save the audience for tracking and sending a push notification, so you need to remove this class to prevent problems with the dashboard and database parse server 2 6 5 before upgrading to this version, you need to make sure that you don’t have any expired certificates added to your app, please go to server settings server settings > ios push notification ios push notification > settings settings and check if there are any expired certificates to renew the certificate, you can upload a new one following this documentation https //www back4app com/docs/ios/push notifications/best ios push notification service#step 1 create your push certificates in the apple developer center about generating an ios certificate parse server 2 2 14 revocable sessions were introduced in the middle of 2015 and it helped to improve the security for users so, if it is your current version, you must be aware of a very common problem related to legacy token at this moment, if you are using legacy token, it’s necessary to change to revocable token before selecting a newer version this link can help you with it revocable token migration tutorial if you got some error and the solutions above don’t work for you, please contact our support team via app id chat conclusion at this point, you have learned how to upgrade or downgrade your current parse server version and possible breaking changes based on the most common errors