Is it still the case we can’t create a watchOS companion app with Fire? I notice there’s a static library option that mentions watchOS, but I have no clue what I’d need to do to be honest, I just noticed https://elements.docs.remobjects.com/Platforms/Cocoa/ToffeeVsIsland/ says it’s not possible.
I’m wondering if I can make the app in Xcode and somehow use this library, but not sure.
Awesome, thanks marc, I shall investigate. I just want to add something because it’s there but the users may like for my tower visiting app to have something that simply shows some info of a nearby tower or a simple add a visit function. I also thought maybe a similar simple complication may be useful.
OK, well as expected, trying to get it onto Testflight is taking longer than actually making the quick app! I think it’s this part that I need some guidance on please. I asked Codebot for a summary of what I tried and what to query with you and this is what it says (the ‘we’ made me laugh):
Release builds succeed and produce an IPA and dSYM, but TestFlight rejects the IPA with error 90733:
Missing architecture. The
“Tower Visit.app/Watch/TowerVisitWatchApp.app/PlugIns/TowerVisitWatchExtension.appex”
bundle is missing the [armv7k, arm64] architecture(s).
The armv7k architecture is required for watchOS apps and app extensions
with a MinimumOSVersion less than 9.0.
The arm64 architecture is required for all watchOS apps and app extensions.
Confirmed the Watch extension and its executable are present inside both the Release app and the IPA. This is an architecture issue, not a missing-extension issue.
Inspected the packaged Watch app and extension: both contain arm64_32only.
Raised the minimum watchOS version from 8.0 to 9.0 and rebuilt. Both packaged Info.plists now report 9.0, and the binaries remain arm64_32 only. This addresses the below-9.0 armv7k requirement, but not the missing arm64slice.
Added an explicit simulator arm64 architecture during earlier troubleshooting. This helped the local build configuration but did not add device arm64 to the IPA.
Tested a device arm64 build using Fire’s bundled references, rather than older references in Downloads. It failed with:
No matching CPU architecture "arm64" in reference ".../watchOS/libsqlite3.fx"
No matching CPU architecture "arm64" in reference ".../watchOS/libToffee.fx"
Found a separate minimum-version discrepancy: the Watch app’s Mach-O header reports watchOS 2.0, although its Info.plist reports 9.0. The extension reports 9.0 in both.
Signing/provisioning issues were resolved; they are no longer blocking the Release build.
You advised:
Our current setup targets watchOS 26 or later and builds device binaries for both arm64 and arm64_32. The imported SDK and the Elements runtime libraries need the corresponding slices. Reimporting the Apple SDK alone does not update libToffee, libSilver, or libElements.
Could you clarify the following?
1. Which exact Elements/Fire build and runtime package provides watchOS device arm64 and arm64_32 support, and where should we obtain/install it?
2. What is the correct process to import the watchOS SDK with both device architectures, including SDK references such as libsqlite3.fx?
3. Which project settings should we use for the Watch app and extension? In particular, is watchOS 26 genuinely required as the deployment minimum, or is that simply the minimum used by your working setup?
I did try raising the minimum to watchOS 26, but that alone does not resolve the missing arm64 slices in the installed references and the message was the same.
Also, how do I use this, to same me setting all the numbers the same?
The armv7k architecture is required for watchOS apps and app extensions
with a MinimumOSVersion less than 9.0.
The arm64 architecture is required for all watchOS apps and app extensions.
The second one i can help with. Delete you locol SDK downloads and rebuild with either 26.5 or 27.2. Both of those include arm64 support for watchOS. I don’t think either of them still includes armv7k (or if they even can); if. not you might just have to up that Deployment target to watchOS 9 or later… But i’ll check.
Update: no they don’t; watchOS 11 dropped support for building armv7k.
const MAX_WATCHOS_VERSION_FOR_ARMV7K = "10.3";
No matching CPU architecture “arm64” in reference “…/watchOS/libsqlite3.fx”
No matching CPU architecture “arm64” in reference “…/watchOS/libToffee.fx”
Not sure about libsqlite3, because that’s built elsewhere and my app didnt need it, but im pretty sure the latest version has arm64 in libToffee.
Confirmed, libsqlite3 wasn’t updated; I’ll try to fix that for today’s build, no promise; if not, i can just send you the lib later.
➜ Cola:~/Code/RemObjects/Elements/Bin/References/Toffee/watchOS git:(develop) ✗ # file libToffee.a
libToffee.a: Mach-O universal binary with 2 architectures: [arm64:current ar archive] [arm64_32_v8]
libToffee.a (for architecture arm64): current ar archive
libToffee.a (for architecture arm64_32): current ar archive
➜ Cola:~/Code/RemObjects/Elements/Bin/References/Toffee/watchOS git:(develop) ✗ # file libsqlite3.fx
libsqlite3.fx: data
➜ Cola:~/Code/RemObjects/Elements/Bin/References/Toffee/watchOS git:(develop) ✗ #
Last week’s for sure; maybe a couple weeks more back.
Bit of a hack: <BundleVersionFromProject>..\Weather for iOS.elements</BundleVersionFromProject>
I now have built with Xcode 27.2, and pointed the sqlite reference to the one you’ve supplied, and upped the deployment for the watch bits to 26.0, but am still getting this:
Missing architecture. The “Tower Visit.app/Watch/TowerVisitWatchApp.app/PlugIns/TowerVisitWatchExtension.appex” bundle is missing the [arm64] architecture(s). The arm64 architecture is required for all watchOS apps and app extensions. We recommend using the default Xcode build setting of “Standard Architectures” to build a binary with support for all required architectures. (90733) n/a (ID: UEUY7DXPG7M26CDKB3VXLIKUXE)
Here’ s the bit from the log:
Version 13.0.0.3149 (develop) built on bajor, 20261030-132024. Commit e9ea470.
Xcode Version is 27.2 (27B52), macOS Version is 27.2 (26B123).
No exact watchOS SDK version was specified for target 'Toffee-watchOS', using 'watchOS 27.2'.
Reference 'CoreGraphics' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2/CoreGraphics.fx' for target 'Toffee-watchOS'.
Reference 'CoreGraphics' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2/CoreGraphics.fx' for target 'Toffee-watchOS' (Device).
Reference 'CoreGraphics' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2 Simulator/CoreGraphics.fx' for target 'Toffee-watchOS' (Simulator).
Reference 'Foundation' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2/Foundation.fx' for target 'Toffee-watchOS'.
Reference 'Foundation' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2/Foundation.fx' for target 'Toffee-watchOS' (Device).
Reference 'Foundation' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2 Simulator/Foundation.fx' for target 'Toffee-watchOS' (Simulator).
Reference 'CoreLocation' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2/CoreLocation.fx' for target 'Toffee-watchOS'.
Reference 'CoreLocation' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2/CoreLocation.fx' for target 'Toffee-watchOS' (Device).
Reference 'CoreLocation' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2 Simulator/CoreLocation.fx' for target 'Toffee-watchOS' (Simulator).
Reference '_LocationEssentials' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2/_LocationEssentials.fx' for target 'Toffee-watchOS'.
Reference '_LocationEssentials' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2/_LocationEssentials.fx' for target 'Toffee-watchOS' (Device).
Reference '_LocationEssentials' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2 Simulator/_LocationEssentials.fx' for target 'Toffee-watchOS' (Simulator).
Reference 'rtl' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2/rtl-26.0.fx' for target 'Toffee-watchOS'.
Reference 'rtl' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2/rtl-26.0.fx' for target 'Toffee-watchOS' (Device).
Reference 'rtl' was resolved to '/Users/Jeremy/Library/Application Support/RemObjects Software/EBuild/SDKs/Island/Darwin/watchOS 27.2 Simulator/rtl-26.0.fx' for target 'Toffee-watchOS' (Simulator).
Reference 'libToffee' was resolved to '/Applications/Fire.app/Contents/Resources/References/Toffee/watchOS/libToffee.fx' via XML for target 'Toffee-watchOS'.
Reference 'libToffee' was resolved to '/Applications/Fire.app/Contents/Resources/References/Toffee/watchOS/libToffee.fx' for target 'Toffee-watchOS' (Device).
Reference 'libToffee' was resolved to '/Applications/Fire.app/Contents/Resources/References/Toffee/watchOS Simulator/libToffee.fx' for target 'Toffee-watchOS' (Simulator).
Reference 'libsqlite3' was resolved to '/Users/Jeremy/Downloads/Toffee/watchOS/libsqlite3.fx' via 'HintPath' for target 'Toffee-watchOS'.
Reference 'libsqlite3' was resolved to '/Users/Jeremy/Downloads/Toffee/watchOS/libsqlite3.fx' for target 'Toffee-watchOS' (Device).
Reference 'libsqlite3' was resolved to '/Users/Jeremy/Downloads/Toffee/watchOS Simulator/libsqlite3.fx' for target 'Toffee-watchOS' (Simulator).
Compiling for arm64_32
Whats the Architecture setting in your project? it seems its not eben TRYING to build for arm64, is it set to only arm64_32 by change, instead of to both?
(i checked and it seems we dlont inlcude arm64 in the defauklt settings yet; will fix.
you’ll wanna set <Architecture>arm64_32;arm64</Architecture>
Change those, and that seemed to work (app accepted), and then (failed processing)…
Invalid WatchKit support. The bundle contains architectures that aren’t allowed or is missing architectures that are required. Verify in the Xcode build settings that the architectures on which your app is built are correct. (90398)
Thanks, it is this. I shall investigate further but have to go out now, but thanks for the assistance again. At least I can check without having to wait for App Store response.
Back now! Just one more question, couldn’t work out this:
I added a ‘app store connect account’ in Fire as I assumed that was the plan, and added the corresponding thing in apple, and yet it doesn’t seem to work :
E: AuthenticationFailure(“Keychain item not found: ‘[my apple App Store address]’ for account ‘[my apple App Store address]’\n\nStore the credential in keychain using --store-password-in-keychain-item or provide it directly using the appropriate argument.”) (0)
Ah, no, this doesnt use that yet. Adding the app store accont is a new IDE feature, it will enable creating certs and profiles (and more), from settings and CodeBot. This publishing predates that, you need to set the account name and password in settings as in my screenhot. (Eventually this will be consolidated, yes).
My apologies for being confusing; “app store connect account” landed this week, but i did think of that or made the connection to clarify, when recommending the older publish feature.