We're thrilled to announce enhancements to Xcode test reporting in Bitrise, designed to improve your mobile app debugging workflow. For iOS developers, our new Beta feature allows for better visibility into Xcode test results on the Build Details page.
Xcode 15 is set to introduce significant stack updates potentially impacting workflows. With these updates, while underlying components or tools may change, testing with Edge Stacks is essential to anticipate and adjust for these shifts.
In this blog post, we’ll round up the best mobile CI/CD advice from last year’s Mobile DevOps Summit to help you release better apps, faster. Our Agenda and Speaker list have been released for our 2023 Mobile DevOps Summit: October 4 - 5.
Bitrise has introduced a new feature that allows you to connect to your code repositories using a private link, simplifying the way you build apps. With this update, you have more control and security, and the process is quicker and less complicated, making managing workflows easier.
We urge users not on private or dedicated plans to test their builds on Xcode 15 with the Edge stacks before September, 2023.
Ship Android apps faster than ever. Our new features allow you to effortlessly integrate with your Google Account, create production releases and release directly to the Google Play Store. Read more on this, and what's coming next.
In this blog post, we unveil a range of new features and enhancements for Release Management. From easier TestFlight distribution and automation triggers to seamless App Store version number management, these updates will take your app deployment experience to new heights.
The mobile app development process is complex and requires continuous monitoring and improvement. Mobile CI/CD enables developers to automate the entire mobile app development process — making it faster and more efficient.
Bitrise streamlines Apple device management by introducing automatic device registration and enhanced control over device registration, simplifying the process and saving you time and effort.
In mobile development, flaky tests are a persistent issue. They’re frustrating because a test is ‘flaky’ when it produces both ‘passing’ and ‘failing’ results from the same code. This wastes developers’ time by triggering unnecessary investigations and delays the integration of their code.
