Close Menu
geekfence.comgeekfence.com
    What's Hot

    Wilkie refers gambling concerns to anti-corruption commission

    August 13, 2026

    Lumen ready for AI traffic rush – with programmable fabric and “more fiber than anyone”

    August 13, 2026

    With a feel for physics, AI models simulate a wider range of real-world scenarios | MIT News

    August 13, 2026
    Facebook X (Twitter) Instagram
    • About Us
    • Contact Us
    Facebook Instagram
    geekfence.comgeekfence.com
    • Home
    • UK Tech News
    • AI
    • Big Data
    • Cyber Security
      • Cloud Computing
      • iOS Development
    • IoT
    • Mobile
    • Software
      • Software Development
      • Software Engineering
    • Technology
      • Green Technology
      • Nanotechnology
    • Telecom
    geekfence.comgeekfence.com
    Home»iOS Development»react native – How to solve “”xcodebuild” exited with error code 65.“ – error from npx expo run:ios?
    iOS Development

    react native – How to solve “”xcodebuild” exited with error code 65.“ – error from npx expo run:ios?

    AdminBy AdminMarch 5, 2026No Comments2 Mins Read23 Views
    Facebook Twitter Pinterest LinkedIn Telegram Tumblr Email
    react native – How to solve “”xcodebuild” exited with error code 65.“ – error from npx expo run:ios?
    Share
    Facebook Twitter LinkedIn Pinterest Email


    Since a few days I am not able to make a development build of my Expo React Native project anymore. Whenever i run npx expo run:ios, I get the following error message:

    ❌  error: Filename "JavaScriptValue.swift" used twice: '/Users/fine/Desktop/coding/first-app-clean/node_modules/expo-modules-core/ios/JS/JavaScriptValue.swift' and '/Users/fine/Desktop/coding/first-app-clean/node_modules/expo-modules-core/ios/JSI/JavaScriptValue.swift' (in target 'ExpoModulesCore' from project 'Pods')
    
    
    › Compiling react-native-screens Pods/RNScreens » RNScreens-dummy.m
    › Compiling @react-native-async-storage/async-storage Pods/RNCAsyncStorage » RNCAsyncStorage-dummy.m
        Run script build phase '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed' will be run during every build because it does not specify any outputs. To address this issue, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'hermes-engine' from project 'Pods')
    
    › 1 error(s), and 1 warning(s)
    
    CommandError: Failed to build iOS project. "xcodebuild" exited with error code 65.
    

    I have been trying to solve this for more than 13 hours already. Here are things I have tried:

    # Remove node_modules and reinstall
    rm -rf node_modules package-lock.json
    npm install
    
    # Clear Expo cache and start
    npx expo start -c
    
    # Remove Pods and lockfile, reinstall pods
    cd ios
    rm -rf Pods Podfile.lock
    pod install
    cd ..
    
    # Remove derived data
    rm -rf ~/Library/Developer/Xcode/DerivedData
    
    # Clean build via expo
    npx expo prebuild --clean
    
    # Try different expo-av versions
    npm install [email protected]
    npm install [email protected]
    
    # Checked for duplicate Swift files
    ls node_modules/expo-modules-core/ios/JS/
    ls node_modules/expo-modules-core/ios/JSI/
    
    # Downgraded Node version
    nvm install 20
    nvm use 20
    

    Does anyone know how to solve this issue? Thank you very much.

    (Disclaimer: I am new to react native so please do not judge if I do things that are not best practice. I really appreciate if someone could help!)



    Source link

    Share. Facebook Twitter Pinterest LinkedIn Tumblr Email

    Related Posts

    What’s New in Xcode 27

    July 30, 2026

    ios – iCloud Dashboard returns “Internal Error” when querying records across all containers

    July 27, 2026

    ios – How to resolve the “Failed to build cache” build error in Xcode on macOS running in Docker in the docurr/macos project?

    July 22, 2026

    ios – Do Critical Alert (Apple) sounds play one at a time, or can two overlap?

    July 17, 2026

    ios – Bizarre animation issue in SwiftUI

    July 12, 2026

    security – How and where mnemonic/private keys are generated/stored in IOS for mobile non-custodial wallet

    July 7, 2026
    Top Posts

    Understanding U-Net Architecture in Deep Learning

    November 25, 202585 Views

    The Next Paradigm in Efficient Inference Scaling – The Berkeley Artificial Intelligence Research Blog

    May 16, 202648 Views

    Is it too late to start learning AI and machine learning in my 30s or 40s?

    April 9, 202648 Views
    Don't Miss

    Wilkie refers gambling concerns to anti-corruption commission

    August 13, 2026

    Independent MP Andrew Wilkie has taken the fight over gambling reform to the National Anti-Corruption…

    Lumen ready for AI traffic rush – with programmable fabric and “more fiber than anyone”

    August 13, 2026

    With a feel for physics, AI models simulate a wider range of real-world scenarios | MIT News

    August 13, 2026

    Monitoring beyond SNMP: Turning your network into a sensor

    August 13, 2026
    Stay In Touch
    • Facebook
    • Instagram
    About Us

    At GeekFence, we are a team of tech-enthusiasts, industry watchers and content creators who believe that technology isn’t just about gadgets—it’s about how innovation transforms our lives, work and society. We’ve come together to build a place where readers, thinkers and industry insiders can converge to explore what’s next in tech.

    Our Picks

    Wilkie refers gambling concerns to anti-corruption commission

    August 13, 2026

    Lumen ready for AI traffic rush – with programmable fabric and “more fiber than anyone”

    August 13, 2026

    Subscribe to Updates

    Please enable JavaScript in your browser to complete this form.
    Loading
    • About Us
    • Contact Us
    • Disclaimer
    • Privacy Policy
    • Terms and Conditions
    © 2026 Geekfence.All Rigt Reserved.

    Type above and press Enter to search. Press Esc to cancel.