Live status / Other services
Ionic is operating normally.
Ionic is operating normally.
Signal updated 15d ago · Sep 2, 2026, 1:00 PM UTC
Affected surface
Components
0 of 8 affected
Last 30 days · Status timeline
What changed
- Investigating
We are currently investigating issues with iOS build signing on Appflow. This may prevent users from completing new iOS builds using the MacOS builds stacks. We will post more details shortly. Thank you for your patience.
- Monitoring
A fix has been implemented for this and users should be able to run iOS builds as expected. Please reach out to our support team in case if you are still seeing any issues. Thank you for your patience.
- Resolved
This incident has been resolved. If you are still seeing any issues please reach out to our Support team.
- Resolved
At 4pm on September 20, 2023, an Appflow code deployment impacted the ability to download Ionic Enterprise native plugins requiring an authorization key. The issue originated from changes in the way we handle authentication parameters. Users were encountering 403 errors during download requests. The issue was identified and resolved. No action is required from Customers at this time.
- Resolved
Around 8:00 am ET, a partial outage was identified in which iOS deployments that were deployed independently from builds were failing to deploy successfully. A fix was released around 10:00 am ET, which has since resolved any iOS deployment issues.
- Resolved
In the week of March 24, Ionic made some internal changes to GitHub configuration during the process of migrating to a new CI/CD setup. While deploying one service to test the changes, one of the required secrets was not correctly migrated. This was not immediately detected as the service's successful responses were heavily cached. Once the caches expired, the missing secret caused the service to respond with failure responses to permission checks. These failures were incorrectly interpreted by downstream services. This was the root cause of these services failing and resulting downtime with the Appflow dashboard. Once the required secret was migrated and caches were flushed, all service was restored. Remediation CI/CD pipeline is updated to check for missing / incorrectly migrated secrets and fail fast under this scenario. Additional changes weee made to downstream services to not misinterpret failure responses.
- Investigating
Beginning around 5:00 am ET, degraded performance of the iOS build runners has been identified. iOS builds may be intermittently failing. We are working on investigating the issue and should have more details available shortly. Thank you for your patience.
- Monitoring
A fix has been implemented and we currently working on identifying the root cause. We expect that new iOS builds should no longer fail. Thank you for your patience.
- Resolved
This incident has been resolved.
- Investigating
We are currently investigating an ongoing issue with iOS builds in Appflow.
- Monitoring
A fix has been applied that should resolve iOS build failures and we are monitoring the results.
- Resolved
This incident has been resolved.
- Resolved
Starting on Jan 6th, 2024 at 17:17 UTC, Appflow builds using the iOS 2024.10 build stack began failing. An issue was identified that was preventing builds from successful completion, resulting in stuck builds timing out after an hour. The issue was resolved Jan 6th 2024 20:15 UTC.
- Resolved
As a result of Cloudflare's outage, users may have been intermittently unable to access Ionic's services as of 11:48 UTC. The incident was resolved as of 14:57 UTC.
- Investigating
Customers using Azure DevOps as their git provider may be unable to link their repositories or complete builds in Appflow. We are looking into the issue and will share updates as we have more information.
- Monitoring
A fix has been implemented and we are monitoring the results. If you continue to experience issues with builds, please try the following steps: 1. Revoke the Azure DevOps integration in Personal settings > Integrations 2. Reconnect the repository in your app's git settings 3. Push a new commit in your repository 4. Trigger a build from the new commit and confirm whether the cloning process completes successfully Please reach out to us if the steps above do not resolve the issue.
- Resolved
This incident has been resolved.
- Resolved
Tokens were not refreshing as expected, causing builds to fail to initialize. Engineering pushed a fix for this process.