Update
Update to 4.6.0
New in 4.6.0 — builds without GitHub and FlangApp builds. A new install builds apps with nothing but the activated license: no GitHub account, no build repository and no own Codemagic account. Apps are built on FlangApp's build servers; every license gets free build minutes, then a minute of build time is paid from the Flangapp AI credits (see Initial Setup, Step 2). Installs that already build from their own GitHub repository or on their own Codemagic account keep doing so after the update — nothing changes for them, and they can switch in Settings → Build API. A build minutes counter is shown in Settings → Build API, on App download and in the new build dialog; App download shows the stage and progress of a running build; the administrator's own apps build, preview and send push notifications without a plan. There are no database changes, and you don't need to run GitHub Repository Updates for 4.6.0.
Version 4.6.0 can be installed over any 3.x version and 4.0.0 – 4.5.6. From 4.5.0 on, FlangApp updates itself: Settings → Software updates shows a new release with its notes and installs it with one button — the panel downloads it, checks the vendor's signature and every file, backs up the files it replaces, installs them and updates the database. “Roll back” puts the previous version back. Automatic updates are off by default; they can install fixes only or all releases during the hours you choose (server time), and the administrators get an e-mail. Every admin page shows a notice when a new release is out. Updates are free with an active license and need the PHP zip, sodium and curl extensions. If you are already on 4.5.0 or newer, use Settings → Software updates instead of the steps below.
In 4.5.4 Android apps are built for Android 7.0 (API 24) and newer, as Google Play requires (“Play Auto-protect requires SDK 24 or higher”); apps get it with their next Android build. In 4.5.2 the panel says when GitHub no longer accepts the saved access token and offers to connect GitHub again; if your builds or GitHub Repository Updates stopped working after you connected GitHub with the “Connect GitHub” button, connect GitHub once more in Settings → Build API. Version 4.4.0 adds the Landing page: ready-made landing covers for your sign-in page, bought in Landing page → Store and customized with a live preview. In 4.3.2 iOS apps target iOS 15.0 instead of 12.0, so App Store Connect accepts them again (error 90068 “Invalid deployment target”); apps get it with their next iOS build. In 4.3.1 Flangapp AI connects to the credits service from servers behind a CDN or proxy such as Cloudflare or Hostinger: the install confirms its domain instead of being refused. In 4.3.0 GitHub is connected with “Connect GitHub” (sign in on github.com with a code, no token to create), Codemagic needs only its API token, and both steps of the Initial Setup Wizard are optional. In 4.2.5 the OneSignal step of the Initial Setup Wizard is optional, so a new install can be finished without push notifications. In 4.2.4 apps keep the user signed in after they are closed completely: Android and iOS save the website's cookies as soon as the app leaves the screen. In 4.2.2 apps no longer show “App not available” when the network is not ready yet at launch: they wait on the splash screen and try again. In 4.2.1 the administrator's Flangapp AI in the customer cabinet spends the install's own credits, as in the admin panel. Version 4.2.0 added native apps for WooCommerce, Shopify and WordPress sites, and Flangapp AI now names the platform behind every site. Version 4.1.2 opens Flangapp AI first when you open an app, 4.1.1 made the panel work on phones and tablets, 4.1.0 opened Flangapp AI to your customers, and 4.0.0 added Flangapp AI, the in-browser app preview, faster builds and Android API level 36. The database is updated by the panel itself, so there is no SQL to import.
1. Upload the files
Copy the contents of Update/4.6.0 PRO/FILE/Backend over your backend folder and the contents of Update/4.6.0 PRO/FILE/Frontend over your frontend folder, replacing the existing files — both folders: this is the last update you upload by hand. Upload them as the web site's own user (FTP or the hosting file manager), so that the panel can replace the files in later updates. Your .env file and Frontend/data/config.json are not in the package and stay as they are. If your server uses PHP OPcache, restart PHP or reset OPcache.
2. Open Software updates and update the build repository
Log in as the administrator. The database is updated as soon as the panel opens (4.2.0 adds a table for the platform connections, 4.4.0 one for the landing covers). Open Settings → Software updates and click “Continue install”: “Database Updates” and “UI Updates” are green. Click “Install” next to “GitHub Repository Updates” and wait until it finishes — this brings the native app screens into your build repository, and the 4.2.2 launch fix and the 4.2.4 sign-in fix into the app template, so this step is required when you update from 4.2.3 or earlier; from 4.2.4 it is not needed. Apps get the fixes with their next build. When every line is green, builds work again. Until then new builds wait with the message “Installation isn't complete.”
If “Database Updates” shows an error, the database user usually lacks the right to create or change tables. Import Update/4.6.0 PRO/database/db.sql in phpMyAdmin with a user that has these rights and reload the page. The file can be imported more than once.
3. Activate the license
Flangapp AI and the updates from the admin panel use your license. If the license is not active yet, activate it in Settings → AppFast license.
The starter template repository is github.com/anzgorn/flangapp_pro_starter. Version 4.6.0 uses it on its own; you don't need to change .env.
Updating versions before 3.0
To update your website, simply copy or replace the files in the Update.zip file into the corresponding folder or file.
1. First, access your phpMyAdmin and select the Flangapp database.
Click on the Import button in phpMyAdmin.
2. Select the db.sql file in the update folder.
3. Click the Import button at the bottom of the page.
Please replace/add the files inside the update folder to the corresponding files/folders on your web server. The new version is ready to use.
Update from 2.7 to 2.8
If you have updated your installed version of Flangapp, generate a new GitHub token and update it in settings (token only).
Go to the Software updates section and update your repository.