Unable to kick-off a build in CodeMagic #2202
-
If you are looking for help, please confirm the following...
Which mobile framework are you using?Flutter (Dart) Steps to reproduce
Expected resultsBuild should kick-off Actual resultsI do not see a build being kicked-off Build id (optional)No response |
Beta Was this translation helpful? Give feedback.
Replies: 12 comments 13 replies
-
we're running into the same issue - is there an alternative way to initiate builds in the web site? |
Beta Was this translation helpful? Give feedback.
-
Experiencing the same issue. Also UI popup for starting new builds often doesn't allow to click "Start new build" button, showing it as grey. |
Beta Was this translation helpful? Give feedback.
-
Experiencing the same issue. I am unable to select a workflow file as the selector is stuck in a |
Beta Was this translation helpful? Give feedback.
-
I'm also having problems adding a new project, after I choose my repository and platform, nothing happens after pressing "Add Application". |
Beta Was this translation helpful? Give feedback.
-
I'm unable to choose a github branch while in the flow to create a build. |
Beta Was this translation helpful? Give feedback.
-
I'm experiencing a similar problem, I am able to select the branch but unable to select the workflow when trying to kick off a build. |
Beta Was this translation helpful? Give feedback.
-
Over 3 hours now 👎 |
Beta Was this translation helpful? Give feedback.
-
I'm unable to trigger the build, please fix this |
Beta Was this translation helpful? Give feedback.
-
One of the really frustrating things about this situation is that since this discussion forum is the only form of communication with the team, and nobody has replied, there isn't even a way to know if they are aware of the situation--and since the slack group is gone it feels safe to assume that since there's no response after multiple hours that nobody on the codemagic team is getting these notifications. |
Beta Was this translation helpful? Give feedback.
-
Similar issue, not able to start a build. |
Beta Was this translation helpful? Give feedback.
-
Hi Everyone, |
Beta Was this translation helpful? Give feedback.
-
Dear users, We want to provide an update on the incident that temporarily impacted our services and share some insights into the situation. Approximately at 23:00 UTC (November 16), our team received an alert signaling potential issues with our service. Unfortunately, due to incomplete actions, the alert was not handled as effectively as it should have been. Regrettably, this led to the escalation of the situation, resulting in a temporary service disruption. As a result, users with repositories connected via SSH keys were not able to start builds. Repositories using other authentication methods, such as GitHub App or OAuth, were not affected. The issue was fully resolved around 04:00 UTC (November 17). We understand the frustration and inconvenience this may have caused, and we sincerely apologize for any disruption to your experience with Codemagic. We want to be transparent about the issue and assure you that we are actively addressing the root cause to prevent similar incidents in the future. One of the key challenges we faced during this incident was a lack of immediate availability to handle the escalated alert. We acknowledge the importance of timely response and are implementing measures to ensure that there is always a designated team ready to address potential issues promptly. Here are the steps we are taking to enhance our incident response and prevent future disruptions:
We understand the trust you place in our services, and we are committed to learning from this incident to better serve you in the future. Your feedback is invaluable, and we encourage you to reach out to us with any concerns or suggestions. Thank you for your understanding, and we appreciate your continued support as we work to strengthen our systems and processes. Sincerely, |
Beta Was this translation helpful? Give feedback.
Dear users,
We want to provide an update on the incident that temporarily impacted our services and share some insights into the situation.
Approximately at 23:00 UTC (November 16), our team received an alert signaling potential issues with our service. Unfortunately, due to incomplete actions, the alert was not handled as effectively as it should have been. Regrettably, this led to the escalation of the situation, resulting in a temporary service disruption.
As a result, users with repositories connected via SSH keys were not able to start builds. Repositories using other authentication methods, such as GitHub App or OAuth, were not affected.
The issue was fully resolved around 04:00 UTC…