Giter Club home page Giter Club logo

Comments (1)

martinezguillaume avatar martinezguillaume commented on July 23, 2024

Little update
From my understanding there are, for the moment, no straight forward solution to this problem.
I found 3 possibilities :

  • Fork the pod that is using the builtin sqlite and make it use the sql from the pod, like that (for me, forking a pod dependency was a real pain, I didn't even succeed to link it properly in my ios project)
  • Work on the pod that is using the builtin sqlite and propose a solution like SQLite.swift (thanks simolus3). So, to add a standalone subspec that use sqlite3 from the pod and not from the builtin system (like this)
  • Patch the pod that is using the sqlite3 from the pod (here expo-updates), and make it use a sqlite version that is aligned with the sqlite system version.
    You can find the sqlite system version inside /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator17.5.sdk/usr/include/sqlite3.h you will have something like this
#define SQLITE_VERSION        "3.43.2"
#define SQLITE_VERSION_NUMBER 3043002
#define SQLITE_SOURCE_ID      "2023-10-10 13:08:14 1b37c146ee9ebb7acd0160c0ab1fd11017a419fa8a3187386ed8cb32b709aapl"

For me, I'm using the last solution to patch expo-updates, my patch look like this
expo-updates+0.25.20.patch

diff --git a/node_modules/expo-updates/ios/EXUpdates.podspec b/node_modules/expo-updates/ios/EXUpdates.podspec
index 92aacaa..407d744 100644
--- a/node_modules/expo-updates/ios/EXUpdates.podspec
+++ b/node_modules/expo-updates/ios/EXUpdates.podspec
@@ -28,7 +28,7 @@ Pod::Spec.new do |s|
   s.dependency 'EXManifests'
   s.dependency 'EASClient'
   s.dependency 'ReachabilitySwift'
-  s.dependency 'sqlite3', '~> 3.45.3+1'
+  s.dependency 'sqlite3', '3.43.1'
 
   unless defined?(install_modules_dependencies)
     # `install_modules_dependencies` is defined from react_native_pods.rb.

It can be dangerous because you'll miss features of the newest sqlite version but in this case and from my understanding, only expo-sqlite are using it, and since I'll not use it'll be fine

Sorry for all this infos, but I wanted to documente everything because this is a complex subject and I'm very surprised that it is not a common issue. Sometimes, I'm thinking that maybe I'm missing something....

from expo.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.