Skip to main content

IPA-based FileWave Kiosk for iOS/iPadOS - EOL

The IPA-based FileWave Kiosk / App Portal distribution method for iOS and iPadOS is end of life. FileWave 16.3.0 and later use the Apple App Store version of FileWave Kiosk, delivered through Apps and Books / VPP from Apple School Manager or Apple Business Manager.

What changed

Starting with FileWave 16.3.0, FileWave moved iOS/iPadOS Kiosk delivery to the Apple App Store version of FileWave Kiosk. This is the standard managed-app distribution model for iOS and iPadOS: acquire the app in Apple School Manager (ASM) or Apple Business Manager (ABM), sync Apps and Books / VPP licenses into FileWave, and let FileWave deploy the App Store Kiosk to managed devices.

FileWave no longer ships new IPA packages for Kiosk in FileWave 16.3.0 or later, and older IPA packages will not be re-signed or refreshed. The older enterprise IPA path should be removed from managed deployments.

Who is affected

  • Customers managing iOS or iPadOS devices with FileWave 16.2.x or earlier.
  • Customers that still have an old iOS App - FileWave Kiosk fileset, IPA fileset, or IPA association in FileWave.
  • Customers that have not yet acquired the free FileWave Kiosk app in ASM/ABM Apps and Books.

Customers already running FileWave 16.3.x or later, with FileWave Kiosk acquired through ASM/ABM and no legacy IPA association, are already using the current deployment model.

Required action

  1. Upgrade FileWave Server and related components to FileWave 16.3.x or later. Use a currently supported FileWave release where possible.
  2. In ASM or ABM, acquire the free FileWave Kiosk app through Apps and Books / VPP.
  3. Confirm FileWave is syncing Apps and Books / VPP licenses from ASM/ABM.
  4. Delete the legacy iOS App - FileWave Kiosk fileset or any older IPA-based Kiosk/App Portal fileset if it exists.
  5. Remove any remaining associations to the old IPA-based Kiosk/App Portal fileset.
  6. Run a Model Update, then run an Apps and Books / VPP sync so FileWave recalculates available licenses.
  7. Verify affected iOS/iPadOS devices, or allow them to check in during their normal verification cycle.

Do not create a new IPA fileset or keep an existing IPA association to make the FileWave 16.3.0+ Kiosk workflow function. The current workflow uses the App Store Kiosk app and VPP licensing instead.

Timing and risk

FileWave cannot provide an exact date when an older IPA installation might stop working in a particular environment. The legacy IPA path depends on enterprise IPA signing and the associated distribution account, and those older IPA signatures are time-limited. FileWave will not be issuing refreshed Kiosk IPA packages for this retired workflow.

Because this depends on Apple platform trust and app-signing behavior, the exact user-visible error may vary or may not appear until an app launch, install, update, or redeployment attempt. The safe operational guidance is to move iOS/iPadOS Kiosk deployment to the FileWave 16.3.0+ App Store / VPP workflow before the old IPA path becomes a problem.

Verify the transition

  • FileWave Server is running 16.3.x or later.
  • FileWave is syncing Apps and Books / VPP licenses from ASM/ABM.
  • The free FileWave Kiosk App Store app has enough available licenses for the managed iOS/iPadOS fleet.
  • No legacy iOS App - FileWave Kiosk fileset or old Kiosk IPA association remains in FileWave.
  • Managed devices receive the App Store version of FileWave Kiosk and users can open Kiosk normally.

FAQ

Can we keep using the old IPA until it stops?

That is not recommended. The old IPA workflow is retired, the IPA signature is time-limited, and FileWave will not refresh Kiosk IPA packages for this method. Upgrade to FileWave 16.3.x or later and use the App Store / VPP workflow.

Do we know the exact date the old IPA will stop working?

No. Treat the old IPA method as an end-of-life deployment path and remove it proactively rather than waiting for a device-side failure.

Do we need to buy the FileWave Kiosk app?

No. The FileWave Kiosk app is free, but it still needs to be acquired in ASM/ABM Apps and Books so FileWave can receive and assign VPP licenses.

What if our older FileWave version automatically deployed Kiosk?

FileWave 15.3.0 through 16.2.x used the older automatic Kiosk deployment behavior. Customers with iOS/iPadOS devices should upgrade to FileWave 16.3.x or later so Kiosk can be distributed through the current App Store / VPP workflow.

Related Content

No comments to display

Back to top