The essential news about content management systems and mobile technology. Powered by Perfect Publisher and XT Search for Algolia.
The News Site publishes posts to the following channels: Facebook, Instagram, Twitter, Telegram, Web Push, Tumblr, and Blogger.
Appflow, the mobile DevOps platform from Ionic, lets teams push certain app changes instantly with the Live Update feature. The Appflow dashboard provides functionality to restrict these live updates to certain versions of your native application. Now, this native versioning feature is also available in the Ionic Cloud CLI so you can easily update from your existing CI/CD pipeline.
Live Updates from Appflow provide the ability to update the HTML, CSS, and JavaScript of mobile applications without app store approval or a native version update. With Live Updates, release critical bug fixes, UI updates, or business logic changes as soon as they’re ready for your users.
The Live Update feature works by installing the Live Update SDK in your native application and assigning a specific channel. Then, when a web build is assigned that channel, the app will listen for these updates and deploy them within your existing native app. A live update web build can be initiated from the Appflow dashboard or via Automation, or using the Ionic Cloud CLI.
A key feature of live updates is designating a minimum, maximum, and/or equivalent version of your native app to restrict the live update. This controls when updates happen based on the native version to ensure that only binary compatible changes are deployed to your app. Previously, native versioning a live update web build was only available in the Appflow dashboard. You can see full instructions on how to update native version restrictions in the dashboard here.
Now, the new Ionic Cloud CLI command means teams can automate the entire live update from their existing CI/CD platform of choice.
The Ionic Cloud CLI allows teams using their own CI/CD platforms to have granular control of Appflow features like builds, deploys, and live updates. Rather than setting up automations using the Appflow dashboard, you can use the CLI to control exactly when builds are produced and deployed and customize any steps between.
Appflow has added
a new live-update set-native-versions
command to the Ionic
Cloud CLI to set the minimum, maximum, or equivalent iOS and
Android versions for a given live update build ID and app
ID.
To use the new command, pass the required build ID and app ID, as well as the flags for the platform and version restriction type.
Example:
ionic-cloud live-update set-native-versions --app-id=b3456cd --build-id=baf924a --ios-min=1.2.3 --android-min=1.2.3
Setting a minimum means the native binary must be at least this version in order to download the update, while maximum requires the app to be at that version or below. Setting an equivalent means that apps with that native binary version will not download the live update because they are equal.
Native version numbers must
follow the NPM semver
standard, such as
1.0.5
. Appflow will not properly handle version
numbers that are invalid, such as those with leading zeros before a
digit (1.0.05
).
If you are running this command in your pipeline after the build step, you can dynamically pass the build ID by saving the output of the build command as a variable.
Example:
BUILDID=$(ionic-cloud build web --app-id=b3456cd --commit=a9eb85e --json | jq -r '.buildId')
ionic-cloud live-update set-native-versions --app-id=b3456cd --build-id=$(BUILDID) --ios-min=1.2.3 --android-min=1.2.3
Once you’ve set the native version restriction, you can also deploy your live update from the Ionic Cloud CLI with the `deploy web` command.
Example:
ionic-cloud deploy web --app-id=b3456cd --build-id=baf924a --destination="Production"
For more information on the Ionic Cloud CLI and available commands, check out the documentation here. The Ionic Cloud CLI is available for Appflow Standard and Enterprise accounts. If you’re not using Appflow yet for automated native builds and deployments, you canstart a free trial today.
The post Support added for Live Update native versioning in Ionic Cloud CLI appeared first on Ionic Blog.
Read more https://ionic.io/blog/support-added-for-live-update-native-versioning-in-ionic-cloud-cli
This is an excellent opportunity to Join the Club!: Get all our extensions, updates, and support for one year, including releases of new products!
Coupon code BLCKFR22 - Valid until November 30th,
2022.
Read more https://www.extly.com/blog/22-latest-news/791-black-friday-sale-2022-30-off.html
Mobile operating systems are always changing, which means the software used to build your applications needs to as well. At Ionic, we track these updates to ensure you have the most relevant native binary build software within Appflow, our mobile CI/CD solution. Here are the latest build stack updates coming your way.
Support for each build stack within Appflow remains in place for approximately two years after its creation date. When new build stacks are introduced and the oldest build stacks cross this threshold, they are formally retired.
It’s now time to retire the following stacks:
Target Build OS | Build Stack Name | Retirement Date |
---|---|---|
iOS | macOS – 2020.11 | November 29, 2022 |
Android | Linux – 2020.11 | November 29, 2022 |
Any Appflow automations using either of these build stacks will need to be updated. If they are not updated by the retirement date, they will automatically update to the latest build stack!
As a few build stacks make their way into retirement, a new iteration is headed your way.
With the official release of iOS 16, a new build stack was required. We’re happy to share that the macOS – 2022.10 is now available for building iOS binaries! This provides support for the latest build tools such as Xcode 14, Node 18, and more. Check out the documentation for a full list of software versions.
As always, we recommend using the latest build stacks for most apps. However, other build stacks will remain available until they pass their retirement window. This is to ensure apps with requirements for specific versions of a build tool are supported for an adequate amount of time.
To check out the specific software versions supported within each of our active build stacks, check out the Appflow Build Stacks docs. If you’re not building your mobile apps with Appflow, it’s never too late to get started.
The post Latest Appflow Build Stack Updates appeared first on Ionic Blog.
Read more https://ionic.io/blog/latest-appflow-build-stack-updates
Bootstrap Icons v1.10.0 is here with nearly 150 new icons. This release includes tons of new variants for person, building, and database icons, plus new brands, rockets, road signs, globes, and many more. We’re now at over 1,900 icons!
Here’s a quick look at all the new icons in v1.10.0:
Some highlights for the new icons include:
building
to buildings
We also fixed the fill rules for several some issues across the docs, including:
Brand
and
Brands
to be just Brand
Looking for more new icons? Head to the issue tracker to check for open requests or submit a new one.
To get started, install or update via npm:
npm i bootstrap-icons
Or Composer:
composer require twbs/bootstrap-icons
You can also download the release from GitHub, or download just the SVGs and fonts (without the rest of the repository files).
The Figma file is now published to the Figma Community! It’s the same Bootstrap Icons Figma file you’ve seen from previous releases, just a little more accessible to those using the app.
Read more https://blog.getbootstrap.com/2022/11/11/bootstrap-icons-1-10-0/
With the release of Chrome 108 in late November, Chrome will change how the Layout Viewport resizes when the on-screen keyboard gets shown. This change requires developers to take action on their Ionic apps to continue to provide a good experience when using keyboards. This change only impacts Ionic apps running in Chrome for Android and does not impact Ionic apps running in Capacitor or Cordova.
Read on to learn what you can do to ensure your app continues running smoothly when these changes go live.
Developers should update their apps to Ionic v6.3.5 or newer to receive code that automatically accounts for these Chrome changes.
For developers that cannot update their apps to Ionic v6.3.5 or
newer, including Ionic v1-v5 apps, add the following to the
viewport
meta tag in your app’s
index.html
file:
interactive-widget=overlays-content
Full Example:
<meta name="viewport" content="viewport-fit=cover,
width=device-width, initial-scale=1.0,
interactive-widget=overlays-content" />
This meta tag update will cause Chrome to use the pre-Chrome 108 layout resizing behavior.
If you have already updated to Ionic v6.3.5 you do not need to
change your viewport
meta tag. However, you may
still make this change if you would like to continue using the
legacy resize behavior.
More information on the details of these updates can be found in this Chrome Developers blog post. Let us know on the Ionic Forums or Twitter if you have any questions about this update!
The post Preparing your Ionic app for changes coming to Chrome for Android appeared first on Ionic Blog.
Read more https://ionic.io/blog/preparing-your-ionic-app-for-changes-coming-to-chrome-for-android