How updates reach the phone (most arrive on launch, some need the store), and the two-minute fix.
Revolve Core ships two kinds of mobile updates. Most are delivered over the air: the app checks for a new version every time it launches and applies it on the next launch. A few — new native capabilities — need a new build from the App Store or Google Play.
§The two-minute fix
- 01Force-quit the app (swipe it away), then open it again. Wait for the sign-in or home screen.
- 02Force-quit and open it once more. The update downloaded on the first launch is applied on the second.
- 03Open the App Store or Play Store listing for Revolve Core. If it shows
UPDATE, install it — that means a new build is required and over-the-air updates cannot bridge the gap.
§Why "it works on the web but not on my phone"
The web app at app.revolvecore.com updates the moment it is deployed; the phone updates on launch. If a feature is on the web and not the phone, it is almost always step 3 above — the phone needs the store build.
◆ NOTE
Android testers on the beta track update through the Play Store like any other app; the "Install the mobile app" guide covers enrolment.
§Still stuck
- ◆Send support the phone model, the OS version, and the app version shown in the store listing.
- ◆The in-app bug reporter (
Report a bug or ideain Getting started) attaches the version and the last screen automatically — use it.
§Related
- ◆Install the mobile app (Getting started)
- ◆Report a bug or idea (Getting started)