Problem only if want Archive App
Has anyone had the problem that the app runs without problems on iPhone or Simulator, but throws an error if i try archive this app?
73 Replies
I have a
target ' Watch App' do
pod 'CryptoSwift', '~> 1.8'
end
in Podfile and all runs. But in Archive get error Missing Module.
Add it using Swift Package Manager instead ? Pods is old school, when life on ios only where objc
@xPsycHoWasPx I don't find CryptoSwift in Swift Package Manager
Enter the github url
GitHub
GitHub - apple/swift-crypto: Open-source implementation of a substa...
Open-source implementation of a substantial portion of the API of Apple CryptoKit suitable for use on Linux platforms. - GitHub - apple/swift-crypto: Open-source implementation of a substantial por...
Or maybe its diff lib im looking at ?
I think this is another one
i will try with https://github.com/krzyzanowskim/CryptoSwift.git
GitHub
GitHub - krzyzanowskim/CryptoSwift: CryptoSwift is a growing collec...
CryptoSwift is a growing collection of standard and secure cryptographic algorithms implemented in Swift - GitHub - krzyzanowskim/CryptoSwift: CryptoSwift is a growing collection of standard and se...
Has swift package also
if github repo has a “package.swift” then it aupports swift package manager
Click add Anyway?
A nice ... this error is gone! Thank you!
But now i have another errors on Apple Watch app:
Seems xcode try build watchos with ios?
But this problem only on Archive
Think your minimum version is set to low
Needs to be ios 14 and up
But it is watchos target where the error is called
And u dont need watchos ?
Just seems strange because watchos and ios is 2 diff things
i have a ios app with watchos app. Both in one projekt
Look in start
Minimum deployments
same error if i change Minimum
did u try clean ?
always do project clean after some major change (this case u went from pod to swift package)
yes and restart xcode
Build works fine
Archive not
Can u show full pic ?
that also display the target in the side menu of errors
Is it “Runner” target that triggers it ?
No, the watch app
So close … u cutted away the very top
just wanted to see what target u picked
also
somethink is messig up 😦
Look one more time on minimum deployment xD
u need to set both targets to do atleast ios 14
But this is watchos
was just making sure
I think i found the problem ....
Debug is watchos ... and release/profile ios!?
hmm why u cut off half xD
Good advice dont hold back on info
But there is Team infos ...
it not problem if it is public?
i cant use those values for anything
its a diff id your team has
or u can just take a marker
and mark them out
But i dont get why watchos part needs ios signing
if its a target only for watchos
its it a 3rd party solution u mixed into your own app or ?
stuff like this often happen if user just slapped existing code into there own without knowing how it works xD
I have add watchos target with option Support Running without iOS App Installation
oh u just took your original ios code ? And added watchos target to all the files ?
But then I wanted to make it embedded in iOS app. So when user install iOS, WatchOS is automatically there ...
Watchos require completely own seperate UI xD
its abit the same with iOS vs macOS
yes, Watchos is complete separate
and works fine 🙂
well something from your other target must get mixed into it
if i start it on device or simulator
so ios UI code / watchos UI code is mixed together
i cant tell without having to look at your files ect xD
maybe time for screen sharing?
right side bar u can see what targets files are assigned 2
Try check all your files, that something from ios have been selected with the watch
Also
or uppersit
but never developed for watchos
so not sure how the process should be vs ios
Maybe because i add this here.
But ok, thank you very much. Now i know why i get this error on Achive. i will try find the problem
is that required when watchos app ?
+ ios app ?
Yes
oki because i know if u make a background app + version that edit the background app, then u mix 2 apps together, so i guess im not surpriced something for watchos is required 2..
DriverKit u kinda embed your drivers into Apps now and install it from there loool
but atm my mind says red flag with the bluetooh app added to ios xD
but thats only because i never done watchos xD
But general its weird that ios target code is flagged by watchos target
Shouldnt trigger ios version error
since no iOS in tsrget to tell it what minimum is
yes
But can be your watchos target is missing something
If i add fresh watchOS app target:
Get the same signing:
Where i can edit Build Configuration in Xcode?
all is handled in “Build Settings” tab
when u have the menu like you do in last pic
is what u doing atm based on following this ? https://developer.apple.com/tutorials/swiftui/creating-a-watchos-app
Apple Developer Documentation
Creating a watchOS app | Apple Developer Documentation
This tutorial gives you a chance to apply much of what you’ve already learned about SwiftUI, and — with little effort — migrate the Landmarks app to watchOS.
And done something semilar as guide says here
and so on
What i ment by selecting files one by one and look in right side if wrong files be picked in watchos also
because even in my own app it tends happen i get message that this feature only avail in macOS 14 (macOS minimum is 13)
and was because i hat both macOS and iOS target picked for thr file, and that feature was implemented in iOS 16 while the other was first added in macOS 14 and not 13 as u would think
since
iOS 16 == macOS 13
iOS 17 == macOS 14
in most swiftui api cases
Example the reason why i didnt just make macOS / iOS combined target, is because same general layout / some touch logic, aint handled equally
also i have Python embeded, because im making a touch designer app for music gear with python scripting
(made my own framework that allows bi directional interop)
but the python part of signing needs different methods on iOS vs macOS xD
and so on