Problem Building HomeAssistant with Lottie on M1 Mac

[Wildchild9]

I have cloned this repo and am trying to get it up and running for a debug build on the simulator currently. I am using an M1 Mac mini and I am on macOS 11.4. Also, my Xcode version is 12.5. Here are the steps I took to build the open the project before I tried to build it.

git clone https://github.com/home-assistant/iOS.git
cd iOS

After this, I deleted the Gemfile.lock file as I was getting the error "google-api-client-0.38.0 requires ruby version ~> 2.4, which is incompatible with the current version, ruby 3.0.1p64" when running the next step of the setup process (bundle install). Then I proceeded with the following commands:

bundle install
bundle exec pod install --repo-update
open HomeAssistant.xcworkspace

Once Xcode opened, I selected the App-Debug scheme and chose the iPhone 12 simulator, then I tried to run the application. This build unfortunately fails with the Swift compiler error "Could not find module 'Lottie' for target 'x86_64-apple-ios-simulator'; found: arm64, arm64-apple-ios-simulator" and I have not been able to remedy this.

Any help to get this up and working would be appreciated. Thanks

[zacwest]

You may be the first person to attempt to build on an Apple Silicon machine, so I'm guessing that's the issue here. It looks like Lottie's trying to build using x86_64 instead of arm64, but I'm not sure why that would be. Just to double check - you haven't launched Xcode in any kind of Rosetta mode, right?

Are there any underlying errors elsewhere in the build step? Can you copy/paste the full build command and output from the build progress in the Navigator > Report Navigator > Build.

[Wildchild9]

That is correct @zacwest, I didn't launch it in any kind of Rosetta mode. And I just exported and attached the failed build report. Let me know if there is any other information that would be helpful.
Build App-Debug_2021-06-21T12-11-56.txt

[zacwest]

Your log there definitely looks like it's trying to compile for x86_64, but almost certainly debug is building only the active arch. You can test this theory by commenting out ONLY_ACTIVE_ARCH = YES in HomeAssistant.debug.xcconfig. However, I'm not sure why it's doing the wrong architecture here.

One other thing you can try is build with entirely-source pods -- run XCODE_BETA=true bundle exec pod install -- the deps it changes aren't actually Xcode 13 specific, but all of them are not precompiled.

[Wildchild9]

I tried both of those things and unfortunately neither of them worked. Commenting out ONLY_ACTIVE_ARCH = YES in HomeAssistant.debug.xcconfig introduced a whole new suite of errors. Namely, "Could not find module 'PromiseKit' for target 'x86_64-apple-ios-simulator'; found: arm64, arm64-apple-ios-simulator".
Build App-Debug_2021-07-23T12-37-28.txt

Trying to run XCODE_BETA=true bundle exec pod install during the setup phase instead of bundle exec pod install --repo-update also did not work and just ended up emitting the same error about Lottie.

[zacwest]

Probably the easiest way to get this working is to run the rosetta version of the simulator. I'm not sure why things aren't working as-is, but it may help to add ARCHS[sdk=iphonesimulator*] = x86_64 to the xcconfig and in the Podfile where it sets per-pod build config settings.

[orcema]

I tried both of those things and unfortunately neither of them worked. Commenting out ONLY_ACTIVE_ARCH = YES in HomeAssistant.debug.xcconfig introduced a whole new suite of errors. Namely, "Could not find module 'PromiseKit' for target 'x86_64-apple-ios-simulator'; found: arm64, arm64-apple-ios-simulator". Build App-Debug_2021-07-23T12-37-28.txt

Trying to run XCODE_BETA=true bundle exec pod install during the setup phase instead of bundle exec pod install --repo-update also did not work and just ended up emitting the same error about Lottie.

Did you manage to get it working, because i try to run it on my M1 Mac using rosetta but when i run the command bundle exec pod install --repo-update i get the error "NotificationTestCases"

`
Checking for latest...
Latest available: 6.2.95; latest supported: 6.1.95
Out of date, but latest supported installed
Updating local specs repositories

CocoaPods 1.11.2 is available.
To update use: gem install cocoapods

For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.11.2

Analyzing dependencies
Pre-downloading: CPDAcknowledgements from https://github.com/CocoaPods/CPDAcknowledgements, commit 2f289a19c3ec41f835a9629fdbea4a89033f61a1
Pre-downloading: ColorPickerRow from https://github.com/EurekaCommunity/ColorPickerRow, commit dcf9545cbe75d0f78b1b96e880d6aa85f98b0795
Pre-downloading: Communicator from https://github.com/zacwest/Communicator.git, commit f5dd96048cbe1e7ebfee85688c23c17c6f71f9e4
Pre-downloading: EMTLoadingIndicator from https://github.com/hirokimu/EMTLoadingIndicator, commit ff5b4ccf9bb424cb454e76ee91e32165d2d9c12c
Fetching podspec for Firebase from Configuration/Podspecs/Firebase.podspec.json
Pre-downloading: HAKit from https://github.com/home-assistant/HAKit.git, commit 0e22e80ee8626e5611f00db08f80ef9150b85345
Pre-downloading: NotificationTestCases from https://github.com/home-assistant/mobile-apps-fcm-push.git, commit 03d66c0b348b1b005cba083d5b9007d29501ce43
[!] Unable to find a specification for 'NotificationTestCases'.`

[zacwest]

Hmm, I've had some trouble with that one too. For the moment you can comment it out in the Podfile (it's used to grab .json files, not code, so it will still run), I need to switch that to a subrepo or a script which pulls in those shared test cases.

[orcema]

After serveral trial and errors i made it up to install successfully on M1 MAC.
Executing the installation instructions on the git page

brew bundle
bundle install
bundle exec pod install --repo-update

i got the error:

Could not find rake-13.0.6 in any of the sources
Run `bundle install` to install missing gems.

then i tried

bundle install --path vendor/cache
pod deintegrate
bundle exec pod install --repo-update

and finally installation was successful

......
Generating Pods project
Integrating client project
Adding Acknowledgements
Pod installation complete! There are 34 dependencies from the Podfile and 33 total pods installed.

but now i have the error here below on target WachApp but cant't figure out what this means.

Provisioning profile "iOS Team Provisioning Profile: *" doesn't include the aps-environment entitlement.

@zacwest
Can you please give me a hint for resolving this error, what is this aps-environement entitlement ?

[zacwest]

aps-environment is the APNS environment key. This should be set up by default in provisioning profiles from the automatic provisioning. If you're trying to build to a device, code signing is required; have you set up an account with developer.apple.com? Did you override the team information in the .xcconfig file as the README states?

[orcema]

Yes i did the override for the "DEVELOPMENT_TEAM" and the "BUNDLE_ID_PREFIX" in the

and for most of the targets the automatic signing worked except for targets App, Watchapp and Extension-PushProvider. I managed to fix it manually the automatic signing management except for the WatchApp target.

[zacwest]

Can you share the exact modifications you did to the xcconfig? The advised route is to add additional keys in a gitignored xcconfig, but if you replace the team ID in all the places the xcconfig references it, you're opting into manual code signing for those targets, which requires special entitlements from Apple that you must apply for.

[orcema]

I changed the "team ID" only in the above illustrated HomeAssistant file and then ran the build.
I will start over and try to apply the adivsed route.
I initially followed the advised route but it failed to override the "DEVELOPMENT_TEAM" and the "BUNDLE_ID_PREFIX" .

[orcema]

I followed the advised route and put "DEVELOPMENT_TEAM" and the "BUNDLE_ID_PREFIX" in a new config file "HomeAssistant.overrides.xcconfig"

This time I didn't change anything in the "HomeAssistant.xcconfig"

ran the installation with success, switched sheme to app-debug

then i ran the build and ended up with the same result as previously editing directly the "HomeAssistant.xcconfig", e.g.

I have to switch the provisioning profile in the build settings from "Local Developer" to "automatic".

This works for targets "App" and "Extension-PushProvider" but not for "Watchapp".

[zacwest]

Ah, I see; I thought setting the CODE_SIGNING_STYLE to Manual conditionally would cause it to ignore that specified provisioning profile, but it's still using it as the basis for automatic. That explains why App & the Extensions-PushProvider targets are not working.

I do not see any obvious reason why the WatchApp target is failing, though; it doesn't use any special entitlements there. Can you go to the Signing report in the issue navigator as it's suggesting and paste the contents? It'll look like:

[orcema]

like this ?

Update Signing_2021-10-16T07-14-55.txt

[orcema]

I tried removing the target "Watchapp" but then i get another kind of error

and here i the log:
Build App-Debug_2021-10-16T07-26-53.txt

[zacwest]

Give that branch a try, it should resolve the automatic code signing issues.

[orcema]

i switched over to branch automatic provisioning but ended up with the same error as above when i removed the target Watchapp

and here the error logs:
Build App-Debug_2021-10-16T07-52-39.txt

[zacwest]

Deleting that target will require you to re-integrate Cocoapods, probably; but you should not need to delete the WatchApp target with the branch above.

[orcema]

i switched over to branch automatic provisioning but ended up with the same error as above when i removed the target Watchapp

and here the error logs: Build App-Debug_2021-10-16T07-52-39.txt

This is the build result with the branch "automatic-provisioning" without deleting the target "WatchApp"

[zacwest]

Can you try cleaning in Xcode in Product > Clean Build Folder? This seems like it may be a stale build profile in the new build system. You may need to kill the Pods directory entirely from the earlier target deletion if it's confused.

[orcema]

I already did a "Clean Build Folder" and ran again the working installation procedure for the M1 Mac
#1681 (comment)
but nothing changes, always the same issue...
😢

[zacwest]

It's erroring on the [CP] Embed Pods Frameworks script, saying its input file set (InputFileList-36460EB356C0C600F45AD622-Pods-iOS-App-frameworks-Debug-input-files-4f6d0d76000313cd5d01fc2a2198a9b7-resolved.xcfilelist) contains an element which chains back to it.

It looks like it's the Unembed Lokalise for Catalyst script in the build phase for the App target. If you remove this, does it work?

[orcema]

it compiled with success by changing the build phase position for the [CP] Embed Pods Frameworks

🥳 🎉 Thanks for your help @zacwest

[orcema]

@zacwest I have a last issue concerning the push notifications.
Despite having configured the Notification with a certificate

i still get the build warnings "push provider is disabled".

related log warnings:
Build App-Debug_2021-10-16T10-32-47.txt

what do i have to do to enable push notifiations ?

[zacwest]

That's the local push extension, which requires a special provisioning profile entitlement from Apple. You can ignore it if you're going to be sending notifications via APNS.

[zacwest]

I've got an M1 now (hooray!) and everything seems peachy at this point.

[orcema]

I've got an M1 now (hooray!) and everything seems peachy at this point.

did you have to reorder the build phase position too ?

[zacwest]

No