We worked with Fastlane to come up with a solution which required the Heat Recovery Unit which recovers waste heat from the exhaust gases – to be dismantled so that the constituent parts could be taken into the building where it was reassembled.”Īna Cardoso, a Sales Engineer with Fastlane, commented – “We built the Heat Recovery Unit at our manufacturing facility in Kent before disassembly and delivery to the site in sections. Peter Smith, Senior Contracts Engineer at TBS, said – “Many of the buildings we work with are awkward in terms of physically getting the plant equipment in but Baker Street proved particularly challenging. Access to the Baker Street site was particularly difficult which meant a flexible approach was required. Fastlane, part of the Elta Group of companies, worked closely with Birmingham based distributor Air Conditioning Supplies (ACS) and heating and ventilating contractor TBS to design a system specifically to meet the needs of the club, supplying a total of eight bespoke units. The club is located on the famous Baker Street and was the first of the company’s UK sites to use heat recovery technology which allows heat generated from the showers to be harnessed and used in other areas of the building. In one of three projects, Fastlane supplied bespoke units to Fitness First’s new flagship club in the heart of London. Would be great to have someone from Apple confirming this.Heat recovery units from Fastlane Ventilation Equipment are a central feature in the move by Fitness First to make their clubs as green and as energy efficient as possible. The Xcode 13 release notes doesn't seem to have have any details about it, and we didn't find any other official Apple statement mentioning that as well :/. We are not 100% sure if manageAppVersionAndBuildNumber was indeed introduced on Xcode 13, but in case it was already there, then there was a change in behavior since exporting on Xcode 12.* works just fine without it. Should Xcode manage the app's build number when uploading to App Store Connect? Defaults to YES. It seems manageAppVersionAndBuildNumber is a new export option introduced for xcodebuild on Xcode 13, that when set as YES (its default) ends up having this unexpected side effect.įrom xcodebuild -help: Available keys for -exportOptionsPlist: The solution for us was to specifically set manageAppVersionAndBuildNumber on the -exportOptionsPlist for xcodebuild, or in our case more specifically via Fastlane's gym export-options property, to false. It had a very bad side effect on our release, because all third party frameworks had their CFBundleShortVersionString replaced by our app CFBundleShortVersionString in the process of archiving and generating an IPA when using Xcode 13, and some of those third parties rely on their framework version number to be sent on networking calls for them to behave properly.
Hey, in the company I work for we were also facing this issue.
0 kommentar(er)
