1. Updating modifications in the Changelog > Update menu

Some modifications made into your app only require to be updated from the Publish > Changelog > Update > Settings menu.
We refer to this operation as publishing the Settings of the app.

As long as the changes are visible in the Publish > Changelog > Update > Settings menu, they can only be seen in the backend preview and in My Apollo Apps app.
The changes in GREEN on this list will be visible into your app after clicking the green "Update" button at the bottom of the Changelog > Update menu.

How to read this page:
A : Date of your last update of the settings (the green changes). All changes made before that date are already visible in the web app and native app. All changes made after that date are listed bellow, and only visible in the backend and My Apollo Apps preview.  
B : Number of modifications yet to be updated.  
C : List of modifications organised by date.
D : Detail of the modifications made on a specific date, after clicking "See the details".  
E : Update button. Clicking on it will publish all the changes listed on the page, and make them immediately visible in your web app and native app. You will have to close and reopen the app to see them. 

2. IMPORTANT

If one of the native apps has just been generated and is in "Ready" status, or if it is pending validation on one of the stores, the Changelog > Settings menu will be temporarily locked. You will still be able to work on your app in the backend, but won't be able to update the Settings.

It is forbidden to update Settings while the app is being reviewed by the stores.
You must wait until the backend marks the native version as published to access this menu again.

3. Updating modifications in the Web App

In order for your web app to be active, you must generate it once from the menu Publish > Publication > Web App.  
Once this is done, updating the settings (the process we described in the part 1/) is usually enough to update the Web App as well.

However, some modifications need a generation of the web app to be applied. You can see those in the menu Publish > Update > Changelog > Web App Engine.

You can see 2 types of information:

Your updates :
They are the updates that you did in your backend which require a generation of the web app in order to be visible.  
The changes you see in this part would be the Maps API Key, and the Facebook ID.

Engine updates :
They are the changes made by the technical team of Apollo Apps. They require a new generation of the app to be implemented in your current Web App.  
For example, a bug fix will be visible on this list, and the Web App must be rebuilt so the bug fix can be applied.

BEWARE: Generating your app will automatically update all the changes of the Settings menu (the changes in green we mentioned in the first paragraph).

4. Generating the Native App (Android and iOS)

In order to fully use your native app, you must generate it once from the menu Publish > Publication > iOS or > Android (depending on the version you choose).  

Like the Web App, updating the Settings (the process described in the paragraph 1/) is enough to update most of the modifications you can do in your Native App.

However, some modifications will require to generate (build) the app in order to be visible into the Native App.
These modifications are listed in the menu Publish > Update > Changelog > Native Engine.

Every time you regenerate (rebuild) the app, you have to install it on your device to see the changes listed under the Native Engine list.
If the app is already published on the stores, you need to submit a new version to iTunes Connect or Google Play so that your users can install the newest version on their phones and see your latest updates.

To generate your app, click on the button Submission Android or Submission iOS at the bottom of the page. You will be redirected to the submission process of the native version you have selected.

BEWARE: Generating your app will automatically update all the changes of the Settings menu (the changes in green we mentioned in the first paragraph).

Did this answer your question?