It uses Fastlane action download_dsyms with extended timeout for build processing and downloads dSYMs always for the latest build. The Github Actions workflow looks something like this and uses Fastlane: So we’ve setup another Github Actions workflow to run periodically every 30 minutes and check for dSYMs on AppStore Connect, and if there are some new ones, download them and upload the to the Firebase. Once Xcode Cloud is done, new build for internal users is available in TestFlight.īut we also use Firebase Crashlytics to monitor our crashes and app issues, and because Bitcode was enabled by default on Xcode 13, and because the archive is done via Xcode Cloud workflow, we don’t have the archive available locally / in Xcode Organizer and we don’t have valid dSYMs at this moment. Once master detects changes, CI will again run tests but it will also notify Xcode Cloud to trigger a workflow there and Archive our app for AppStore Connect internal testing. If things look good, and you get an approval by code reviewer, you can merge your PR to the master. Run tests on our CI (MacMini on MacStadium) Run danger and check if PR has all things it should have (updated tests, hashtag in title for proper changelog parser, …) Run swiftformat on the changed files and push to the PR Github Actions trigger couple of workflows: Let’s first talk about our workflow that we used to have last couple of months (until last week).ĭevs work on their branches and then open up a PR to the master branch. Last 12 months with Xcode 13 & Xcode Cloud & Fastlane
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |