Closed chandrapol closed 1 year ago
Hi @chandrapol,
I checked the CocoaPods Specs repo and can confirm that the 16.11.3 release exists there.
Can you try a pod install --repo-update
, so that CocoaPods will fetch the latest specs, and see if that resolves your issue?
Hi @jyaganeh :
Even before running pod install --repo-update
, I see Airship was fetched.
Podfile.lock
PODS:
- Airship (16.11.3):
- Airship/Automation (= 16.11.3)
- Airship/Basement (= 16.11.3)
- Airship/Core (= 16.11.3)
- Airship/ExtendedActions (= 16.11.3)
- Airship/MessageCenter (= 16.11.3)
- ...
- ...
But for some reasons, our project does not recognize. It is happening only on Xcode 14.3.
Xcode 14.2 just runs fine.
@chandrapol Ill try to reproduce today. Thanks for the update
What version are you coming from? In SDK 16 we had to rename the module import to AirshipKit
from Airship
to avoid a conflict with the class Airship
.
What version are you coming from? In SDK 16 we had to rename the module import to
AirshipKit
fromAirship
to avoid a conflict with the classAirship
.
pod 'Airship', '~> 16.11.3'
What was the previous version in your pod lock file for Airship? If you replace import Airship
with import AirshipKit
does your issues go away?
import AirshipKit
This worked. I will close this issue.
Thanks you very much for your effort and time in responding.
Preliminary Info
What Airship dependencies are you using?
pod 'Airship', '~> 16.11.3'
What are the versions of any relevant development tools you are using?
pod 'Airship', '~> 16.11.3'
14.3 (14E222b)
1.11.3
13.3
Report
What unexpected behavior are you seeing?
What is the expected behavior?
Xcode reports
No such module Airship
. Airship has been working since years. This is happening with new Xcode update (to 14.3).What are the steps to reproduce the unexpected behavior?
14.3
pod deintegrate
pod install
Do you have logging for the issue?
Not relevant