Issue 1:
Steps to Reproduce

I am ready to submit my iOS app to iTunes Connect but not able to Archive to send to Apple.

Run flutter build ios --release

Open Runner.xcworkspace in Xcode v 9.3

Make sure Bundle Identifier is the correct App ID in Apple Developer Portal

Product->Archive Menu Option

Receive Warnings about Swift 3 @object and Error exit code 1 (see below)

Error

Non-fat binary /Users/marco/Library/Developer/Xcode/DerivedData/Runner-asytzrlvctklzifuuprykzalkakh/Build/Intermediates.noindex/ArchiveIntermediates/Runner/InstallationBuildProductsLocation/Applications//Runner.app/Frameworks/App.framework/App is not armv7 arm64. Running lipo -info:
Non-fat file: /Users/marco/Library/Developer/Xcode/DerivedData/Runner-asytzrlvctklzifuuprykzalkakh/Build/Intermediates.noindex/ArchiveIntermediates/Runner/InstallationBuildProductsLocation/Applications//Runner.app/Frameworks/App.framework/App is architecture: arm64
Command /bin/sh failed with exit code 1

Warnings

ld: warning: ignoring file /Volumes/Data/Flutter/fatima_prayers/ios/Flutter/App.framework/App, file was built for arm64 which is not the architecture being linked (armv7): /Volumes/Data/Flutter/fatima_prayers/ios/Flutter/App.framework/App

The use of Swift 3 @objc inference in Swift 4 mode is deprecated. Please address deprecated @objc inference warnings, test your code with “Use of deprecated Swift 3 @objc inference” logging enabled, and then disable inference by changing the "Swift 3 @objc Inference" build setting to "Default" for the "Runner" target.

The use of Swift 3 @objc inference in Swift 4 mode is deprecated. Please address deprecated @objc inference warnings, test your code with “Use of deprecated Swift 3 @objc inference” logging enabled, and then disable inference by changing the "Swift 3 @objc Inference" build setting to "Default" for the "Runner" target.

Logs

iMac:fatima_prayers marco$ flutter analyze
Analyzing /Volumes/Data/Flutter/fatima_prayers...
No issues found!
Ran in 5.2s

Flutter Doctor

iMac:fatima_prayers marco$ flutter doctor -v
[✓] Flutter (Channel beta, v0.3.1, on Mac OS X 10.13.4 17E202, locale en-US)
• Flutter version 0.3.1 at /Users/marco/Development/flutter
• Framework revision 12bbaba9ae (6 days ago), 2018-04-19 23:36:15 -0700
• Engine revision 09d05a3891
• Dart version 2.0.0-dev.48.0.flutter-fe606f890b

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
• Android SDK at /Users/marco/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-27, build-tools 27.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
• All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.3)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 9.3, Build version 9E145
• ios-deploy 1.9.2
• CocoaPods version 1.5.0

[✓] Android Studio (version 3.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 23.2.2
• Dart plugin version 173.4700
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] VS Code (version 1.22.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Dart Code extension version 2.11.2

[✓] Connected devices (2 available)
• Android SDK built for x86 • emulator-5554 • android-x86 • Android 8.1.0 (API 27) (emulator)
• iPhone X • ABCDEdddd.... • ios • iOS 11.3 (simulator)

• No issues found!

Any Ideas?

Issue 2:
@chinmaygarde says this should be very straightforward and is just about teaching our Mac bot to build the ARM32-bit variants of our engine, uploading them to the right place, and teaching our XCode project template to use them.

EDIT: Turns out it was not straight forward. Work is actively underway, @cbracken is driving the effort.