#cocoapods

@ricobeck

Let's pour one for #CocoaPods 🥂

> Pods that are associated with this email:
> - NXOAuth2Client (last updated May 19, 2014)
> - NXCollectionViewDataSource (last updated May 19, 2014)
> - TKCoreDataController (last updated Jul 3, 2014)

0 0 0 0

LOGO PED - Semantic Tags by aéPiot

@logo-ped.bsky.social

3 months ago

MultiSearch Tag Explorer MultiSearch Tag Explorer - Explore tags and search results by aéPiot

#COCOAPODS
multi-search-tag-explorer.aepiot.ro/advanced-sea...
2026 #MAJOR #LEAGUE #BASEBALL #DRAFT
allgraph.ro/advanced-sea...
MultiSearch Tag Explorer

aepiot.ro

0 0 0 0

MacGeneration

@macg.co

6 months ago

Développement : CocoaPods prépare son passage en lecture seule, prévu fin 2026 Nous étions passé à côté de l’annonce initiale de la fin programmée de CocoaPods, un gestionnaire de paquets très populaire dans le monde du développement Apple. Ce type d’outil est très utilisé par les développeurs, car il permet de simplifier la gestion des dépendances indispensables à toute app un minimum complexe. Pour simplifier, CocoaPods permet de récupérer des briques (frameworks, SDK…) qui vont servir à créer un programme, ce qui évite au développeur d’avoir à tout coder lui-même. Image MacGeneration. Si ce genre d’utilitaires reste indispensable dans la trousse à outils de tout développeur, il existe plusieurs options et Swift Package Manager (SPM) créé par Apple a largement pris le relai de CocoaPods. Ce gestionnaire de paquets plus récent n’est peut-être pas aussi sophistiqué que son ancêtre, il a pour lui d’être directement intégré à Xcode et son utilisation est ainsi simplifiée dès lors qu’on veut coder une app en Swift. Au fil du temps, il a pris de plus en plus de place, au point où ses alternatives ont perdu progressivement en popularité. Swift Package Manager, notre série au complet sur le Club iGen C’est notamment pour cette raison que les créateurs de CocoaPods ont décidé d’arrêter leur propre solution. Ils ont annoncé à l’automne dernier un passage en lecture seule, qui est programmé pour le 2 décembre 2026. L’objectif n’est pas de tout arrêter d’un coup, ce serait une catastrophe pour un outil qui est toujours utilisé par des dizaines de milliers de projets open-source et un nombre probablement très élevé d’apps. L’arrêt se fera progressivement, avec l’envoi de plusieurs alertes aux contributeurs de « Pods », le nom des paquets dans ce gestionnaire. Surtout, CocoaPods ne cessera pas totalement de fonctionner le 2 décembre 2026 : la bascule en lecture seule empêchera de mettre à jour les paquets existants et il sera aussi impossible d’en ajouter de nouveaux. En revanche, on pourra toujours utiliser le gestionnaire pour récupérer un paquet existant et ainsi maintenir la gestion des dépendances pour tous les projets qui dépendent de lui. Ses créateurs se veulent rassurant de ce côté : il n’est pas question de casser entièrement CocoaPods pour de nombreuses années encore, l’infrastructure qui permet de télécharger les paquets restera active tant que GitHub et jsDeliver (CDN) continuent de fonctionner normalement. Si vous avez créé des Pods, l’heure est malgré tout venue pour les déplacer vers un autre gestionnaire. Outre SPM d’Apple, Carthage est une option populaire dans l’écosystème.

#CocoaPods #Développement

0 0 0 0

TMH

@tmaria.bsky.social

7 months ago

Let's celebrate chocolate making! Hang this #photography piece -Cocoa Fruit & Cocoa Beans- on your kitchen or Restaurant wall. This fruit is used to make chocolate! Here:
fineartamerica.com/featured/coc...

#cacoa #cocoabeans #cocoapods #naturephotography #Foodie #Chocolate #foodphotography #nature

21 4 0 0

DEV Community

@dev.to.web.brid.gy

10 months ago

React Native Expo SDK 51 Upgrade: Starting April 24, 2025, iOS apps must be built with the iOS 18 SDK. My Descent into the Podfile Abyss (and How I Climbed Out) Upgrading Expo SDK 50 → 51 in the Bare workflow to meet Apple’s iOS 18 SDK requirement. If you’re a React Native developer you want to stay in the sweet spot of library stability—but sometimes a looming deadline forces your hand. You start getting emails like this: App Store Connect Warning Hello, We noticed one or more issues with a recent delivery for the following app: Quiznect Version 1.0.40 Build 40 ITMS-90725: SDK version issue - This app was built with the iOS 17.5 SDK. Starting April 24, 2025, all iOS and iPadOS apps must be built with the iOS 18 SDK or later, included in Xcode 16 or later, in order to be uploaded to App Store Connect or submitted for distribution. Apple’s deadline arrived, so I had to upgrade my Expo app. I ran: npx expo upgrade …and hoped for the best. Sometimes it works flawlessly. Other times you end up on a multi‑day debugging odyssey through Podfiles, build logs, environment variables, and EAS configurations. This is the story of my upgrade from Expo SDK 50 → SDK 51 in the Bare Workflow. It wasn’t pretty, but I emerged with an iOS 18 SDK‑compliant build. May my tale of woe and triumph save you some time and sanity! ⸻ The Goal • Upgrade from Expo SDK 50 to SDK 51 • Meet Apple’s iOS 18 SDK requirement (Xcode 16+) by April 24, 2025 • Stay reasonably up‑to‑date without jumping straight to SDK 52 ⸻ Initial Steps & The First Hurdle: Dependencies & Workflow 1. Commit all changes, then run: npx expo upgrade 2. Expo CLI pointed out manual steps—because I use the Bare workflow (I manage ios/ & android/ in Git). Lesson 1: Know your workflow (Managed vs. Bare). The native‑dir upgrades differ significantly. I had an old patch-package workaround causing build failures on the build server. Lesson 2: Clean up obsolete workarounds & devDependencies before upgrading. ⸻ Targeting the Right SDK (and Dependencies) I first tried expo@latest (SDK 52) but pivoted to the stable SDK 51. In package.json: "dependencies": { "expo": "~51.0.0", // target SDK 51 "react": "...", "react-native": "...", // … }, Then: npx expo install --fix npm list expo react react-native expo-modules-core When mismatches persisted, I: npm cache clean --force sudo rm -rf node_modules rm package-lock.json npx expo install --fix Verified correct versions: • Expo 51.x • React 18.2.0 • RN 0.74.x • expo‑modules‑core 1.12.x Lesson 3: Manually set your SDK version in package.json • Clean‑install when deps get stuck • Always verify with npm list, don’t blindly trust --fix ⸻ The Pod Install Gauntlet cd ios npx pod-install Common Errors & Fixes 1. uninitialized constant FlipperConfiguration - Remove or comment out old Flipper logic in ios/Podfile. 2. cannot load such file ... native_modules - Comment out the bad require_relative in Podfile or install @react-native-community/cli. 3. undefined method use_expo_modules! - Ensure require for expo/scripts/autolinking is present. 4. React-Runtime Hermes → minimum deployment target; Bump platform :ios, '15.0' (RN 0.74 needs ≥ 14.0/15.0). 5. Unable to find a specification for fmt: rm ios/Podfile.lock to clear stale lock. 6. Unable to find a specification for ExpoModulesCore: npm uninstall expo-random → npx expo install expo-crypto npx expo install expo-modules-core pod cache clean --all + pod repo update Ensure source: 'https://cdn.cocoapods.org/' in Podfile. Lesson 4: Pod errors come in waves—fix one, the next appears. Lesson 5: Match your iOS deployment target to your RN version. Lesson 6: Deleting Podfile.lock often forces a fresh, clean resolution. Lesson 7: Migrate deprecated packages early. Lesson 8: Verify JS 👉 Native (.podspec) alignment. ⸻ The EAS Build Environment Saga Cloud builds have their own quirks: eas build --profile production --platform ios • expo doctor failures → fix locally, commit lockfiles. • eas.json rejected cocoapodsVersion → remove it or update eas-cli. • module redefinition (ReactCommon) → selective :modular_headers => true in Podfile. • Apple required Xcode 16 → set in eas.json: // eas.json excerpt { "build": { "production": { "ios": { "image": "macos-sonoma-14.6-xcode-16.1" } } } } Lesson 9: Always fix expo doctor issues locally and commit everything. Lesson 10: Keep your eas-cli up‑to‑date and resolve PATH conflicts. Lesson 11: If eas.json keys fail, check for deprecations or CLI versions. Lesson 12: Complex native errors sometimes need granular CocoaPods tweaks. ⸻ Success! Final command: eas build --profile production --platform ios --clear-cache ✅ Result: A successful Expo SDK 51 build against Xcode 16/iOS 18 SDK. Upgrading in the Bare workflow isn’t always straightforward, but with methodical troubleshooting—both on the JS side and in CocoaPods & EAS—you can emerge victorious. Happy upgrading!

0 0 0 0

@objectbox.bsky.social

1 year ago

💥 ObjectBox 4.1 for swift brings JWT authentication for Data Sync

github.com/objectbox/ob...

Enjoy! ❤️

#Swift #iOS #cocoapods #edgecomputing #vectordatabase #database #sync

0 0 0 0

GitSwifty

@gitswifty.bsky.social

1 year ago

Everytime I try and do something with #cocoapods I just end up in #ruby version hell 😭😭

Are people still using it or can I just drop support for it and require #SwiftPM? It’s so much easier to work with! #swift #swiftlang #iosdevelopment

0 0 0 0

Evely Kahungu

@evelynkahungu.bsky.social

1 year ago

My first raw cocoa tasting.
#Ghana
#Cocoapods

1 0 1 0

Mark Shaffer

@codemelted.com

1 year ago

CodeMelted | An Introduction to CocoaPods So my job is making me learn Swift as part of a new project I am supporting. This is fine. One of the many aspects of this job is the use of CocoaPods. Google Developer's put together a series of quic...

So my job is making me learn Swift as part of a new project I am supporting. This is fine. One of the many aspects of this job is the use of CocoaPods...

#CodeMeltedBlog #cocoapods #swift

codemelted.com/blog/article...

2 0 1 0

GOMOOT

@meneguzzo68.bsky.social

1 year ago

Vulnerabilità CocoaPods: rischi per app iOS e macOS I dispositivi Apple sono stati esposti a tre gravi vulnerabilità per quasi un decennio: falle nel gestore di dipendenze CocoaPods hanno esposto milioni di app.

💡 Vulnerabilità critiche in CocoaPods hanno esposto milioni di app iOS e macOS per quasi un decennio

gomoot.com/vulnerabilit...

#Apple #blog #cocoapods #hacker #ios #macOS #news #picks #security #tech #tecnologia #vulnerability