Platform

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 available at Server Settings, this block looks like below:

Now, you can select the version you’d like to have and click on SAVE button.

Breaking changes

Before upgrading to a newer version of Parse Server, it is highly recommended that you keep a development app to apply this change.

Also, in this topic, you can check the most common errors to don’t be stumbled upon a breaking change. See:

Parse Server 5.2.3 or higher

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 to make it work.

1
2
3
4
5
6
{
"fileUpload": {
    "enableForPublic": true,
    "enableForAnonymousUser": true
  }
}

enableForPublic: This setting refers to public upload.
enableForAnonymousUser: This setting refers to anonymous user upload.

Parse Server 3.7.2 or higher

Before upgrading to a Parse Server version equal to or higher than 3.7.2, note that word id turned into a reserved field and it is related to GraphQL implementations. Note that you might not able to manage your objects with Create, Read, Update or Delete via REST API or SDK.

Parse Server 3.1.1

There are two problems that might happen:

  1. 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 fewer words, this update has cleaned up Cloud Code syntax.

  2. 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 > iOS Push notification > Settings and check if there is any expired certificate.

In order to renew the certificate, you can upload a new one following this documentation about generating a 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 doesn’t work for you, please contact our support team with the app Id via 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.